Hi, > I think you have a concept mistake. When you come back from one page to > another, a complete faces cycle is executed. Thus, the RENDER_VIEW IS > executed and a new view is created. You can think the previous stored page > is restored, but that's not true. If you use x:savestate you can store > from > a single attribute to a complete view (mostly data values) but in restore > view phase a complete new view is created (a new component tree). Then, > you > must recreate the dynamic components or store it and restore manually > (savestate or another custom component storage).
Ah, that would explain the behaviour. So, every time I leave a view, that one is destroyed *completely* and re-entering it does not lead to calls to restoreState, right? I am a bit confused, because when leaving the view I can see calls to saveState and that means that this data will not be used then. Thanks, Uli -- Ulrich Teichert Stormweg 24 24539 Neumünster, Germany Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen! Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
