Yes, in my last message I did the following
<e:attributeNames var="attributes"/><t:insertAttribute name="${format}">
<c:forEach items="${attributes}" var="attribute"> <t:putAttribute
name="${attribute.key}" value="${attribute.value}"/>
</c:forEach></t:insertAttribute>
> Date: Wed, 16 Apr 2008 17:11:21 +0200> From: [EMAIL PROTECTED]> To:
> [email protected]> Subject: Re: Iterate through Attributes> > 2008/4/15,
> JRD <[EMAIL PROTECTED]>:> > <tiles:insert definition="${definition}">> >
> <tiles:put name="viewFormat" value="${viewFormat}"/>> > <c:forEach
> items="${theTiles.attributeNames}" var="attribute">> > <tiles:put
> name="${attribute}"><tiles:getAsString> > name="${attribute}"/></tiles:put>>
> > </c:forEach>> > </tiles:insert>> > About this particular piece of code
> (once translated to Tiles 2 tags),> it does not work since the
> <tiles:getAsString> tag is inside a> <tiles:insertDefinition> tag, that
> creates a new attribute context.> I am trying to understand if it can be
> corrected or not (in the sense> that this behaviour is correct). I think it
> is a bug, but I am trying> to understand what is the best way to fix it,
> without adding too much> complexity.> > Antonio
_________________________________________________________________
Get in touch in an instant. Get Windows Live Messenger now.
http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008
