You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Pedro Santos (JIRA)" <ji...@apache.org> on 2016/11/21 03:16:58 UTC

[jira] [Created] (WICKET-6283) Page parameter equality should not depend on named parameters order

Pedro Santos created WICKET-6283:
------------------------------------

             Summary: Page parameter equality should not depend on named parameters order
                 Key: WICKET-6283
                 URL: https://issues.apache.org/jira/browse/WICKET-6283
             Project: Wicket
          Issue Type: Bug
    Affects Versions: 7.5.0, 8.0.0-M2
            Reporter: Pedro Santos
            Assignee: Pedro Santos


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+



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)