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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.3
• Fix Version/s: 1.5.5, 6.0.0-beta1
• Component/s: wicket
• Labels: wicket
• Environment: Win XP, 4GB RAM, Tomcat 6, Java 6
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Chris Colman
• Created: 10/Jan/12 09:45
• Updated: 21/Oct/12 19:50
• Resolved: 11/Jan/12 13:01

Description

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.