[jira] Resolved: (WICKET-1019) Ajax tree strange behaviour when updating dynamically some nodes

["Matej Knopp (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matej Knopp resolved WICKET-1019.
---------------------------------

    Resolution: Invalid

This is not a bug in wicket, it's a wrong treemodel. The treenode does return true in isLeaf, because at the point when it's rendered, it has no children. The children are only added in Tree.onNodeLinkClicked, which is not the correct place to do it.

In order to implement dynamic tree model that loads tree children on demand, one has to implement the TreeNode directly, the DefaultMutableTreeNode doesn't  really help here.

> Ajax tree strange behaviour when updating dynamically some nodes
> ----------------------------------------------------------------
>
>                 Key: WICKET-1019
>                 URL: https://issues.apache.org/jira/browse/WICKET-1019
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.0-beta3
>         Environment: Windows XP Home Edition
>            Reporter: Yves Zoundi
>            Assignee: Matej Knopp
>         Attachments: quickstart.zip, screenshot-1.jpg
>
>
> Lots of people require lazy loading of a tree when there is a huge amount of data to load. The ajax tree has some bugs when nodes are populated dynamically. For example when you click on a node and trigger an event in your application to populate the node children if needed, the + sign is not shown in the tree. Wicket seems to be aware that the node now has children. However, if you expand the populated node, the + sign isn't displayed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.