How Spring MVC Work? Complete Workflow of Spring MVC Request

When a user access any web application on their browser, it seems to be a two step process for them, First where the user send request to the server and second is Server sending the response back with processed data.

But there are a lot of other processing happen during these two steps.
There are multiple layers in between. In today's video we'll see what all is happening to a Request submitted by user to Spring MVC application and how the response is travelled back to the user after processing.

MVC stands for Model-View-Controller. It is a design pattern used in software development to separate an application into three interconnected components:
Model: Represents the data and business logic of the application. It can be a single object or a collection of objects.
View: Represents the user interface and displays information to the user. Commonly, JSP (JavaServer Pages) with JSTL (JavaServer Pages Standard Tag Library) is used to create view pages.
Controller: Contains the application’s business logic. It handles user requests, processes data, and communicates between the model and view. In Spring MVC, the @Controller annotation marks a class as the controller.

0:00 Introduction
0:53 Beginning of Request
0:58 Filters
1:41 Front Controller-DispatcherServlet
1:57 Interceptors
2:39 Handler Mapping with Example
3:33 Controller Method Invocation
3:56 Service and DAO Layer
4:46 View Resolver
5:10 Response Generation

To check out more on the tutorials Topic wise you can follow below links

Links:

Please do checkout other tutorial videos also if required:

Please do LIKE, Share and SUBSCRIBE

Thank You

The Spring Framework is an application framework and inversion of control container for the Java platform. The framework's core features can be used by any Java application, but there are extensions for building web applications on top of the Java EE platform.(Wikipedia)

A BeanFactory is like a factory class that contains a collection of beans. The BeanFactory holds Bean Definitions of multiple beans within itself and then instantiates the bean whenever asked for by clients.

The BeanFactory is the actual container which instantiates, configures, and manages a number of beans. These beans typically collaborate with one another, and thus have dependencies between themselves. These dependencies are reflected in the configuration data used by the BeanFactory

BeanFactory also takes part in the life cycle of a bean, making calls to custom initialization and destruction methods.

Bean life cycle is managed by the spring container. When we run the program then, first of all, the spring container gets started. After that, the container creates the instance of a bean as per the request, and then dependencies are injected. And finally, the bean is destroyed when the spring container is closed. Therefore, if we want to execute some code on the bean instantiation and just after closing the spring container, then we can write that code inside the custom init() method and the destroy() method.

Spring Bean Scope in a nutshell refers to the lifecycle and visibility of a bean instance in a Spring-based application. Bean scopes determine the number of instances of a bean that will be created and how long the bean instances will exist. The five main scopes in Spring are: Singleton, Prototype, Request, Session, and Global Session.

#java #spring #springframework #springmvc