Here's my scenario... I want to create a component with an embedded form that has a textfield, and on submit, fires an Ajax request to the component. However, I have this idea that I'd like to let this component fire a custom event (using triggerEvent) back up to the page, and the page could tell another component on the page to go through the render lifecycle, because the info in this event warrants this other component to update it's content.
The technical hurdle with this approach, I think, is that when a component receives an AJAX event, it's the only thing that gets a chance to go through the rendering lifecycle... and I don't see anyway to somehow have another component to re-render too.One note: I'm avoiding using zone updates to orchestrate this cross-component behavior, because in my understanding, the bulk of the logic has to then live in Javascript in the client. But if that's what I have to do, OK... Thanks for any help! Seth -- View this message in context: http://www.nabble.com/In-Ajax-request-to-component-causing-another-component-a-chance-to-render-tp23599118p23599118.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
