[
https://issues.apache.org/jira/browse/WICKET-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eelco Hillenius updated WICKET-1428:
------------------------------------
Issue Type: New Feature (was: Bug)
../ has never been supported, and the main reason for that is/ was that it is
more difficult to assume which class loader is used. I'm not sure if it really
is a problem we can't overcome though, so we could make this a feature request.
> AutoLinkResolver Does Not Resolve Relative Links Correctly
> ----------------------------------------------------------
>
> 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
>
> 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.
