On Fri, 27 Jan 2012 11:32:36 -0200, Denis Stepanov
<[email protected]> wrote:
Zone with an id generated randomly(ajax request) is useless
It isn't (I've explained it in this thread:
http://www.mail-archive.com/[email protected]/msg57958.html),
otherwise Tapestry committers wouldn't care to implement.
You have only explained why there are random ids, I'm not saying there
are bad just in this case a zone with a random id is useless.There is
only one way how to use random id zone is to extract its id after
rendering and honestly I don't think is the right way.
Just provide a client id and Tapestry won't change it.
Most developers will not understand why a zone inside a zone doesn't
work without knowing all nuances, some kind of warning or even error
which will tell to provide explicit id whould be nice.
I agree that the documentation should warn about components without
developer-provided ids inside zones.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
