.apache.org">http://tiles.apache.org for more information about Tiles, which basically is a templating mechanism for JSP-based web applications.
Note: Spring 3.0 requires Tiles 2.1.2 or above, with explicit support for Tiles 2.2. Tiles 2.1's EL support will be activated by default when running on JSP 2.1 or above and when the Tiles EL module is present in the classpath.
The TilesConfigurer simply configures a TilesContainer using a set of files containing definitions, to be accessed by {@link TilesView} instances. This is aSpring-based alternative (for usage in Spring configuration) to the Tiles-provided {@link org.apache.tiles.web.startup.TilesListener} (for usage in web.xml
).
TilesViews can be managed by any {@link org.springframework.web.servlet.ViewResolver}. For simple convention-based view resolution, consider using {@link TilesViewResolver}.
A typical TilesConfigurer bean definition looks as follows:
<bean id="tilesConfigurer" class="org.springframework.web.servlet.view.tiles2.TilesConfigurer"> <property name="definitions"> <list> <value>/WEB-INF/defs/general.xml</value> <value>/WEB-INF/defs/widgets.xml</value> <value>/WEB-INF/defs/administrator.xml</value> <value>/WEB-INF/defs/customer.xml</value> <value>/WEB-INF/defs/templates.xml</value> </list> </property> </bean>
The values in the list are the actual Tiles XML files containing the definitions.
@author Juergen Hoeller
@since 2.5
@see TilesView
@see TilesViewResolver