On Sun, 13 Mar 2005 09:55:00 -0500, Sean Schofield <[EMAIL PROTECTED]> wrote: > I have an issue where when a custom component is used in two different > pages and with Tiles. It seems that on postback everything is decoded > properly but then when the navigation rule kicks in, the new view is > loaded and the state information is lost. > > First question: In JSF is a navigation rule treated like a "fresh" > request. In other words, does it skip restore view phase just like > the the first time you load a JSF page? I suspect this is the case.
Yes. The only phase that is executed for the new page is Render Response. Think of the request processing lifecycle phases as being related to the *request*, and not to any given page. > My workaround for this at the moment involves storing the state > information that I want to preserve in the session. So once done > decoding I just stash what I need in the session map. Then before > encoding I pull it out of the session. Does this approach make sense? If you only need the information to prepare the new page on the current request, I would store it in request scope instead of session scope, so you don't have to worry about cleaning up after yourself. > > sean > Craig
