[
https://issues.apache.org/jira/browse/WICKET-1428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12596798#action_12596798
]
James Carman commented on WICKET-1428:
--------------------------------------
Peter,
I'm not a big fan of the "wicket:up" string, since it's too verbose. But, I
agree we should pick something that means "go up one level" and just use that.
You didn't like the idea of using two colons "::"? Colons are already used in
Wicket, so it might kind of stick with the "theme" better. I'm glad you did
some of the legwork on this (I had no idea where to look). It seems like an
easy fix. We'd just need to unit test the heck out of it so that we don't
break stuff (and nobody else breaks it in the future).
> 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-use-wicket-up.patch, 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.
