Hi, just wanted to ask what you guys think about a global server side event functionality in tapestry. Currently the events triggered by triggerEvent on ComponentResource just bubble up and halt when the first handler returns non null. It would be nice to have a event mechanism where matching handlers in all components on a page (not only the ancestors) are triggered, the results are collected and passed to the event triggering method.
The use case I have in mind is a page which has three components that each display different aspects of a group of users (one component listing all users of a group with details, one component with birth dates of the users and one component with twitter messages from the users). The "list of users" component has a delete button which deletes a specific user. This results into an Ajax request to the server and triggers a zone update of the user list. However the birthday and the twitter lists still show the previously deleted user, because the components on the server side aren't informed that they also need to refresh their zones. Ideally they have had received a server side event and contributed their zones to the Ajax event result. What do you think? Should I add a JIRA for this? Regards, Markus --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
