Re: Antwort: Re: Antwort: Re: x:dataScroller how to preserve the state - finally solved

[Werner Punz <we...@gmx.at>]

mathias.werlitz@daimlerchrysler.com wrote:
> 
> Thanks for the info. Important to know.
> But I would expect this behavior, because the component and its state 
> should be preserved with the instance in the bean.
The problem is not that the component does not preserve the state, but 
the problem is much deeper in the request cycle.
The problem is, if you send an request which is not covered by the 
faces-config navigation, a simple refresh, the datamodel is basically 
the same between encodebegin and encodechildren

if you do it over a faces-config nav refresh, the datamodel gets 
rendered and then is lost to the scroller, for some strange kind of reason.

So what happens, the state basically is preserved, but the datamodel 
gets lost between two rendering phases.