On consideration, I really don't want to get involved in a web.xml if I can avoid it. I'm not using the stock http transport as things are, somehow the code from the service factory plugs itself into the pax-web universe. I think I'll do some sleuthing.
On Mon, Dec 14, 2015 at 9:22 AM, Benson Margulies <[email protected]> wrote: > I have avoided blueprint in favor of DS but both are in karaf so I can > probably go there. > > On Dec 14, 2015 12:00 PM, "Sergey Beryozkin" <[email protected]> wrote: >> >> Hi Benson >> >> I suspect you may need to avoid depending on the default CXF HTTP >> Transport and deploy your bundle as a web bundle (with web.xml). >> Do you work with Aries ? If yes then use CXFBlueprintServlet: >> >> >> https://github.com/apache/cxf/blob/master/systests/jaxrs/src/test/resources/jaxrs_soap_blueprint/WEB-INF/web.xml >> >> and have a blueprint-web-osgi dependency >> >> Cheers, Sergey >> >> >> On 13/12/15 18:11, Benson Margulies wrote: >>> >>> How does the config in >>> http://cxf.apache.org/docs/servlet-transport.html for async map out in >>> pax-web? >>> >>> is there a ConfigAdmin param that gets set? >>> >> >
