Let's take a look at an example of applying the MVC pattern in Spring. Spring is a very famous framework, isn't it? It provides many functions when developing applications based on Java. It follows the following architecture. Yes, we will examine Spring Web MVC where the MVC pattern is applied. So, when we talk about which part the MVC pattern is applied to, it's the request handling process of the Dispatcher Servlet. Therefore, today we will take a closer look at the request handling process of the Dispatcher Servlet. So, when a user's request comes in like this, right? So, when a request is sent to a web server created with Spring, in the beginning, the Dispatcher Servlet, which is a front controller, handles this request.

I got it all. Come to me, everything is correct. After receiving everything, what do you do next? Through handler mapping, we determine which controller will handle this request. So, when we go to the factory, there will be a factory manager, right? So, you should think about the factory manager. The factory manager decides which controller to assign the task to. So, how is this decision made now? In fact, in the past, it was based on things like class names, URLs, and XML configurations, but usually, we refer to request mapping. So, nowadays, we simply assign the controller based on request wrapping. So, when you write code in Spring, you will probably build your code like this. Currently, it's simplified into a simple function, but in reality, as you continue, you will end up writing code that maps controllers like this.

Anyway, by doing that, we need to decide on the controller. What does the controller do now? When I explained the MVC pattern earlier, what did I say? It handles business logic. To handle business logic, it may or may not reference the database. If it does, it goes through the repository layer and the database layer below. In any case, it retrieves data from here, processes it, and then goes out. It contains things like model constants and variables. Based on these things, along with view resolver, we create a view to show to the user. So, as you can see, the controller is in the center, and now the model and the view resolver...

This is how the view is, the pattern controller acts as a bridge between the model and the church in the center, right? This is what contains these things, right? By doing this, in the end, this view is delivered to the user. Do you understand? In this way, we have looked at the process of handling requests in Spring. That's all for today.

Spring과 MVC패턴 | 디스패처서블릿

▶CS지식의 정석 
https://inf.run/17Fb
▶C++ 10주완성 코딩테스트
https://inf.run/xZhA


Spring과 MVC패턴 | 디스패처서블릿

Spring과 MVC패턴 | 디스패처서블릿

Scripts