That's funny, I was about to post regarding the numerous issues with <wicket:link>...
And one suggestion I was going to give was to add support for "../packge/Page.html". I don't think it currently supports this, at least I couldn't see it from a code examination. Your only option, I believe, is to resort to absolute path... "/com/mycompany/myproject/module1/page/Page1.html" or ".com.mycompany.myproject.module1.page.Page1.html" This of course breaks if you refactor your packages. BTW, this absolute path syntax is not documented anywhere I could find. Not even in the WIA book. I found it only be going to the source. My thinking is that <wicket:link> works great if you keep all your pages in the same package, but has numerous issues if you separate your pages into their own packages, as I have done. I think the uber feature would be to have it search the entire classpath (if not found in the "current pages" package). This would solve the issue of <wicket:link> paths breaking when pages are refactored to other packages. Phil On Sun, Mar 16, 2008 at 11:07 AM, James Carman <[EMAIL PROTECTED]> wrote: > Suppose I have a package structure like this... > > com.mycompany.myproject > --- module1 > ------- page > --------- Page1.html > --- module2 > ------- page > --------- Page2.html > > If I want to autolink from Page1.html to Page2.html, it would look like: > > <wicket:link> > <a href="../../module2/page/Page2.html">Click Here!</a> > </wicket:link> > > Correct? This doesn't appear to be working for me. I get a warning > from AutolinkResolver: > > "WARN - AutoLinkResolver - Did not find corresponding java > class: .....module2.page.Page2" > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Phil Grimm Mobile: (858) 335-3426 Skype: philgrimm336
