On 03/01/2004 06:12 PM Axel Groß wrote:
On 2004-03-01 at 17:53:30 +0100, Adam Hardy wrote:
I see the need for extending the entries of a putList without overriding the entries in the super definition.
Example:
<definition name=".head.common" path="htmlHead.jsp">
<putList name="httpEquiv">
<item value="pragma" link="no-cache" />
<item value="cache-control" link="no-cache" />
<item value="expires" link="0" />
</putList>
</definition>


<definition name=".head.project" extends=".head.common">
<putList name="httpEquiv">
<item value="expires" link="1" />
<item value="description" link="tiles definition extension example" />
</putList>
</definition>
so usually this would replace the list in .head.common with the one in
.head.project
desired behaviour would be to just add the new entries ("description") and overwrite those which are already present ("expires").

this is the behaviour that I use already. I don't know how you manage to replace the list.

so you would actually get for .head.project the "pragma" and "cache-control" values? I'd be really surprised.. (i don't get them)


My definitions inherit the list and its contents. (I am not sure about replacement).

mine do too. So for clarification: what happens if you do putList on a name you already did a putList in the superdefinition?

Ah. I spoke too soon. Sorry. I do name the lists seperate names - that's why. I name blah1, blah2, blah3. So you're right, it would be good to be able to inherit and add to the same name.


Adam
--
struts 1.1 + tomcat 5.0.16 + java 1.4.2
Linux 2.4.20 Debian


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to