It is correct, and there is nothing special you should do, if your TreeModel
is correctly implemented (=it reflects the change).
If it doesn't, it means that the TreeModel which you set to the tree is
holding stale data, you need to correct that.
-Matej
On 8/30/07, Doug Leeper [EMAIL PROTECTED]
After further evaluating what I need done...I don't believe I need AJAX.
The Tree Node needs to be updated to reflect a data change, i.e. name.
However, the name change occurs in a page...not in the same page as the
tree.
Am I correct in this...no AJAX is needed since I am changing Pages?
If
On Tue, 21 Aug 2007, Doug Leeper wrote:
As I am new to Ajax and Wicket, I am not sure what the target would be. Is
this the node, the user object, or something else? Do I need to configure
anything to get Ajax to work?
It is the AjaxRequestTarget object which is passed to all
Ajax event
Your treemodel must fire the appropriate treeNodesChanged events on
the listeners. And then you need to call
tree.updateTree(ajaxRequestTarget);
-Matej
On 8/20/07, Doug Leeper [EMAIL PROTECTED] wrote:
I am using the TreeTable in Wicket Extensions. When selecting on a node, a
page allowing
I am using the TreeTable in Wicket Extensions. When selecting on a node, a
page allowing the user to edit the node value (and other useful info). Upon
saving, I would like the associated TreeNode to show the new value. How
would one go about having the TreeNode get its value again?
Thanks
--
