Re: Get Wicket to ignore wicket parameters

2012-01-19 Thread Steve Fatula
On Jan 17, 2012, at 9:31 PM, Jeremy Thomerson wrote:

> 
> I'm sure it can be handled in Wicket, but even then I'd default to
> mod_rewrite for something as simple as "always remove parameter X from
> query string for pages A, B, C".  To me dealing with old URLs is better
> done at that level rather than cluttering the application with it.
> 

Yeah, this is true. Also, by using mod_rewrite, one can tell the search engines 
that it's a permanent change so hopefully over time, most of the old links fade 
away.

Steve
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Get Wicket to ignore wicket parameters

2012-01-17 Thread Steve Fatula
I have taken over management of a site using wicket, which I was woefully 
unfamiliar with. Have been able to do some screens, modify them, add stuff, 
etc. without much trouble. However, the overflow flow I am not familiar with.

The site had some web pages that were stateful and had a sort bar. That was 
removed. Wicket parms in the url are encoded. 

So, a previous link might look like:

www.site.com/something.html?page=2&z=afhyewifewicfhewichewicvhweripcvh

These pages were indexed by the search engines. Now that the sort functions are 
gone, and, we've made the page a stateless page, requests to pages with the 
wicket parms (in the z=) now return an error as so:

2012-01-17 10:55:36,700 (TP-Processor23) [   RequestCycle.java:1432:ERROR] 
unable to find component with path 
someProductList:productList:topToolbars:2:toolbar:headers:2:header:orderByLink 
on stateless page 

Wel, is true of course since that's been removed. However, we want pages to 
still work, just, ignore the wicket stuff.

Can this be handled via some method in wicket? i.e., something that can tell 
wicket to ignore the wicket stuff for the specific page in question? Some stuff 
in the query string are still used on those pages, just want to not process the 
wicket stateful stuff. Or, is it best handled with mod_rewrite in Httpd?