I believe on the page lifecycle the "detach()" method is always called. The page lifecycle is from request to response so after every response the detach() method is call. I also believe that all 'non-persist' attributes are automatically set to null or initial value without work. Some things to watch for is declaritively persisting objects or injecting objects whos states dont change. I hope this helps.
Kevin On 3/29/06, Phillip Rhodes <[EMAIL PROTECTED]> wrote: > > I am using session persistent page properties that need to be cleared out > when the user leaves the page (goes to another tapestry page). > > Since there are many different menus, and exits from one page to the next, > it would be hard for me to programmatically call forgetPage at every exit > point. > > It would be nice if you could specify different lifecycles for a page > property, so that if the user left the page, all it's properties would > automatically be forgotten. > > There is a "flash" strategy, but due to the volumn of session data, this > will not work for me. > > I would be interested in hearing how others have solved this problem. > Thanks. > Phillip > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
