So far, we have seen lots of concepts, such as the dispatcher servlet, request mapping, controllers, and view resolver; it would be good to see the overall picture of the Spring MVC request flow so that we can understand each component's responsibilities. However, before that, we need to understand the Model View Controller (MVC) concept some more. Every enterprise-level application's presentation layer can logically be divided into the following three major parts:
The part that manages the data (Model)
The part that creates the user interface and screens (View)
The part that handles interactions between the user, user interface, and data (Controller)
The following diagram will help you understand the event flow and command flow within an MVC pattern:
The classic MVC pattern
Whenever a user interacts with the view by clicking on a link or button, the view issues an event notification to the controller, and the controller issues a command notification to the model to update...