I think you would need to create your own strategy. -- Jeremy Thomerson http://www.wickettraining.com
On Mon, Oct 12, 2009 at 1:31 PM, Luther Baker <lutherba...@gmail.com> wrote: > Thank nino. Unfortunately, I think you may have misunderstood my question. > > Indeed, I understand how to configure Wicket for RESTful URLs but my > question is different. What I'm asking has to do with the PLACEMENT of the > url parts. IE: I want the leftmost portion of the URL to be a parameter. > RosterListPage.java should receive requests from: > > /cardinals/roster/list/14 > /rams/roster/list/12 > /falcons/roster/list/18 > > or think about it from a project tracking standpoint: > > /jira/issues/list/29 > /bambool/issues/list/32 > /fisheye/issues/list/25 > > I want urls like: > > http://code.google.com/guice/issues/list/45 > http://code.google.com/wicket-guice/issues/list/32 > http://code.google.com/jtrac/issues/list/21 > > Does that help clarify? Notice, the ROOT of the URL keeps changing. In my > case, I want to mount parts 2 and 3 of the browser's URL to an actual > Wicket > page. > > How do I 'mount' a URL when the root of the URL keeps changing - and is > itself, a parameter. Would I need to implement > IRequestTargetUrlCodingStrategy > myself or is there an existing strategy that I can leverage a bit? > > Hope that makes sense, > > -Luther > > > On Mon, Oct 12, 2009 at 2:03 AM, nino martinez wael < > nino.martinez.w...@gmail.com> wrote: > > > You can already do this, a 2 sec google search brought this up: > > > > > > > http://blog.xebia.com/2008/10/09/readable-url%E2%80%99s-in-wicket-an-introduction-to-wicketstuff-annotation/ > > http://css.dzone.com/news/wicket-creating-restful-urls > > > > 2009/10/12 Luther Baker <lutherba...@gmail.com> > > > > > I'd like to use a RESTful URL style where the page parameters are not > > > necessarily at the far right of the URL. For starters, I understand the > > > basics of Indexed and/or MixedParam url mounting to convert this: > > > > > > /issues/list?project=*myapp*&max=*14* > > > > > > to this: > > > > > > /issues/list/*myapp*/*14* > > > > > > but what I'm looking for is something like: > > > > > > /*myapp*/issues/list/*14* > > > > > > where "/issues/list" identifies the page and "/myapp" and "/14" are the > > > parameter values. In this case, the actually mapping looks something > > like: > > > > > > */[page]/[action]/* ==> Page > > > > > > Thoughts on the base way to manage this? > > > > > > -Luther > > > > > >
