Spring 프레임 워 크 참고 문서 (5) - The Web 의 Portlet MVC Framework

Spring 프레임 워 크 참고 문서 (5) - The Web 의 Portlet MVC Framework
Part V. The Web
이 부분 참고 문 서 는 소개 할 것 이다. spring 프레임 워 크 는 표현 층 에 대한 지원 (특히 웹 표현 층 에 대한 지원) 과 웹 socket 형식의 웹 응용 을 지원 합 니 다.
spring 프레임 워 크 는 자신의 웹 프레임 워 크 를 가지 고 있 습 니 다 - Spring Web MVC, 이 부분 은 앞의 두 장 에서 소개 된다.후속 장절 소개 spring 프레임 워 크 와 기타 웹 기술 의 통합, 예 를 들 어 JSF 기다리다
Spring MVC 프레임 워 크, portlet 프레임 워 크 를 소개 합 니 다.Following that is coverage of Spring Framework’s MVC portlet framework.
끝 부분 은 Spring 프레임 워 크 를 전면적으로 덮어 씁 니 다. Chapter 20, 웹 소켓 지원 (포함) Section 20.4, “STOMP Over WebSocket Messaging Architecture”)。
Chapter 16, 웹 MVC 프레임 워 크 Chapter 17, 보기 기술 Chapter 18, 다른 웹 프레임 워 크 와 통합 Chapter 19, Portlet MVC Framework
Chapter 20, WebSocket 지원 19. Portlet MVC Framework
19.1 Introduction
JSR-168 The Java Portlet Specification
For more general information about portlet development, please review a whitepaper from Oracle entitled "Introduction to JSR 168", and of course the JSR-168 Specification itself.
In addition to supporting conventional (servlet-based) Web development, Spring also supports JSR-168 Portlet development. As much as possible, the Portlet MVC framework is a mirror image of the Web MVC framework, and also uses the same underlying view abstractions and integration technology. So, be sure to review the chapters entitled Chapter 16, 웹 MVC 프레임 워 크 and Chapter 17, 보기 기술 before continuing with this chapter.
Bear in mind that while the concepts of Spring MVC are the same in Spring Portlet MVC, there are some notable differences created by the unique workflow of JSR-168 portlets.
The main way in which portlet workflow differs from servlet workflow is that the request to the portlet can have two distinct phases: the action phase and the render phase. The action phase is executed only once and is where any backend changes or actions occur, such as making changes in a database. The render phase then produces what is displayed to the user each time the display is refreshed. The critical point here is that for a single overall request, the action phase is executed only once, but the render phase may be executed multiple times. This provides (and requires) a clean separation between the activities that modify the persistent state of your system and the activities that generate what is displayed to the user.
Spring Web Flow
Spring Web Flow (SWF) aims to be the best solution for the management of web application page flow.
SWF integrates with existing frameworks like Spring MVC and JSF, in both Servlet and Portlet environments. If you have a business process (or processes) that would benefit from a conversational model as opposed to a purely request model, then SWF may be the solution.
SWF allows you to capture logical page flows as self-contained modules that are reusable in different situations, and as such is ideal for building web application modules that guide the user through controlled navigations that drive business processes.
For more information about SWF, consult the Spring Web Flow website.
The dual phases of portlet requests are one of the real strengths of the JSR-168 specification. For example, dynamic search results can be updated routinely on the display without the user explicitly rerunning the search. Most other portlet MVC frameworks attempt to completely hide the two phases from the developer and make it look as much like traditional servlet development as possible - we think this approach removes one of the main benefits of using portlets. So, the separation of the two phases is preserved throughout the Spring Portlet MVC framework. The primary manifestation of this approach is that where the servlet version of the MVC classes will have one method that deals with the request, the portlet version of the MVC classes will have two methods that deal with the request: one for the action phase and one for the render phase. For example, where the servlet version of AbstractController has the handleRequestInternal(..) method, the portlet version ofAbstractController has handleActionRequestInternal(..) and handleRenderRequestInternal(..) methods.
The framework is designed around a DispatcherPortlet that dispatches requests to handlers, with configurable handler mappings and view resolution, just as theDispatcherServlet in the web framework does. File upload is also supported in the same way.
Locale resolution and theme resolution are not supported in Portlet MVC - these areas are in the purview of the portal/portlet container and are not appropriate at the Spring level. However, all mechanisms in Spring that depend on the locale (such as internationalization of messages) will still function properly becauseDispatcherPortlet exposes the current locale in the same way as DispatcherServlet.
19.1.1 Controllers - MVC 의 C 층
기본 정적 처리 장 치 는 매우 간단 하 다. Controller 인터페이스, 두 가지 방법 만 제공 합 니 다.
void handleActionRequest(request,response)
ModelAndView handleRenderRequest(request,response)
이 프레임 워 크 의 실현 층 에는 비슷 한 컨트롤 러 가 많이 포함 되 어 있다. 예 를 들 어 AbstractController, SimpleFormController 잠깐 만.데이터 바 인 딩, 명령 대상 의 사용, 모델 처리 와 보기 해석 은 servlet 프레임 워 크 에서 모두 같 습 니 다.
19.1.2 Views - MVC 의 V 층
All the view rendering capabilities of the servlet framework are used directly via a special bridge servlet named ViewRendererServlet. By using this servlet, the portlet request is converted into a servlet request and the view can be rendered using the entire normal servlet infrastructure. This means all the existing renderers, such as JSP, Velocity, etc., can still be used within the portlet.
19.1.3 Web-scoped beans
Spring Portlet MVC supports beans whose lifecycle is scoped to the current HTTP request or HTTP Session (both normal and global). This is not a specific feature of Spring Portlet MVC itself, but rather of the WebApplicationContext container(s) that Spring Portlet MVC uses. These bean scopes are described in detail inSection 5.5.4, "요청 역할 영역, 세 션 역할 영역 과 전역 세 션 역할 영역"
19.2 The DispatcherPortlet
Portlet MVC is a request-driven web MVC framework, designed around a portlet that dispatches requests to controllers and offers other functionality facilitating the development of portlet applications. Spring’s DispatcherPortlet however, does more than just that. It is completely integrated with the Spring ApplicationContextand allows you to use every other feature Spring has.
Like ordinary portlets, the DispatcherPortlet is declared in the portlet.xml file of your web application:

    sample
    org.springframework.web.portlet.DispatcherPortlet
    
        text/html
        view