Just an idea: you could bind the component itself to a session scoped bean or save that bean with the <x:saveState> component between requests.
I have not tried this, but I guess that should avoid loosing the state between multiple requests even with page navigation.
- Antwort: Re: x:dataScroller how to preserve the state - ... mathias . werlitz
- Re: Antwort: Re: x:dataScroller how to preserve the... Werner Punz
- Antwort: Re: Antwort: Re: x:dataScroller how to... mathias . werlitz
- Re: Antwort: Re: Antwort: Re: x:dataScrolle... Werner Punz

