Thiago, PageDetached fires when the instance of the page used to service the request gets returned to the page pool. It doesn't have anything to do with the user navigating away from a page.
The problem is, with Forward and Back buttons, navigating away from a page is a browser-side event. Different frameworks have tried various ways to stop the back-button from breaking applications. It's one of the big reasons that T5 moved to the redirect-after-post pattern. Jonathan > -----Original Message----- > From: Thiago H. de Paula Figueiredo [mailto:[EMAIL PROTECTED] > Sent: Friday, October 24, 2008 14:29 > To: Tapestry users > Subject: Re: Trapping the "user is on a new page event" and calling > ComponentResources.discardPersistentFieldChanges() on new page? > > Em Fri, 24 Oct 2008 14:21:05 -0300, Joel Halbert <[EMAIL PROTECTED]> > escreveu: > > > Hi, > > > > Is there a hook you can leverage to trap an event when the user > > navigates to a new page? > > I didn't understand how different this situation would be from simply > catching the end of the rendering of a page. This would be the > @CleanupRender event or, maybe better, the @PageDetached event. All the > component events are described here: > http://tapestry.apache.org/tapestry5/guide/rendering.html and the page > events here: > http://tapestry.apache.org/tapestry5/guide/lifecycle.html. > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
