[
https://issues.apache.org/jira/browse/WICKET-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537881#comment-14537881
]
Guillaume Smet commented on WICKET-5903:
----------------------------------------
Hi Andrea,
I confirm you fixed the reported case but it was a self contained test case
which was over simplified.
The issue in our application isn't fixed with the latest snapshot.
I worked on a more complete test case: you'll see that there's still something
fishy: when you click on the second link, you end up on the third page and when
you click on the third link, you end up on the general page.
Feel free to ping me if there's something unclear in my explanations or my
quick start.
HTH
--
Guillaume
> Regression in mount resolution when using optional parameters
> -------------------------------------------------------------
>
> Key: WICKET-5903
> URL: https://issues.apache.org/jira/browse/WICKET-5903
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 7.0.0-M5
> Reporter: Guillaume Smet
> Assignee: Andrea Del Bene
> Fix For: 7.0.0-M6
>
> Attachments: MountIssue-quickstart.tar.gz
>
>
> Hi,
> When using an optional parameter, there is something fishy with the way
> Wicket 7 resolves the mount point.
> For instance, if you mount in the following order the following paths:
> /test/${id}
> /test/mount/{#id}
> requests to /test/mount/4 are directed to the page mounted with /test/${id}
> Quick start to come.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
