You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Juergen Donnerstag (JIRA)" <ji...@apache.org> on 2010/12/30 19:19:45 UTC

[jira] Resolved: (WICKET-3281) autolink doesn't work with relative paths in borders

     [ https://issues.apache.org/jira/browse/WICKET-3281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Juergen Donnerstag resolved WICKET-3281.
----------------------------------------

    Resolution: Invalid

relativ autolinks are always resolved against the Page. If one is a.b.Page1 and the other a.b.c.Page2 than relative links don't work in one or the other. Please use normal *Link Components instead. Autolinks can make life easier in certain use cases, but we do not aim to make them work in each and every situation.

> autolink doesn't work with relative paths in borders
> ----------------------------------------------------
>
>                 Key: WICKET-3281
>                 URL: https://issues.apache.org/jira/browse/WICKET-3281
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.14
>            Reporter: Anatoly Kupriyanov
>            Assignee: Juergen Donnerstag
>         Attachments: wicketbug.tgz
>
>
> Take the "navomatic" wicket example and move the Page2.java and Page2.html into an another java-package - relative paths in the NavomaticBorder.html will be resolved incorrectly, they resolved against current page, but not against NavomaticBorder.html.
> So, I cannot use autolink functionality from bordes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.