[ https://issues.apache.org/jira/browse/TOBAGO-1107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402205#comment-13402205 ]
Hudson commented on TOBAGO-1107: -------------------------------- Integrated in tobago-trunk #807 (See [https://builds.apache.org/job/tobago-trunk/807/]) TOBAGO-1107: Using a TreeState object instead of "expanded" and "marked" in the tree node tag - do not update expanded state, if the field wasn't sent. (Revision 1354456) Result = SUCCESS lofwyr : http://svn.apache.org/viewvc/?view=rev&rev=1354456 Files : * /myfaces/tobago/trunk/tobago-theme/tobago-theme-standard/src/main/java/org/apache/myfaces/tobago/renderkit/util/RenderUtils.java > Using a TreeState object instead of "expanded" and "marked" in the tree node > tag > --------------------------------------------------------------------------------- > > Key: TOBAGO-1107 > URL: https://issues.apache.org/jira/browse/TOBAGO-1107 > Project: MyFaces Tobago > Issue Type: Task > Components: Core > Reporter: Udo Schnurpfeil > Assignee: Udo Schnurpfeil > Fix For: 1.6.0-beta-1, 1.6.0 > > > The expanded and marked state was saved in the tree model directly since > Tobago 1.5.0. > But it turns out, that has some disadvantages: > - to handle the state, you may have to write extra code to save the state > - usually this code is only for presenation (expanded), so you mix data and > presentation > So introducing the TreeState. The TreeState shoud be independet from tree > model implementations. It saves the path a node, instead of the node > themself. This is different to the TreeState of Tobago 1.0.x. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira