[ http://issues.apache.org/jira/browse/MYFACES-438?page=comments#action_12319986 ]
Mathias Werlitz commented on MYFACES-438: ----------------------------------------- #1 If we just persist the selected node with the component this part of the component state is lost, when the same model is used with another component ... as it is the case when opening another page. If the user supplies a session scoped TreeModel the state including the selected node can be reused. #2 This idea came to my mind because if the tree2 is used in client mode we use cookies to store the state of the component first on the client and then sync the server state with it. Because of this the user does not have to provide a session scoped model and the expand/collapse state still can/must be restored from the cookie if another page is opend. Storing the selected node as well in a cookie would free the user in client mode from providing a session scoped TreeModel (incl. TreeState). Otherwise he would have to like in #1. Anyway in my point of view the current TreeModel and TreeState is not thread-save (but has to be when used in session scope) ... we should note that. But this is another issue ... > [tree2] Selected node is lost when navigating to another page > ------------------------------------------------------------- > > Key: MYFACES-438 > URL: http://issues.apache.org/jira/browse/MYFACES-438 > Project: MyFaces > Type: Bug > Components: Tomahawk > Versions: Nightly Build > Environment: Window 2000 pro, JSF, Sun RI, Nightly Build 09-Aug-2005 > Reporter: Marc Vandeloise > Assignee: sean schofield > > I have the preserveToggle=true which is supposed to keep the state > of the tree2 navigator when openning another page... but it always > collapse... > The issue still persist with Nightly Build 19-Aug-2005 > From: Sean Schofield <[EMAIL PROTECTED]> > --- > There was a recent change to tree2 that may have broken this feature. > Are you using a recent (with 7-10 days) version of the source code? > If so, then please file a JIRA issue. This is most likely a bug that > was introduced by the new TreeModel and TreeState interfaces. > sean > ------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
