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: [email protected] For additional commands, e-mail: [email protected]
