Overall, I would recommend SiteMesh over Tiles.
Here's how to setup SiteMesh 3
You can use Tiles for in-page templates, but use SiteMesh for site-wide template. Nevertheless...
How to make Tiles suck less:
Use convention over configuration. For example, put your definitions in webapp/WEB-INF/tiles.xml
and there's no need to tell tiles where it is.
Use wildcards:
<definition name="default" template="/WEB-INF/templates/default.jsp">
<put-attribute name="titleKey" value=""/>
<put-attribute name="body" value=""/>
</definition>
<definition name="*" extends="default">
<put-attribute name="titleKey" value="{1}.title"/>
<put-attribute name="body" value="/WEB-INF/views/{1}.jsp" />
</definition>
If your controller returns view name index
, it will match the definition *
, and use the JSP file /WEB-INF/views/index.jsp
for the body, and use the message property index.title
.
If your controller returns view name contact-us
, it will match the definition *
, and use the JSP file /WEB-INF/views/contact-us.jsp
for the body, and use the message property contact-us.title
In your template, add:
<c:set var="titleKey"><tiles:getAsString name="titleKey" /></c:set>
and
<title><spring:message code="${titleKey}"/></title>
Add ReloadableResourceBundleMessageSource
bean to your servlet application context.
Make a file /src/main/resources/messages.properties
, with content like:
index.title = Welcome to Acme, Inc.
contact-us.title = Contact Us
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…