>> Actually, you can reach all the component's ancestor, if you do not >> return anything in the event handler.
That's not what I want as this is the problem: Only the ancestors. >> You can use eventlink to hit multiple components, but only one handler >> can return the final result. Eventlink triggers an event in one component that is then bubbling up the ancestor chain, or? So all the limitations I am talking about apply here. Feel free to correct me. > In addition, you could pass some object in the event context that would > aggregate Still only the ancestor chain. Even if you rethrow the event all the time and do a manual aggregation. > In my humble opinion, triggering an event for all components in a page would > be a bad thing with probably bad performance. This might be true. But what is the alternative. I don't get what you want to tell me with the Environment reference. I have not used it actively but what I understand: a) It works in a parent/child relationship. b) Components must be "rendered" to have a look into the environment. -> In my case that means: the event is catched by the page, an environment object is setup and all components are rendered to work with the environment. This can't be more efficient then going through the components to search for specific event handlers and only do partial renderings. > 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? I talk about partial renderings and events. I'll have a look anyway. Thanks, Markus > > -- > 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
