Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 1.8DR#1
-
Component/s: ICE-Components
-
Labels:None
-
Environment:All
Description
Tree's navigatedNode currentNode fields are both DefaultMutableTreeNode objects, which means that trying to save the last selected or expanded node info, may serialize the entire tree model (twice). That could also entail a memory leak, if the model changes, while these two fields continue referencing the old model's nodes. We need to instead be storing some kind of path expression, and just look up the nodes as needed.
Issue Links
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
We have added the save/restore support to for the "navigatedNode" using the "navigatedNodePath". Considering the fact that the "navigatedNode" is a public property and might be accessed by the application code.
trunk: revision 17859
Show
Adnan Durrani
added a comment - We have added the save/restore support to for the "navigatedNode" using the "navigatedNodePath". Considering the fact that the "navigatedNode" is a public property and might be accessed by the application code.
trunk: revision 17859
It came across that both the "navigatedNode" and the "currentNode" do not need to saved/restore.
Reason:
The "navigated node" property has never being accessed. However the decode method of the Tree component do the lookup of the "navigated node" using the "navigatedPathNode" sent by the client, to just to flip the Expended state. So it doesn't require state variable.
The "currentNode" is a state variable which represents the current processing node, which is set inside the iteration and its not required after JSF lifecycle completes.