t:saveState is more like page-scope-plus. If you only use it on one page, then it's page-scope.
But if you add the same declaration to another page, then it'll carry over into that page as well. As long as the next page continues to reference the named saveState, then the value will be persisted. On 9/7/05, Dave <[EMAIL PROTECTED]> wrote: > Thanks. Is <x:saveState> session scope or page scope? > For examle, one page(JSP) uses <x:saveSate > to save a backing bean > property. Is it available to a different page using the backing bean > (request scope). Two bean instances because of request scope. > > > [EMAIL PROTECTED] wrote: > > > > Can <x:saveState> save any information about a backing bean(request > > scope) on server side? when a new backing bean is created, will it > > get the data saved with <x:saveState>? Thanks. Dave > > Yes, just place this in your DD. > > <context-param> > <param-name>javax.faces.STATE_SAVING_METHOD</param-name> > <param-value>server</param-value> > </context-param> > > > ________________________________ > Click here to donate to the Hurricane Katrina relief effort. > >
