you would use /*, wicket lets urls that it cannot map fallthrough and be handled as usual.
additionally wicketfilter has some context params that lets you specify ignore masks, see the source/javadocs. -igor On Sun, May 9, 2010 at 8:22 PM, Chris Colman <chr...@stepaheadsoftware.com> wrote: > Oh, of course! Sorry I was mistakenly assuming we'd use "/*" which would > match everything but if we use the non wild card "/" then that will only > do an exact match and other URLs with /content etc., will still be able > to match their own separate patterns and redirect to their appropriate > filters/sevlets. > >>-----Original Message----- >>From: Jeremy Thomerson [mailto:jer...@wickettraining.com] >>Sent: Monday, 10 May 2010 12:23 PM >>To: users@wicket.apache.org >>Subject: Re: Any solution for the context problem with the relative > links >>of BookmarkablePageLink? >> >>Should still work. If you're using the filter, the idea is that it > will >>only respond to the URLs that it recognizes, and will pass other > requests >>down the chain. >> >>-- >>Jeremy Thomerson >>http://www.wickettraining.com >> >> >> >>On Sun, May 9, 2010 at 8:48 PM, Chris Colman >><chr...@stepaheadsoftware.com>wrote: >> >>> Using the word 'context' was probably misleading on my part. In > servlet >>> containers context=app. What I was talking about was the first 'path' >>> element after the domain name, >>> >>> Eg., content in www.mysite.com/content >>> >>> In this case I'm talking about a single app but I set up multiple >>> different URL patterns in the web.xml of that app to direct different >>> patterns to different filters/sevlets. >>> >>> I have a virtual host and all the filters/servlets are under that >>> virtual host and all desployed via a single .war >>> >>> >> >Is your servlet container listening directly to port 80? >>> >> >>> >> Yes. It's pure tomcat - not behind Apache Webserver. >>> >> >>> >> >If not, do the forwarding via a proxy on whatever you are using >>> >> >as a frontend. In that frontend, have it rewrite the URLs (i.e. >>> >> >mod_proxy and mod_rewrite). >>> >> > >>> >> >Otherwise, can you have your app mounted on "/"? >>> >> >>> >> I have quite a few non wicket servlets for things like commands > and >>> web >>> >> services and each, including wicket, have their own unique context > so >>> >> that they can all operate peacefully together under. >>> >> >>> >> If I mount the wicket app on "/" will that then pick up request > for >>> all >>> >> the other contexts or is there a way to mount wicket at "/" and > still >>> >> have other contexts mapping to different servlets? >>> > >>> > >>> >If you're using the Filter, it should fall through for other > requests - >>> >allowing them to still be processed. You may have to configure this >>> >behavior - it's been a while since I've personally done it. I know >>> that >>> >last week I configured a Wicket webapp on /foo when I already had >>> another >>> >app on / and they both worked just fine. Two wars - one deployed in >>> >tomcat/webapps/ROOT, and the other in tomcat/webapps/foo. It just >>> worked. >>> > >>> >-- >>> >Jeremy Thomerson >>> >http://www.wickettraining.com >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
