I had no problem using expansions in a loop, (T5.0.5)
<t:loop source="arr" value="value">
${value},
</t:loop>
Davor Hrg
On 9/17/07, Nick Westgate <[EMAIL PROTECTED]> wrote:
>
> It's mentioned somewhere (maybe in the source) that expansions are
> treated as literals, and therefore cached and never re-evaluated.
>
> The result is quite non-intuitive in a loop, which has irked me for
> some time, and I'm beginning to consider it a bug. It's also one
> reason I still value the Any component.
>
> I'll log a JIRA.
>
> Cheers,
> Nick.
>
>
> Michael Gottschalk wrote:
> > Hi Leon,
> >
> > On Sunday 16 September 2007 18:41:07 Leon Derks wrote:
> >> I have a problem with the t:type="loop" component in my Menu Component
> >>
> >> [...]
> >> Every categoryId is 1. (and it generates to much <ul> tags).
> >> [...]
> >> This is what is in Menu.html
> >>
> >> <ul t:type="loop" source="categories" value="category">
> >> <li>
> >> <t:actionlink t:id="category"
> >> context="${category.id}">${category.name} | ${category.id
> }</t:actionlink>
> >> </li>
> >> </ul>
> >
> > it will work if you don't use the expansion in the actionLink context
> > parameter:
> > <t:actionlink t:id="category" context="category.id">
> >
> > Never use the ${}-notation when giving parameters to a component. I
> don't know
> > why, but it will not work as expected.
> >
> > Regards,
> > Michael
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
