In this section, you will learn about chaining of multiple view resolvers.

Chaining of Multiple view resolvers

In this section, you will learn about chaining of multiple view resolvers.

Spring supports multiple view resolvers and you can chain resolvers. And in some specific condition, you can override it. In your application context, you can chain view by adding more than one resolver to application context.

You can set view resolver's ordering in view resolver chain by setting order property. Keep in mind - higher the order priority, the later the view resolver is positioned in the chain. The InternalResourceViewResolver must always assign with the lowest priority because it will resolve the view whatever view name is returned.

Example

In the given below example, three view resolvers, XmlViewResolver, ResourceBundleViewResolver, InternalResourceViewResolver contained by the chain and they have order 0,1,2 respectively :

<beans ...>
	<bean class="org.springframework.web.servlet.view.XmlViewResolver">
		<property name="location">
		<value>/WEB-INF/spring-views.xml</value>
		</property>
		<property name="order" value="0" />
	</bean>
	
	<bean class="org.springframework.web.servlet.view.ResourceBundleViewResolver">
		<property name="basename" value="spring-views" />
		<property name="order" value="1" />
	</bean>
	
	<bean id="viewResolver"
	class="org.springframework.web.servlet.view.InternalResourceViewResolver" >
		<property name="prefix">
		<value>/WEB-INF/pages/</value>
		</property>
		<property name="suffix">
		<value>.jsp</value>
		</property>
		<property name="order" value="2" />
	</bean>
</beans>

 

Related Tags for Chaining of Multiple view resolvers:

More Tutorials from this section

• Spring 3.2 Asynchronous Request Processing
• Autogenerated logical view name through RequestToViewNameTranslator
• Chaining of Multiple view resolvers
• ContentNegotiatingViewResolver
• Content Negotiation Configuration
• ControllerClassNameHandlerMapping class for handling convention mapping
• @Controller annotation for defining new controller
• Customizing the Default Error Page
• Customizing the MVC Java config or XML Namespace
• Support for ETag
• @ExceptionHandler & @ResponseStatus annotation
• Spring 3.2
• Interceptors Configuration using Java or XML
• Locales in Spring MVC
• Modification in conventional ModelAndView
• Multipart support for file upload in Spring MVC
• mvc:default-servlet-handler
• MVC Java Config or the MVC XML Namespace
• Processing Sequence of DispatcherServlet
• Redirecting and forwarding to views