Antonio, I had the same problem when upgrading from Struts 2.0.6 to Struts 2.0.9.
If I get you right, it breaks down to: you can extend templates, but not tiles. Templates can represent whole pages or parts of them. To use templates as tiles (i.e. for a sub-page), you need a separate definition to fill the attributes of that template. And only such a definition can be used as a tile in the page definition which may extend the master template. Is that right? But this behaviour is different to that of the Tiles plugin of Struts 2.0.6. There it was possible to extend a master template in various levels into more specialized templates adding extra attributes and sub-page templates on the way while being able to overwrite any attribute of any previous level. Is there a special reason for that change? Antonio Petrelli-3 wrote: > > 2007/7/31, Neil Aggarwal <[EMAIL PROTECTED]>: > > The solution is in the second sentence of the FAQ: > > <snip> > In this case, usually you have to create a new definition extending > from an existing one, fill the attribute in the correct template and > assign the new definition as an attribute to the main template. > </snip> > > In other words: > > <definition name="product.nav" template="/productNavLayout.jsp"> > <put-attribute name="productPathNav" value="/productPathNav.jsp" /> > <put-attribute name="productNav" value="/productNav.jsp" /> > </definition> > > <definition name="product.nav.extended" extends="product.nav"> > <put-attribute name="productContent" value="product.grid" /> > </definition> > > <definition name="page.products" extends="layout"> > <put-attribute name="content" value="product.nav.extended" /> > </definition> > > HTH > Antonio > -- View this message in context: http://www.nabble.com/Nesting-tiles-3-levels-deep-not-finding-attribute-tf4179213.html#a13087898 Sent from the tiles users mailing list archive at Nabble.com.
