[
https://issues.apache.org/jira/browse/WICKET-5903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538441#comment-14538441
]
Guillaume Smet commented on WICKET-5903:
----------------------------------------
Hi Andrea,
I can confirm it's OK now. I can access to the pages of my application.
Let's port a second one to see how it goes!
Thanks.
> 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)
