[jira] [Updated] (WICKET-4330) Non standard ("wicket") namespace causes incorrect relative URL in certain cases

["Chris Colman (Updated) (JIRA)" <ji...@apache.org>]

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

Chris Colman updated WICKET-4330:
---------------------------------

    Attachment: nonStdNamespaceBug.zip

Quickstart - uses port 80, not 8080!
                
> Non standard ("wicket") namespace causes incorrect relative URL in certain cases
> --------------------------------------------------------------------------------
>
>                 Key: WICKET-4330
>                 URL: https://issues.apache.org/jira/browse/WICKET-4330
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.5.3
>         Environment: Win XP, 4GB RAM, Tomcat 6, Java 6
>            Reporter: Chris Colman
>              Labels: wicket
>         Attachments: nonStdNamespaceBug.zip
>
>
> The problem is related to non standard (i.e. "wicket") namespaces.
> In my quickstart if I change the namespace in all markup from "wicket"
> to "foobar" then the BPL which has only the last segment differing from the current page ends up producing an incorrect link to another page in the same path.
> i.e.
> Browser is at this page:
> http://127.0.0.1/content/other/o/1234/aspect/fred
> <p>
> 	Here's a relative link to another page in the same 'path'
> 	<div>
> 		<a foobar:id="janeLink" href="../../../../../jane"
> style="outline: 0;">
> 			jane
> 		</a>
> 	</div>
> </p>
> <p>
> 	A link to the current page
> 	<a foobar:id="fredLink" href="fred">fred</a> </p>
> The above BPL href of ../../../../../jane is wrong.
> With 'wicket' set as the namespace the 'jane' BPL outputs 'jane' which is correct.
> This same code worked with the non standard namespace under 1.4.x
> Attached quickstart demonstrates the issue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira