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 after some serious thought.
Seems like I asked a dumb question, hah Isaac Matej Knopp wrote: > 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, >> >> 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 component results in "No Page found for component". Following is a >> brief sample code: >> ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
