[
https://issues.apache.org/jira/browse/WICKET-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530867
]
mrcheeks edited comment on WICKET-1019 at 9/27/07 4:03 PM:
--------------------------------------------------------------
Here is a maven quickstart project to reproduce the bug to create an archetype
and run the project, please do the following.
mvn archetype:create -DarchetypeGroupId=homeip.net.mrcheeks.wicket.ajaxapp
-DarchetypeArtifactId=quickstart -DarchetypeVersion=1.0-SNAPSHOT
-DgroupId=com.mycompany -DartifactId=myproject10
You can run the project with the command
mvn jetty:run
You can see the website at the address : http://localhost:9090/
was (Author: mrcheeks):
Here is a maven quickstart project to reproduce the bug to create an
archetype and run the project, please do the following.
mvn archetype:create -DarchetypeGroupId=homeip.net.mrcheeks.wicket.ajaxapp
-DarchetypeArtifactId=quickstart -DarchetypeVersion=1.0-SNAPSHOT
-DgroupId=com.mycompany -DartifactId=myproject10
You can run the project with the command
mvn jetty:run
> 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
> Attachments: quickstart.zip
>
>
> 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 if
> you expand it, but 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.
