Re: URL coding strategies

2010-12-16 Thread Bas Gooren
more information in the identifier. Bas - Original Message - From: "Henrique Boregio" To: Sent: Thursday, December 16, 2010 6:06 PM Subject: Re: URL coding strategies Hey Bas, you're right, I hadn't thought of it that way. In option 1, how would I go about using a

Re: URL coding strategies

2010-12-16 Thread Henrique Boregio
Hey Bas, you're right, I hadn't thought of it that way. In option 1, how would I go about using a unique textual identifier? Say there are 2 items with the name "Ford Ranger Model 2005" but each one is posted by different users, the URL would still be: http://www.mysite.com/item/Ford-Ranger-Model-

Re: URL coding strategies

2010-12-16 Thread Bas Gooren
ge goes to the product page directly? That way the only contextual information you have is what is in the url. Good luck. Bas - Original Message - From: "Henrique Boregio" To: Sent: Thursday, December 16, 2010 4:05 PM Subject: URL coding strategies Hello, I am mounti

Re: URL coding strategies

2010-12-16 Thread Andrea Del Bene
Hi Henrique, are you using a custom WebRequestCodingStrategy implementation? This class should let you encode visible URL as you prefer. Hello, I am mounting my URLs so I can list product items like so: http://www.mysite.com/item/id/0 http://www.mysite.com/item/id/1 and so on...then I user thi

URL coding strategies

2010-12-16 Thread Henrique Boregio
Hello, I am mounting my URLs so I can list product items like so: http://www.mysite.com/item/id/0 http://www.mysite.com/item/id/1 and so on...then I user this id param to fetch the data from the database. I am not accesing this page directly. I have another page where the items are fully listed (

Re: Multiple URL coding strategies on the same mount path

2010-11-14 Thread Martin Grigorov
The exceptions are lightweight, i.e. they don't have stack trace information and thus are faster to instantiate. See AbortException code On Sun, Nov 14, 2010 at 2:01 PM, Sebastian wrote: > Does that scale? This means an exception is thrown on each HTTP request > below /shop/ > > Regards, > > Seb

Re: Multiple URL coding strategies on the same mount path

2010-11-14 Thread Sebastian
Does that scale? This means an exception is thrown on each HTTP request below /shop/ Regards, Seb On 14.11.2010 03:23, Igor Vaynberg wrote: the easiest way is to mount a page onto /shop using indexed coding strategy. parse the parameters, and throw a restartresponseexception with the right pa

Re: Multiple URL coding strategies on the same mount path

2010-11-13 Thread Igor Vaynberg
the easiest way is to mount a page onto /shop using indexed coding strategy. parse the parameters, and throw a restartresponseexception with the right page. -igor On Sat, Nov 13, 2010 at 5:15 PM, Sebastian wrote: > Hi, > we are currently migrating a webapp to Wicket and have the requirement to >

Multiple URL coding strategies on the same mount path

2010-11-13 Thread Sebastian
Hi, we are currently migrating a webapp to Wicket and have the requirement to keep the existing URL structure. Here is an example of REST-like URLs we need to match to different pages: /shop/=> ShopWelcomePage.class /shop/A/ => BrandsByFirstCharPage.class /s

Re: URL coding strategies

2010-03-18 Thread bgooren
you only query the database once for the product, but the url is not seo-friendly. vp143 wrote: > > Hi there, I have a question about URL coding strategies > > > > I have decided to use IndexedParamUrlCodingStrategy for friendly URL's. > > > > I have set

URL coding strategies

2010-03-17 Thread Vishal Popat
Hi there, I have a question about URL coding strategies I have decided to use IndexedParamUrlCodingStrategy for friendly URL's. I have set PageParameters for this strategy in the following way: PageParameters pageParameters = new PageParam