Hello The only thing that I can think of (I didn't try it and I don't know what you can do with jetty.xml without checking) is to: - add a handler inside etc/jetty.xml using <Add> element for respective <Server> - put this handler into a bundle *that you can install as fragment bundle of pax-web-jetty* - but as I said - I didn't try.
regards Grzegorz Grzybek 2018-02-05 9:11 GMT+01:00 Maurice Betzel <[email protected]>: > Moin Grzegor, > > i did get the default handler (aka "/") working by blueprint (from the pax > web samples dir), but this does not cover other http contexts further up in > the context tree. I have some Camel routes running there and i would like > to have one default exception and error page for all contexts. Jetty > provides such a possibility by IoC in the Jetty XML where one can override > the default classes, but due to OSGi class-loading Jetty will not find my > overriding classes declared in a separate bundle. > At this moment i am looking at the "bundleContext.getServiceReference( > "org.ops4j.pax.web.service.WebContainer" );" as it has a method > registerErrorPage which with a null httpContext should use the default http > context. > Or is there a way to register a bundle so that Jetty wil find it by its > jetty.xml? > > -- > -- > ------------------ > 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.
