Re: How to contribue a CXF JAX-RS OSGi Sample?

Hi KL On 19/11/11 17:20, K Fung wrote: Hi Sergey, I've updated CXF-3859 with my newest iteration of the code :-) great Here is what has changed in this version... + Removed use of java.net repository as mail.jar is no longer a required dependency + Bump version to 2.5.1-SNAPSHOT + Use org

Re: CORS

I was thinking a bit more about it, we should probably just put it into org.apache.cxf.jaxrs.ext.cors in the jaxrs frontend at the moment, as I think that the creation of cxf-rt-jaxrs-extensions is needed shortly anyway which could keep most of the extensions, we can 'spawn' more specific modul

Re: Test Cases failing due to double slash in the URL generated by CXF

Hi On 23/11/11 12:24, irfannagoo wrote: Hi Guys, We have recently moved from CXF 2.2 to CXF 2.4.3 version. CXF 2.4.3 is generating this wadl resource base url "http://:/myapp/v1//" (observe the double slash) instead of "http://:/myapp/v1/". This problem was not see in CXF 2.2. Due to this, we

Re: Upgrading from 2.1.4 to 2.1.9

Hi Dan, Thank you for your fast reply. Daniel Kulp wrote > > The error makes it sound like there is an XML issue. Can you post the xml > configuration ? Here is the xml configuration file, which is pretty light (and works in 2.1.4) : http://www.springframework.org/schema/beans"; xmlns:xsi="

Re: Upgrading from 2.1.4 to 2.1.9

On 23/11/11 14:17, matiou wrote: Hi Dan, Thank you for your fast reply. Daniel Kulp wrote The error makes it sound like there is an XML issue. Can you post the xml configuration ? Here is the xml configuration file, which is pretty light (and works in 2.1.4) : http://www.springframework.o

Re: Upgrading from 2.1.4 to 2.1.9

Hmm... The XML looks fine. Sounds like your picking up a bad XML/StAX parser and not woodstox. You MAY be able to work around it via: http://cxf.apache.org/transports/http/configuration"; name="*.http-conduit"> http://cxf.apache.org/transports/http/configuration"; AutoRedirect

Re: How to contribue a CXF JAX-RS OSGi Sample?

Hi Sergey, > I'm wondering if 'minimalosgi' has to be exported ? I tried this before and it didn't work. minimalosgi has one classloader; the CXF bundle has its own classloader. minimalosgi's classloader has knowledge about CXF (due to the Import-Package declarations in its MANIFEST.MF) but CXF

Re: Upgrading from 2.1.4 to 2.1.9

Thank you ! it works fine now by adding the redundant namespaces. Have a good day -- View this message in context: http://cxf.547215.n5.nabble.com/Upgrading-from-2-1-4-to-2-1-9-tp5009968p5017225.html Sent from the cxf-dev mailing list archive at Nabble.com.