Hi Benson
It likely can be controlled from jetty.xml in pax-web (enabling the
async mode) but as we have learnt recently, pax web only checks
jetty.xml if a full blown war or web bundle is deployed.
Web Bundle is your regular bundle, with only web.xml added to it, plus
an extra WebAppContext instruction in Manifest
Sergey
On 14/12/15 15:09, Benson Margulies wrote:
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 <ben...@basistech.com> 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" <sberyoz...@gmail.com> 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?
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/
