You can add something like this in the web.xml file.
Hi, thanks for the suggestion, it's appreciated.
However, I need different behaviour, the 404 is limited to the WAR, you can't specify another context or host it seems, then Jetty throws a 400 or 404 error.
I'd like to be able to define some sort of central context where ALL 404 come together of all deployed WAR's. I want one WAR to handle the 404 errors that are thrown in other WAR's.
Here i am again. Im still having problems configuring Jetty properly and am a little bit confused about how it's handling virtual hosts and HttpContexts. Is it possible to map multiple WAR's on the same machine to a / context root if those WAR's use seperate virtual host names ? I need behaviour that when the user types www.war1.com Jetty serves WAR1, and for www.war2.com serves the other web app. However, if you deploy 2 app's to a / request dispatching to those contexts would be impossible right ? Since the server can't distinguish between the apps. I guess ill just drop in 1 RequestDispatch servlet on the root of jetty and define names instead of just "/" for the contexts of my web apps.
Im a little bit puzzled, am I missing something ?