.apache.org">http://tiles.apache.org for more information about Tiles, which basically is a templating mechanism for web applications using JSPs and other template engines.
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.tiles3.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. If the list is not specified, the default is {@code "/WEB-INF/tiles.xml"}.
@author mick semb wever
@author Rossen Stoyanchev
@since 3.2