Following Toby's Spring 3.1 on Spring Boot:
Breather Diagram 01. Architecture of Spring for MVC
Ah-key-tek-chuh of Spring for MVC
Before Spring kicks off in earnest, I want to post once more — organizing the architecture I learned in class.
Personally, while learning Java, the thing I think is most important is distinguishing Java from the framework.
While doing examples, you sometimes get confused whether Spring is Java or Java is Spring.
Reviewing Toby: Spring is a framework for IoC. Java is the Java language.
IoC refers to a series of methodologies where, when a program is built, it isn't done as one-man-army execution but through division of labor managed overall by a role called a "factory." This is described by the phrase "Inversion of Control."
For a while I plan to distinguish Java and Spring concepts, and first draw out a few diagrams and architectures.
First, I'm posting the first diagram.
Spring MVC Architecture
Brief description of the Spring framework diagram
1. When the DispatcherServlet, acting as the front controller, receives a request, it gets handler information via HandlerMapping and passes it to the HandlerAdapter.
2. The HandlerAdapter validates the object for the handler information, and if there's no issue, runs the relevant method on the controller. (If there is an issue, it outputs error messages — 404, 505, etc.)
3. The controller exchanges information through business logic. The received information is connected to a viewResolver or view object via viewName to produce the response.
