Description
Wicket is falling to find the page instance for its request when the named parameters order differs from page's PagePamameter#namedParameter.
MountMapper, for instance first, decodes query parameters after the ? sign before the named parameters encoded in the URL segments. So:
the URL: segument/example?cid=0
decoded by: new MountMapper(MyPage.class, "segment/${my_name}");
is decoded as: cid=0, my_name=example
While there is no guarantee, nor documented requirement, that the page should set named parameters in an specific order, Wicket should ignore it and map the request to the page instance regardless of the named parameters order.
Wicket 6 is not affected since this order test was add during WICKET-4441 to versions 7+
Attachments
Issue Links
- is related to
-
WICKET-6332 NullPointerException in PageParameters#equals()
-
- Resolved
-