2011/8/29 Rick R <[email protected]> > What is driving me crazy though is "How would you accomplish this "without" > using cascade='true' ?" (In fact I think the application I'll eventually > have to integrate with is using a very old version of Tiles (1?) that > doesn't have cascade? ) > > You mentioned above "Either you define a new definition that uses > plainBody.jsp... ," which I 'think' I did in the above pastie with > "plain.body" and 'standard.body' definitions, but if I give it an attribute > of content which I expected to be overridden, it's not overridden. As an > example in the below I'll end up with "foo bar 2" as the content instead of > the 'signup' definition put-attribute content (if I remove cascade = true > on > the signup put-attribute .) > > <definition name="plain.body" > templateExpression="/WEB-INF/layouts/plainBody.jsp"> > <put-attribute name="content" value="foo bar 2"/> <!-- never really > overridden ??? --> > </definition> >
Probably, anonymous nested definitions best fits your needs: http://tiles.apache.org/2.2/framework/tutorial/advanced/nesting-extending.html#Anonymous_nested_definitions Antonio
