[
https://issues.apache.org/jira/browse/WICKET-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524267
]
Matej Knopp commented on WICKET-914:
------------------------------------
Hi, thanks for quickstart. This was indeed a bug in Tree, where the root node
change was not properly detected. It should be fixed now. I also added
convenience updateTree() method, which takes care of looking up the
AjaxRequestTarget during ajax response, so it can be called from a
TreeStateListener handler.
Thus to "fix" your example, you'll have to:
change
bTree.invalidateAll() to bTree.updateTree() in your
ATreeStateListener.nodeSelected();
remove
nodeStructureChanged(root);
nodeChanged(root);
from BTreeModel.setData, as the model takes care of it automatically.
> Tree not "redrawn" when resetting root node
> -------------------------------------------
>
> Key: WICKET-914
> URL: https://issues.apache.org/jira/browse/WICKET-914
> Project: Wicket
> Issue Type: Bug
> Components: wicket-extensions
> Affects Versions: 1.3.0-beta2
> Reporter: Doug Leeper
> Assignee: Matej Knopp
> Fix For: 1.3.0-beta4
>
> Attachments: wicketTest-src.jar
>
>
> I have a tree that I reset the root node when a user selects on another
> component (Component A). However, the tree is not "redrawn" until I click on
> the tree (the previous tree contents are shown).
> Have called Tree.invalidateAll() and
> DefaultTreeModel.nodeStructureChanged(tnode )
> DefaultTreeModel.nodeChanged( tnode )
> DefaultTreeModel.reload()
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.