AW: Very strange problem with expansion of ${name}

2008-12-10 Thread Maximilian Weißböck
Oh, I see... yes, its Maven... Thanks, Max > -Ursprüngliche Nachricht- > Von: Andreas Andreou [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 10. Dezember 2008 13:51 > An: Tapestry users > Betreff: Re: Very strange problem with expansion of ${name} > > are you runnin

Re: Very strange problem with expansion of ${name}

2008-12-10 Thread Joakim Olsson
> Is there a special meaning to the expansion of ${name} ? > > Cause I have a very strange problem. > > If I use ${getNode().getName()} in my template, all is ok. > If I use ${node.getName()} in my template, all is ok. > > If I use ${node.name} I do not get the expected value, instead > the name of

Re: Very strange problem with expansion of ${name}

2008-12-10 Thread Andreas Andreou
are you running this with maven? If you've set it to filter the resources, that may be the cause. On Wed, Dec 10, 2008 at 2:28 PM, Maximilian Weißböck <[EMAIL PROTECTED]> wrote: > Is there a special meaning to the expansion of ${name} ? > > Cause I have a very strange problem. > > If I use ${getNo

Very strange problem with expansion of ${name}

2008-12-10 Thread Maximilian Weißböck
Is there a special meaning to the expansion of ${name} ? Cause I have a very strange problem. If I use ${getNode().getName()} in my template, all is ok. If I use ${node.getName()} in my template, all is ok. If I use ${node.name} I do not get the expected value, instead the name of the applicati