On Oct 25, 2006, at 6:01 PM, Chris Pratt wrote:
Greg, to answer your question, "how do I think this should work?" One
improvement I can think of would be to allow this type of
construct. In the
tiles-defs.xml, specify a definition like:
[snip]
Then allow inserting, referencing and populating in one fell swoop,
something similar to:
<%@ taglib prefix="tiles" uri="http://struts.apache.org/tags-tiles-
el"%>
<tiles:insert definition="site.layout">
<put name="header" value="/tiles/index-header.jsp"/>
<put name="body" value="/tiles/index-body.jsp"/>
<put name="footer" value="/tiles/index-footer.jsp"/>
</tiles:insert>
which right now ignores all the puts in the body of the insert and
just
inserts the definition. This would allow you to separate the reusable
definitions from the single use pages.
Thanks, that helps a lot. I think there's a lot of people out there
who would like it to work this way. We've had some discussions on
the dev list about restructuring the tags in Tiles 2. The problem is
that the <tiles:insert> tag means multiple things. In some cases it
means "insert this definition here" (like your example above). In
other cases it assumes you are "inside" a definition template and it
means "insert the specified attribute here". I can see what you mean
about trying to insert a definition on the fly instead of defining it
in the XML file. Have you tried using the <tiles:definition> tag?
Greg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
