On Thu, 23 Sep 2010 11:32:09 -0300, Markus Joschko
<markus.josc...@gmail.com> wrote:
Eventlink triggers an event in one component that is then bubbling up
the ancestor chain, or?
It bubbles up in the ancestor chain until the callback passed to the
triggerEvent method says the event was handled.
Still only the ancestor chain. Even if you rethrow the event all the
time and do a manual aggregation.
You don't need to retrigger the event. See comment above.
You can use the Environment to
make components communicate in ways that triggering events can't. Look
at how validation works for form fields.
Can you be more specific what I should pay attention for? Isn't
validation done when the page is fully rendered?
No. It is done when the form is submitted (which is an event too). The
form fields store commands in an object in the Environment that is put in
a hidden field by Form. Later, when the form is submitted, Form executes
these commands.
--
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: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
