Should I be able to do the following localization using extended tiles definitions?
In tiles-defs.xml:
<tiles-definitions>
<definition name=".page.base" page="/default-layout.jsp">
<put name="header" value="/header.jsp"/>
<put name="footer" value="/footer.jsp"/>
</definition>
<definition name=".page.index" extends=".page.local">
<put name="content" value="/index-content.jsp"/>
</definition>
<definition name=".page.cart" extends=".page.local">
<put name="content" value="/cart-content.jsp"/>
</definition>
</tiles-definitions>In tiles-defs_de_DE.xml:
<tiles-definitions>
<definition name=".page.local" extends=".page.base">
<put name="menus" value="/menus_de_DE.jsp"/>
</definition>
</tiles-definitions>In other words, there is a common base page across all the locales. Each local adds a locale-specific menu to every page. Then there are the variety of specific pages that add their unique content.
Does this make sense? Is this the right way to do this, or is there some other way to accomplish this?
Right now, I'm getting an error saying that it can't find a definition for .page.local, but I may be doing something else wrong.
Thanks, Paul ----- Paul Hodgetts -- Principal Consultant Agile Logic -- www.agilelogic.com Consulting, Coaching, Training -- On-Site & Out-Sourced Development Java, J2EE, C++, OOA/D -- Agile Methods/XP/Scrum, Use Cases, UI/IA
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
