Hello Hmm, I see your case is quite complex - is there a chance you prepare integration test in pax-web-itests/pax-web-itests-container/pax-web-itests-container-jetty?
I'd have to try to reproduce your issue, but I have to know what other web bundles / wars you have installed - maybe you also have some whiteboard services or plain httpService.registerServlet() calls? regards Grzegorz Grzybek 2018-02-06 10:28 GMT+01:00 Maurice Betzel <[email protected]>: > No, it did not. Jetty is producing the response using the default Jetty > handler. > > > Am Dienstag, 6. Februar 2018 09:49:55 UTC+1 schrieb Maurice Betzel: >> >> My default handler gets hit on https://somehost/api/rest/exis >> tingcontext/nonexistingcontext, but reports that the base request was >> handled and the response was committed. Did the Camel servlet handle the >> error before my default handler? >> > -- > -- > ------------------ > OPS4J - http://www.ops4j.org - [email protected] > > --- > You received this message because you are subscribed to the Google Groups > "OPS4J" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
