Let me explain again how the wildcard works:
<definition name="home/*"> creates a lot of definitions, not just one.
In all attributes, {1} will be replaced by the value of the *.
That means the above declaration defines the definition "home/start",
too, and {1} will be replaced by "start" everywhere. No need to extend
the definition for that: it's done already.
Now why do you get an error? Because when you cannot write
"extends='home/*'": 'home/*' is not a definition, it is a wildcard
pointing to many different definitions.
Hope this helps,
Nick
On 12-04-11 12:50 PM, Ninju Bohra wrote:
My problem is slightly different. I am getting an error when I try to extends a
wildcard<definition> in the following manner:
<!-- Creating Tile definitions for all the home pages via simple wildcards
(*) -->
<definition name="home/*" extends="template-home">
<put-attribute name="page_css" value="/css/{1}.css"/>
<put-attribute name="page_js" value="/js/{1}.js"/>
<put-attribute name="primary-content"
value="/WEB-INF/pages/home/{1}.jsp"/>
</definition>
<definition name="home/start" extends="home/*">
<put-attribute name="primary-content"
value="/WEB-INF/pages/home/start.jsp"/>
</definition>
