Hi, I think this is because you're mixing path parameters with query string one. It could be a bug, could you provide a quickstart with this to help us qualify and fix it if it is a bug.
Regards, __ Cedric Gatay (@Cedric_Gatay <http://twitter.com/Cedric_Gatay>) http://code-troopers.com | http://www.bloggure.info | http://cedric.gatay.fr On Tue, Jul 23, 2013 at 7:31 PM, Francois Meillet < [email protected]> wrote: > Try this pattern /storage/${id}/#{shape} > > Optional parameters are denoted by using a # instead of $ > > > François Meillet > Formation Wicket - Développement Wicket > > > > > > Le 23 juil. 2013 à 19:14, Andrew Schetinin <[email protected]> a écrit > : > > > Hi, > > > > I have a shared resource mounted to a URL pattern "/storage/${id}" > > So that the URL look like "/storage/12345" > > and with optional additional parameters "/storage/12345?shape=xyz" > > > > It works fine when I create a new URL - the "id" parameter is correctly > > encoded in the URL. > > > > But when I process the actual request, I only receive the optional > > parameters like "shape", while "id" parameter is not present in > > RequestParameters. Therefore I need to parse the URL string and extract > the > > ID parameters manually. > > > > The question is - why Wicket does not decode the parameters back? > > Is it by design, or is it only a problem with shared resources? > > > > Regards, > > > > Andrew > > > > -- > > Andrew Schetinin > >
