I was planning on finding the phases where I can successfully run zone.getClientId() to acquire it's client id. Then in the ajax handler method, I can use the AjaxResponseRenderer to render the zone using it's correct ID (Since I couldn't predict it because I couldn't assign it my self and it always had a suffix added by Tapestry)
*---------------------* *Muhammad Gelbana* http://www.linkedin.com/in/mgelbana On Tue, Aug 12, 2014 at 3:23 PM, Thiago H de Paula Figueiredo < thiag...@gmail.com> wrote: > On Tue, 12 Aug 2014 06:34:29 -0300, Muhammad Gelbana <m.gelb...@gmail.com> > wrote: > > I mixed between component events and rendering phases. I always thought >> that component render phases are fired events by default but I was wrong. >> >> This answer cleared up a lot: >> http://stackoverflow.com/questions/25213133/5-4-beta-6- >> zone-event-handler-isnt-called >> > > I'd add that there's a difference between component render events > (afterRender, etc) and other events (I'd call that action events). > Component render events are not bubbled, while action one does, and this > explains why your code didn't work. > > RenderNotification is a mixin listens for the beginRender and afterRender > component render events and triggers an action event. > > Everything here is completely unrelated to ids, t:id or HTML. > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
