Will do later today! On Sat, May 9, 2015 at 7:12 AM, Martin Grigorov <[email protected]> wrote:
> Hi, > > It is a regression. > I guess it was broken with the removal of MountMapper. > Please create a ticket with a test case. > Thanks > On May 8, 2015 11:23 PM, "Guillaume Smet" <[email protected]> > wrote: > > > Hi all, > > > > I'm currently trying to migrate a few of our applications to 7 in the > hope > > we could provide useful feedback. > > > > In one of our applications, we have the following mounts: > > mountPage("/ticket/${id}", TicketDescriptionPage.class); > > mountPage("/ticket/contract/${companyId}/${id}/#{optionalTag}/", > > TicketContractTicketListPage.class); > > mountPage("/ticket/contract/#{companyId}", TicketContractListPage.class); > > mountPage("/ticket/search/#{optionalTag}/", > TicketCompleteListPage.class); > > > > With Wicket 6, we were able to access /ticket/contract without any issue. > > > > With 7, /ticket/contract is directed to TicketDescriptionPage which is > not > > what we expect (and leads to an error). > > > > Moreover /ticket/contract/105/327/00.01.21/ is also directed to > > TicketDescriptionPage . > > > > Is this change intentional? Looks like a regression to me (and an > annoying > > one as I would prefer not changing our URLs). > > > > Thanks for your feedback! > > > > -- > > Guillaume > > >
