On 2004-03-01 at 17:53:30 +0100, Adam Hardy wrote:
> On 03/01/2004 02:37 PM Axel Gross 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").
>
> Axel,
Hi Adam!
> this is the behaviour that I use already. I don't know how you manage to
> replace the list.
??? *puzzled*
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?
>
> Adam
Axel
> --
> struts 1.1 + tomcat 5.0.16 + java 1.4.2
struts 1.1 + tomcat 5.0.19 + java 1.4.2_03
> Linux 2.4.20 Debian
winXP home ed
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
