[ https://issues.apache.org/jira/browse/WICKET-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588716#action_12588716 ]
James Carman commented on WICKET-1428: -------------------------------------- I don't see a problem with URLs like: resources/markup.level1.level2.level3.page.TestPage/../../../../base.js The ../ when dealing with a class name (such as we have here) means to go up to the parent package to look for the package-relative resource. Correct? To me, it's just a matter of making the resource handling logic understand resource URLs with this ../ stuff in it. Again, I'm no expert on the internals of Wicket like you folks. This is just my view from the outside. > AutoLinkResolver and Parent-Relative (../) Links > ------------------------------------------------ > > Key: WICKET-1428 > URL: https://issues.apache.org/jira/browse/WICKET-1428 > Project: Wicket > Issue Type: New Feature > Components: wicket > Affects Versions: 1.3.2 > Reporter: James Carman > Fix For: 1.5-M1 > > Attachments: WICKET-1428.patch, wicket-link-outside-of-package.zip > > > 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> > This is not working, however. The AutoLinkResolver spits out a warning > message: > "WARN - AutoLinkResolver - Did not find corresponding java class: > .....module2.page.Page2" -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.