I haven't used this yet, I don't think. Likely case could be the code
that recognizes the ${ and } markers isn't smart enough and is
chopping the property expression up at the wrong location. Try using
an Output component and a prop: expression in the value parameter.
On Mon, Aug 8, 2011 at 2:42 PM, Igor Drobiazko <[email protected]> wrote:
> The prop expression has been updated in 5.3 to support maps. It looks like
> it's broken. None of the following expressions work inside a template:
>
> ${echoMap({ 1: 'one', 2.0: 'two' })}
> ${}
>
> According to the documentation they should work.
>
> http://tapestry.apache.org/property-expressions.html
>
> Did somebody try it already?
>
> --
> Best regards,
>
> Igor Drobiazko
> http://tapestry5.de
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
