Re: [Wicket-user] No Page found for component after selecting TreeNode

2007-04-09 Thread Isaac Weng
Thanks for the quick replay. After some digging, I found that I forgot to check that TreeItem is also a WebMarkupContainer which is rebuilt. A wrong way to re-implement my requirement in the Tree component let me think it worked on the Tree component in wicket-extension, which is obvious not af

Re: [Wicket-user] No Page found for component after selecting TreeNode

2007-04-08 Thread Matej Knopp
When tree node is selected the appropriate part of tree is rebuilt, which also involves recreating the components. So the component on which you're calling getPage() is no longer in hierarchy, thus the page returned is null. -Matej On 4/8/07, Isaac Weng <[EMAIL PROTECTED]> wrote: > Hi, > > Si

[Wicket-user] No Page found for component after selecting TreeNode

2007-04-08 Thread Isaac Weng
Hi, Similar to ILinkCallback of Tree in wicket-extension, I created a callback link which allows me to select a tree node in my custom Link component. After the link is clicked, the callback is executed and the node is selected. However, after selectNode() runs, getPage() in the Link compo