We should probably clarify that in the docs, it's always been my assumption
you needed to use a component id with zones which you can can't dynamically
set. Thanks Thiago.
On Thu, Feb 19, 2015 at 1:27 PM, Thiago H de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Thu, 19 Feb 2015 16:19:54 -0200, George Christman <
> gchrist...@cardaddy.com> wrote:
>
> <t:zone t:id="countZone" id="${compId}">
>>
>
> Never, never, never ever use ${} expansions when binding Tapestry
> parameters. In 100% of the cases, it's either harmless, but philosophically
> wrong (as in this case, where the parameter type is String) or
> completelywrong (when the parameter type isn't a String). id="prop:compId".
>
> In addition, I'd prefer to give the zone an id different from the
> component surrounding it, in case the component itself needs an id in the
> future. Just a suggestion.
>
>
> --
> Thiago H. de Paula Figueiredo
> Tapestry, Java and Hibernate consultant and developer
> http://machina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
--
George Christman
CEO
www.CarDaddy.com
P.O. Box 735
Johnstown, New York
