DataBinder's "initDirectFieldAccess" Package org.springframework.web $ ^{*} $ changed WebApplicationContext's "ROOT_WEB_APPLICATION_CONTEXT_ATTRIBUTE" to actually start with the package refined Struts DelegatingActionProxy and Delegating(Tiles)RequestProcessor to fall back to root WebApplicationContext * added DelegatingNavigationHandlerProxy and DelegatingPhaseListenerMulticaster to JSF support wherever a root cause gets wrapped by a ServletException (for nicer root cause handling) * WebApplicationContext interface does not extend ThemeSource anymore; implementing ThemeSource is now optional *

"contextAttribute" property (for WebApplicationContext retrieval) to DelegatingFilterProxy and FrameworkServlet * RequestContext does not fail when WebApplicationContext's ServletContext is null (like refined Struts DelegatingActionProxy and Delegating(Tiles)RequestProcessor to fall back to root WebApplicationContext * added DelegatingNavigationHandlerProxy and DelegatingPhaseListenerMulticaster to JSF support

Sources ..... 78 Context Configuration with Dynamic Property Sources ..... 83 Loading a WebApplicationContext ..... 85 Context Caching ..... 90 Context Hierarchies ..... 92 3.5.7. Dependency Injection integration testing of your Spring MVC and REST Controller classes in conjunction with your WebApplicationContext configuration for Spring MVC, use the Spring MVC Test Framework instead. ### Chapter 3. Integration TestContext Framework provides consistent loading of Spring ApplicationContext instances and WebApplicationContext instances as well as caching of those contexts. Support for the caching of loaded contexts

Context Hierarchy DispatcherServlet expects a WebApplicationContext (an extension of a plain ApplicationContext) for its own configuration. WebApplicationContext has a link to the ServletContext and the Servlet methods on RequestContextUtils to look up the WebApplicationContext if they need access to it. For many applications, having a single WebApplicationContext is simple and suffices. It is also possible to context hierarchy where one root WebApplicationContext is shared across multiple DispatcherServlet (or other Servlet) instances, each with its own child WebApplicationContext configuration. See Additional

profiles ..... 312 Context configuration with test property sources ..... 316 Loading a WebApplicationContext ..... 319 Context caching ..... 321 Context hierarchies ..... 322 Dependency injection implementations ..... 475 22.2. The DispatcherServlet ..... 475 Special Bean Types In the WebApplicationContext ..... 479 Default DispatcherServlet Configuration ..... 480 DispatcherServlet Processing features. You simply need to wire up your business logic using an ApplicationContext and use a WebApplicationContext to integrate your web layer. ![Image](/uploads/documents/1/8/8/0/18806a1f0fa62b480a2465d065da2509/p37_1

configuration with environment profiles Context configuration with test property sources Loading a WebApplicationContext Context caching Context hierarchies Dependency injection of test fixtures Testing request of other MVC implementations The DispatcherServlet Special Bean Types In the WebApplicationContext Default DispatcherServlet Configuration DispatcherServlet Processing Sequence features. You simply need to wire up your business logic using an ApplicationContext and use a webApplicationContext to integrate your web layer. Figure 2.4. Remoting usage scenario ![Image](/uploads/doc

... 319 Context configuration with test property sources ..... 324 Loading a WebApplicationContext ..... 326 Context caching ..... 329 Context hierarchies ..... 330 Dependency implementations ..... 482 22.2. The DispatcherServlet ..... 482 Special Bean Types In the WebApplicationContext ..... 486 Default DispatcherServlet Configuration ..... 487 DispatcherServlet Processing features. You simply need to wire up your business logic using an ApplicationContext and use a WebApplicationContext to integrate your web layer. ![Image](/uploads/documents/8/b/b/3/8bb395d7613b352480ac6c54691be95b/p37_1

configuration with environment profiles Context configuration with test property sources Loading a WebApplicationContext Context caching Context hierarchies Dependency injection of test fixtures Testing request of other MVC implementations The DispatcherServlet Special Bean Types In the WebApplicationContext Default DispatcherServlet Configuration DispatcherServlet Processing Sequence features. You simply need to wire up your business logic using an ApplicationContext and use a webApplicationContext to integrate your web layer. Figure 2.4. Remoting usage scenario ![Image](/uploads/doc

up your business logic using an ApplicationContext and integrate your Web UI layer using a WebApplicationContext.  Remoting ApplicationContext and optional parent contexts, and application-layer specific contexts such as the WebApplicationContext, among other enhancements. In short, the BeanFactory provides the configuration framework ApplicationContexts in Spring can be scoped. In the web framework, each DispatcherServlet has its own WebApplicationContext, which contains the DispatcherServlet configuration beans. The default BeanFactory used by

书栈(BookStack.CN) 目 录 致谢 README Spring Web MVC框架简介 Spring Web MVC的新特性 允许其他MVC实现 DispatcherServlet WebApplicationContext中特殊的Bean类型 默认的DispatcherServlet配置 DispatcherServlet的处理流程 控制器的实现 使用@Controller注解定义一个控制器 使用@ Spring表单的JSP标签库 新增生命周期仅绑定到当前HTTP请求或HTTP会话的Bean类型。严格来说，这不是Spring MVC自身的特性，而是Spring MVC使用的上下文容器WebApplicationContext所提供的特性。这些bean的scope在6.5.4请求、会话及全局会话scope一节有详细描述。 允许其他MVC实现 21.1.2 允许其他MVC实现 有些项目可能更倾向于使 ApplicationContext 实例是可以有范围（scope）的。在Spring MVC中，每 个 DispatcherServlet 都持有一个自己的上下文对象 WebApplicationContext ，它又继承了根 (root) WebApplicationContext 对象中已经定义的所有bean。这些继承的bean可以在具体的 Servlet实例中被重载，在每个Servlet实例中你也可以定义其scope下的新bean。