Chaining multiple view resolvers

[ervalerio]

in my webapp I'd like to have both tiles aggregations (in the struts meaning of the term), and plain-old-jsp.

Then, i tried adding the following beans in my applicationContext.xml:


<bean id="tilesViewResolver" class="org.springframework.web.servlet.view.InternalResou rceViewResolver">
<property name="order" value="0"/>
<property name="requestContextAttribute" value="requestContext"/>
<property name="viewClass"
value="org.springframework.web.servlet.view.tiles.TilesJs tlView"/>
</bean>
<bean id="jstlViewResolver"
class="org.springframework.web.servlet.view.InternalResou rceViewResolver">
<property name="viewClass">
<value>org.springframework.web.servlet.view.JstlView</value>
</property>
<property name="prefix">
<value>/WEB-INF/jsp/</value>
</property>
<property name="suffix">
<value>.jsp</value>
</property>
</bean>


my hope was that when resolving a view, the tiles resolver is used first, and if no definition for the requested view is found, it tries to resolve it as a jsp. Unfortunatly, it doesn't work: when requesting main.html, which is not a tile definition, it doesn't find it.

is that they correct technique to chain view resolvers ?

thanks,
valerio

[Colin Yates]

You should read the documentation for InternalResourceViewResolver ;):

* Convenience subclass of UrlBasedViewResolver that supports InternalResourceView
* (i.e. Servlets and JSPs), and subclasses like JstlView and TilesView.
*
* <p>The view class for all views generated by this resolver can be specified
* via <code>setViewClass</code>. See UrlBasedViewResolver's javadoc for details.
*
* <p>BTW, it's good practice to put JSP files that just serve as views under
* WEB-INF, to hide them from direct access (e.g. via a manually entered URL).
* Only controllers will be able to access them then.
*
* <p><b>Note:</b> When chaining ViewResolvers, a InternalResourceViewResolver
* always needs to be last, as it will attempt to resolve any view name,
* no matter whether the underlying resource actually exists.

[ervalerio]

hello,
*<p><b>Note:</b> When chaining ViewResolvers, a InternalResourceViewResolver
* always needs to be last, as it will attempt to resolve any view name,
* no matter whether the underlying resource actually exists.

the last counting from zero ? the javadoc doesn't provide an example of usage of that class, which would help a lot :(
i found out about the 'order' property only searching into the forum..
do you have a working example or a link to it perhaps ?

[Colin Yates]

The problem is that you have defined two InternalResourceViewResolvers. The first one will always win.