[
https://issues.apache.org/jira/browse/WICKET-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588950#action_12588950
]
Johan Compagner commented on WICKET-1428:
-----------------------------------------
we chould use a param, but then only for these situations.
if you dont want the classname you can set an alias for that thats already
possible for a long time. (or really mount it)
and no we cant just generate that and remember it because a shared resource is
dynamically generated on the fly
so
/resources/xxxxx.Yyyyy/foo.js
has to work also if the app server just restarted without any hit yet to the
resource yet (so it isn't rendered through a page yet)
Then purely that url has to be able to resolve the resource.
So if you make something make sure that that is working, that the resource can
be created and found by just the information that you have in the url and
nothing more.
> 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.
