Playing with Spring MVC

In Spring MVC, the following is a pattern of a simplified request handling mechanism:

1. DispatcherServlet receives a request and confers the request with handler mappings to find out which controller can handle the request, and then passes the request to that controller.
2. The controller performs the business logic (can delegate the request to a service or business logic processor) and returns some information back to DispatcherServlet for user display or response. Instead of sending the information (model) directly to the user, the controller returns a view name that can render the model.
3. DispatcherServlet then resolves the physical view from the view name and passes the model object to the view. This way, DispatcherServlet is decoupled from the view implementation.
4. The view renders the model. A view could be a JSP page, a servlet, a PDF file, an excel report, or any presentable component.

The following sequence diagram represents the flow and interaction of Spring MVC components...