[
https://issues.apache.org/jira/browse/WICKET-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12588811#action_12588811
]
jwcarman edited comment on WICKET-1428 at 4/14/08 3:01 PM:
---------------------------------------------------------------
Could you use a URL parameter to specify the path?
resources/markup.level1.level2.level3.page.TestPage?path=/../../../../base.js
Also, I've never really liked the fact that we have the classname in the URL.
Could we use something to replace the "scope" of the resource URL with some
constant (and it would be remembered for subsequent invocations)? Basically,
we'd have a bidi-map that goes from some generated string <-> class name or
something?
was (Author: jwcarman):
Could you use a URL parameter to specify the path?
resources/markup.level1.level2.level3.page.TestPage?path=/../../../../base.js
> 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.
