You could try mounting /mount/tree first and then /mount Not sure if that will help, but I think the order of the mounts is relevant in lookups.
Martijn On Fri, Jun 6, 2008 at 3:56 AM, David Leangen <[EMAIL PROTECTED]> wrote: > > I've been stepping through the code, but I'm having a tough time > figuring this one out... > > Using 1.3. > > I have one page mounted on: > > /mount1 > > And another mounted on: > > /mount1/tree > > On the /mount1/tree page, I have a tree component. > > Problem is that whenever I click on a node in the tree, I am taken to: > > /mount1/mount1 > > Which is obviously a problem. :-) > > Even when I explicitly use setPageResponse using the current page as my > parameter in onNodeLinkClicked, the problem persists. So there seems to > be some kind of problem handling the target. > > Any hints would be really appreciated. > > > Thank you! > David > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.3 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
