Spring MVC 프레임워크와 그 구성 요소에 대한 이해

Spring은 여성을 제어하고, MVC를 지원하며, 프론트 컨트롤러를 사용하여 URL 매핑을 처리하고 다양한 환경에 대한 의존성을 줄입니다.

### Spring MVC 소개
* 🌸 Spring MVC는 **모델-뷰-컨트롤러(MVC) 패턴**을 지원하는 프레임워크로 도입되었습니다.
* Spring MVC에서 컨트롤러의 함수는 **서비스로 구현**되며, 뷰 출력은 **JSP 템플릿**을 전달하여 처리합니다.
* 🎯 Spring MVC에서 프론트 컨트롤러의 주요 역할은 **사용자 요청을 받아 실제 컨트롤러로 전달**한 다음 처리된 값을 전달하는 것입니다.
* 📦 Spring MVC의 프론트 컨트롤러는 **사용자에게 전달할 입력값을 쉽게 패키징**할 수 있습니다.
* 🔗 Spring MVC의 프론트 컨트롤러를 사용하면 **커플링을 줄이고 다양한 환경에서 프레임워크를 사용**할 수 있습니다.
* 📜 구성 파일은 Spring MVC에서 **URL을 처리할 컨트롤러를 지정**하는 데 사용됩니다.
* ⚙ Spring MVC를 사용할 때 이전에 애플리케이션에서 설정했던 매핑 정보가 이제 **Spring 구성으로 이동**했습니다.
* 💡 많은 개발자가 시간 제약으로 인해 **Spring과 같이 잘 알려진 라이브러리를 사용**하는 경향이 있지만, 개별적으로 기능을 구축하여 기술을 개발하는 것이 도움이 될 수 있습니다.

Hello, this is lesson 6. Nice to meet you. I think from today, we can have a time where we can actually look forward to Spring. Since today is not the first practical session but the first session, let's start by finding out what MBC, which controls women called Spring, is. For those taking this class, it is natural to have studied servlets and JSP before and have experience in creating a program in the MVC pattern. If you don't have such experience, I briefly explained the basic concepts and choices, so I will continue with supplementary explanations. First of all, the Spring we are talking about supports the MVC. It means that the monster practices. You will understand what that means when you see it. Originally, we had Model 1 and Model 2 regarding the model. There was a conceptual part called the controller, and then there was a part responsible for view output, but they were combined into one.

When my model goes in, it was divided into this, but when it is not, basically, the part of the control that is resolved is implemented as a service, and then we could find the template that is responsible for the output that is responsible for passing the fellow named jsp as a belt. At that time, we used the dispatch philosophy to do forwarding. So, all controllers need to implement the dispatch function, and we think we should have a little experience with all controllers. Therefore, how do we implement this? Only the controller function is purely implemented, and since this is not a servlet but a woman, you can think of it as a general Java class. It is a bit oddly expressed the concept of a general Java class, but you can find it as a general Java class. It's just a plain Java object.

I will become a god. So if you don't stay in your body here, then since the controller is missing now, of course, only the dispatch function will remain. However, now that the controller is gone, the function of dispatch is an opportunity to forward this, so the function is almost the same. So, instead of creating multiple of these, just make one. When you do this, the role of this guy becomes simple. When a user request comes in, he actually forwards that request to my controller, the actual controller that I have, and then receives the value returned by processing that request and forwards it to B. It acts as an intermediary. However, it's not that simple. The role of this guy is very important. Receiving a user's request means not just routing the request, but also that if there are input values to be passed to the user, it can easily package those input values.

Let's talk about how to easily deliver user input here. Instead of using Market Parameter and Sub-later like we've done so far, we can block all the functions of the service here. So, by using the basic input side, we can provide a basic format that can be used here, such as offering strings or integers, for example. The second point is not just simply delivering in basic form, but we can organize data in various ways, such as organizing by dates, must-have items, or experiences. Then, here, we can handle input without using any third-party libraries, and even when trying to pass on data the child has, there is no dispatch function here. The dispatch will now return the request here without using any libraries.

You will receive it. Then, when returning, you will need a page from this side. It means that the return information that says what page of mine is needed will inform about the information for the Envue page. By calling the child, now you can limit the service function here. The main reason we separate this guy is to make it possible to reduce the distance for things like services or requests or happy cities, so that you can reduce the coupling here and allow you to use it in different environments. This way, you can lower the coupling here and make it possible for you to use it in different environments. So, how do we make this well? It's very important. It's about how Spring provided this. We will create a controller using the Front Controller Live that we are providing. In a way, if we make this Front Controller very well, it will be very pleasant.

It seems that you can also develop such a way to break up. You can make the capital to now 1t dry up and play a role in the sub lg g pad ultra spray function. So, should we bring up various u options? All those u options should be received and processed by the child, so all the children must be scheduled to come in. Therefore, appropriate controllers need to handle all that, so they should have separate information on which controller will handle the url. That's why when using the font controller, you need a configuration file. We need to know about things like which one is being processed and so on. That's why in the past, we mapped urls and things here, or if there was a later version upgrade, we had set it up here through annotations. The content has been moved here. Here, everything is just for this phone.

Only the settings for the game are set up, so for this reason, we are mapping information here. So in a way, it may seem like nothing has changed significantly, even if we set it to 20. The mapping information we set here has simply moved up to the Spring. By doing this, questioning whether one must definitely use this for the frontend, as I mentioned earlier, by reducing the compatibility with this, maybe in the end, even if the actual environment changes, we may still be able to do it. We used to create this directly in the past, so we created a separate control separated from this and the experimental results to reduce the dependency and make it possible for us to use this in different environments in the future. Nowadays, if we use Spring instead of creating it ourselves, when we complete something, we create an environment that can be distinguished from Tomcat.

Now, when it comes to the six cleaning times called Spring, we may also know another problem. This is my personal opinion, but in fact, I don't think it's good to develop this using the methodology. Many developers seem to struggle with time issues and find it difficult to match certain markers, so they tend to rush to well-known libraries and use them. If possible, since these things are not difficult, wouldn't it be better to build skills by developing them individually? Anyway, we are going to use Spring to control the leaves. This controller will deliver two pieces of information, and when the dispatch requests it, it will find the appropriate value and deliver the related data.

Yes, it was mentioned that the output data used at that time is called a model. That's correct. If it's like this, it's possible. Calling something like spray 0 b c is using this library directly. Where is this library used? It exists in the Spring's MVC library. If you look there, there is something called dispatch * sira. We will set this up and use it later. We will cover the details in the next session. Thank you very much, and we will continue with the next set.

Spring MVC (스프링 웹 MVC) 강의 01 - Spring MVC란

뉴렉쌤이 유툽으로 제공하는 IT 전문가를 위한 프로그래밍 강의 (현재 온라인 서비스는 공사중입니다  ver 0.0.1.)
분야 :  가리지 않음 모든 분야

제작 : (주) 뉴렉처
ⓒ2021. Newlecture All rights reserved.

국비지원 무료 과정 모집 안내 : (2024년 6월 3일에 시작하는 자바 풀스택 과정 모집중 입니다.) 
국비지원 무료과정입니다. 빈자리 없을 수도 있습니다. 선착순 지원 서두르세요. 

https://www.newlecture.com/class/detail?id=3




뉴렉처

Spring 프레임워크는 모델, 뷰, 컨트롤러를 결합한 MVC 패턴을 지원합니다.

Spring의 컨트롤러는 전달을 위해 디스패치 철학을 사용하여 서비스로 구현되며, 기본적으로 일반 Java 객체입니다.

컨트롤러는 사용자 요청을 수신하여 실제 컨트롤러로 전달한 다음 처리된 값을 뷰로 보내는 동시에 사용자를 위한 입력 값을 패키징하는 중요한 역할을 합니다.

사용자 친화적인 입력 전달 시스템 만들기

타사 라이브러리를 사용하지 않고 문자열이나 정수를 제공하는 사용자 입력을 위한 기본 형식을 개발하세요.

날짜, 필수 항목, 경험 등 다양한 방식으로 데이터를 구성하여 입력을 효과적으로 처리할 수 있습니다.

프론트 컨트롤러 라이브를 사용하여 컨트롤러를 생성하여 사용자 요청을 효율적으로 관리하고 처리합니다.

URL 매핑에 Spring 사용으로의 전환

URL 매핑에 Spring을 사용하도록 전환하면 프로세스를 더 잘 제어하고 관리할 수 있습니다.

매핑 정보를 Spring으로 옮기면 향후 다양한 환경을 처리하고 처리하기가 더 쉬워집니다.

또한 이러한 전환은 의존성을 줄이고 프론트엔드와의 호환성을 개선하여 보다 유연한 솔루션을 제공하는 데 도움이 됩니다.

스프링을 사용하여 MVC에서 잎사귀 제어하기

개발자들은 스프링에서 잎을 제어하기 위해 잘 알려진 라이브러리를 사용할 때 종종 시간 문제로 어려움을 겪습니다.

이러한 라이브러리를 서둘러 사용하기보다는 개별적으로 개발하면서 실력을 쌓는 것이 좋습니다.

이 과정에서 사용되는 출력 데이터를 모델이라고 하며, 스프링의 MVC 라이브러리는 잎을 제어하기 위한 특정 라이브러리가 사용되는 곳입니다.