Re: Async in OSGi / pax-web

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:

Re: CXF 3.0.7 JAXRS POST read body

Hi Perhaps it is supposed to work with JAX-RS, so I've fixed it as part of https://issues.apache.org/jira/browse/CXF-6709 I'd still recommend you to avoid dealing with Servlet request/response directly - one of the main ideas of JAX-RS was to provide a simpler/alternative mechanism. Thanks,

Re: Missing JAX-RS API jar in Karaf

Freeman, it's not just my bundle. I've filed a JIRA. com.basistech:cxf-async-jaxrs-example-features:bundle:0.0.1-SNAPSHOT [INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:3.1.4:provided [INFO] | +- org.apache.cxf:cxf-core:jar:3.1.4:provided [INFO] | | +-

Re: Async in OSGi / pax-web

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

RE: CXF incorrect WSDL automatically generated ? Please help !

Hi Aki For completeness, let me add that last Friday I created a Hello World cxf web service where I added a header parameter. I deployed it in one server with WebLogic 12c and also in a different server with WebLogic 10.3. The result was that the automatic generated WSDL in 10.3 had the

Re: Async in OSGi / pax-web

On Mon, Dec 14, 2015 at 11:00 AM, Sergey Beryozkin wrote: > 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

Re: Async in OSGi / pax-web

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

Re: Async in OSGi / pax-web

A simple example worked. On Mon, Dec 14, 2015 at 1:02 PM, Benson Margulies wrote: > Off I go! > > On Mon, Dec 14, 2015 at 12:37 PM, Daniel Kulp wrote: >> >>> On Dec 13, 2015, at 1:11 PM, Benson Margulies wrote: >>> >>> How does the

Re: Async in OSGi / pax-web

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" 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

AW: CXF 3.0.7 JAXRS POST read body

Hi, Thanks Sergey. You're right, I should make use of the JAX-RS mechanisms. But because I already ran into some problems, I am a little bit concerned facing further more severe problems especially when it comes to chunking etc. So I'd like to be able to run both variants of our application

Re: Async in OSGi / pax-web

May be you can try with a single service first - no complexity is added, you'd only add a web.xml which would refer (via Spring DM or Blueprint) to the actual application context, with CXFServlet, same as you do it without OSGI, when working with CXFServlet. I was referring to that

Re: Async in OSGi / pax-web

> On Dec 13, 2015, at 1:11 PM, 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? Have you tried it? I believe pax-web always assumes that

Re: Cont: upgrading cxf client to 3.0.1

It have been a while, but I just found out that I solved the issue by disabling Mtom: Then it works... ;) Any idea why this solved the issue ? (I am trying CXF 3.1.4 currently). And how is it possible to solve this with mtom enabled ? The issue was: The Webservice response contained

Re: Async in OSGi / pax-web

Off I go! On Mon, Dec 14, 2015 at 12:37 PM, Daniel Kulp wrote: > >> On Dec 13, 2015, at 1:11 PM, 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

CXF 3.0.7 JAXRS POST read body

Hi everybody, I am currently refactoring a REST application whose implementation is based on a subclass of javax.servlet.http.HttpServlet and thus is using javax.servlet.http.HttpServletRequest and javax.servlet.http.HttpServletResponse quite extensively to use CXF and JAXRS. The refactored