[
https://issues.apache.org/jira/browse/WICKET-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Igor Vaynberg updated WICKET-1428:
----------------------------------
Fix Version/s: (was: 1.3.3)
1.5-M1
Assignee: (was: Igor Vaynberg)
ok, the reason your anchor works is that you actually go all the way up to the
root and construct what is essentially an absolute path from root to the
resource. this isnt really complete support for "relative urls"
the reason relative urls are hard with this is that the url ends up looking
like this
/context/resources/some.package.in.my.app.SomeClass/../../../../someResource.js
so there is a mismatch between our encoding of the class path with "." and
encoding of the relative path with "../"
the problem here is that the browser will act on ../../ and transform the path
before it even hits the server.
there are two ways i see to fix this. either encode "../" into something like
"wicket:up" in the url and then decode it back, or key the resources as
some/package/in/my/app/SomeClass in sharedresources instead of using class
name. both of these changes are quiet major and wont make it into 1.3x branch i
dont think. so we can put this off until 1.5 and see if anyone interested
provides a patch.
> 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.
