Antwort: Re: Antwort: 1.0.9 -> 1.1.1 : tree2 node state

[mathias . werlitz]

Yes, that was the problem.

[EMAIL PROTECTED] schrieb am 28.11.2005 11:53:03:

> Hmm ... so it was saving the node state in session the whole
> time, even when javax.faces.STATE_SAVING_METHOD was set to
> client?
>
> danke
>
> ---- Original message ----
> >Date: Mon, 28 Nov 2005 11:46:47 +0100
> >From: [EMAIL PROTECTED]  
> >Subject: Antwort: 1.0.9 -> 1.1.1 : tree2 node state  
> >To: users@myfaces.apache.org
> >
> >   If you leave the view ... than you have a new view
> >   and the state of tree is also a new one.
> >   No other component (afaik) does maintain the state
> >   over several views. The tree did save the state in
> >   1.0.9 in the session ... that made it possible to
> >   maintain the state. But this pollutes the session
> >   memory.
> >   If you use the client-side toggle you can use
> >   preserveState=true instead or if you use server-side
> >   toggle you can provide a session scoped TreeModel
> >   (and return TreeState.isTransient() -> true). That
> >   way you can maintain the state on your own.
> >
> >   [EMAIL PROTECTED] schrieb am 25.11.2005 21:51:29:
> >
> >   > Using 1.0.9, the following maintains node state
> >   very well:
> >   > node state is preserved even after users leave the
> >   view and
> >   > come back.  After moving to 1.1.1, this only
> >   happens when the
> >   > back button is pushed. Can anyone give me a high
> >   level idea
> >   > as to what has changed?
> >   >
> >   > <t:tree2 showRootNode="false" id="tree"
> >   >    value="#{officeTreeBacker.tree}" var="node"
> >   >    varNodeToggler="t" clientSideToggle="false">
> >   >
> >   > Dennis Byrne
>
> Dennis Byrne