Michael has it right: in 5.0.5 the second will fail.
I logged a JIRA earlier, but as Martin kindly points out
this was fixed back in July!
There doesn't seem to be a 5.0.6-SNAPSHOT available though.
Cheers,
Nick.
Davor Hrg wrote:
shouldn't it be:
,
?
On 9/17/07, Michael Gottschalk
On Monday 17 September 2007 10:03:21 Davor Hrg wrote:
> shouldn't it be:
>
>
> ,
>
Yes, exactly, this will work. I just wanted to make clear that the problem is
not with expansions in general, but only when they are given to components as
parameters.
You are right, the solution to this p
shouldn't it be:
,
?
On 9/17/07, Michael Gottschalk <[EMAIL PROTECTED]> wrote:
>
> On Monday 17 September 2007 08:42:46 Davor Hrg wrote:
> > I had no problem using expansions in a loop, (T5.0.5)
> >
> >
> > ${value},
> >
>
> Expansions in a loop are only a problem if they
On Monday 17 September 2007 08:42:46 Davor Hrg wrote:
> I had no problem using expansions in a loop, (T5.0.5)
>
>
> ${value},
>
Expansions in a loop are only a problem if they are given as parameters to
components. E.g. your example will work, but the following will not:
,
On Mon, 2007-09-17 at 10:23 +0900, Nick Westgate wrote:
> It's mentioned somewhere (maybe in the source) that expansions are
> treated as literals, and therefore cached and never re-evaluated.
I'd think this is fixed with
https://issues.apache.org/jira/browse/TAPESTRY-1667, isn't it?
Cheers,
Marti
I had no problem using expansions in a loop, (T5.0.5)
${value},
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
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 co
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 tags).
> [...]
> This is what is in Menu.html
>
>
>
>context="${category.id}">${catego
I have a problem with the t:type="loop" component in my Menu Component
Every link that is generated gets the id of the first Category. So the html
source looks like this:
CategoryA
| 1
CategoryB | 70
CategoryC | 110
Every categoryId is 1. (an
