Problems with Karaf 2.3.1 and Cxf

I've been using Karaf 2.3.0 for a while. I now tried to upgrade to Karaf 2.3.1 but ran into problems with CXF. I use cxf-codegen-plugin to generate code from a WSDL file so that I can call the web service via a proxy. However, after upgrading to Karaf 2.3.1 I get the following exception:

Re: Problems with Karaf 2.3.1 and Cxf

Hi Bengt, do you use the jre.properties.cxf ? No problem with 2.3.0 ? Regards JB On 04/02/2013 09:30 AM, Bengt Rodehav wrote: I've been using Karaf 2.3.0 for a while. I now tried to upgrade to Karaf 2.3.1 but ran into problems with CXF. I use cxf-codegen-plugin to generate code from a WSDL

Re: Problems with Karaf 2.3.1 and Cxf

Hi, No concrete idea now, could you please append a test case which we can build and reproduce it? Thanks － Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog:

Re: Problems with Karaf 2.3.1 and Cxf

Hello JB, No I don't use jre.properties.cxf - where can I find it? It doesn't seem to be part of the distribution. Everything works fine under Karaf 2.3.0 - without using jre.properties.cxf. I'm also using Camel 2.10.3. I did this on Karaf 2.3.0 too without any problems. It seems like the

Re: Problems with Karaf 2.3.1 and Cxf

Hello Freeman, It would be a lot of work for me to narrow down my application to a simple test case. I'd really like to try other possibilities first, like: - Understanding how the factory pattern is supposed to work, espcially for Cxf - What has been changed in Karaf 2.3.1. that could affect

Re: Problems with Karaf 2.3.1 and Cxf

I found this blog post by Dan Kulp: http://www.dankulp.com/blog/2011/11/apache-cxf-in-osgi/ I modified the jre.properties accordingly but I still get the exact same stack trace. /Bengt 2013/4/2 Bengt Rodehav be...@rodehav.com Hello Freeman, It would be a lot of work for me to narrow down

Re: Problems with Karaf 2.3.1 and Cxf

It's the jre.properties that I'm taking about. It should be provided in etc/jre.properties.cxf. So the problem is not about a JRE package mismatch. I gonna take a deeper look (especially around the dependencies updates between 2.3.0 and 2.3.1). Regards JB On 04/02/2013 10:38 AM, Bengt

Re: Problems with Karaf 2.3.1 and Cxf

Thanks JB, I did notice that Karaf provides servicemix-specs API bundles in lib\endorsed. It includes jaxws. I thought that these jar's overrode the JVM. If so, then you shouldn't need to modifiy the jre.properties - or have I got it all wrong? /Bengt 2013/4/2 Jean-Baptiste Onofré

Re: Problems with Karaf 2.3.1 and Cxf

Hi, No, that blog is a little bit out of data and not applicable for Karaf 2.3.x anymore. With Karaf 2.3.x we endorse specs(like jaxws/jaxb) jars, so we need export those packages from system bundle 0, so don't comment it out and those endorsed specs jars can load jaxws impl bundle(cxf jaxws

Re: Problems with Karaf 2.3.1 and Cxf

Hi, You are right, I just replied you about it. － Freeman(Yue) Fang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://fusesource.com | http://www.redhat.com/ Twitter: freemanfang Blog: http://freemanfang.blogspot.com http://blog.sina.com.cn/u/1473905042 weibo: @Freeman小屋

Re: Problems with Karaf 2.3.1 and Cxf

I'll see if I can get a test case done for this although it might take a while. Meanwhile, can you explain what mechanism is used for resolving the implementation classes. I mean, how is the system bundle supposed to resolve a class that resides in another bundle? (In this case the

Re: Problems with Karaf 2.3.1 and Cxf

Hi, Good question, yeah, the traditional JAVA SPI mechanism generally doesn't work in OSGi container. So Servicemix Specs project[1] use OSGi locator to resolve this problem, Guillaume has a blog about it years ago[2] [1]https://svn.apache.org/repos/asf/servicemix/smx4/specs/trunk/

Re: Problems with Karaf 2.3.1 and Cxf

Thanks, will read the blog. 2013/4/2 Freeman Fang freeman.f...@gmail.com Hi, Good question, yeah, the traditional JAVA SPI mechanism generally doesn't work in OSGi container. So Servicemix Specs project[1] use OSGi locator to resolve this problem, Guillaume has a blog about it years ago[2]

Re: Problems with Karaf 2.3.1 and Cxf

I read the blog but it didn't go into details regarding how the implementation classes are found - I guess I'll have to look in the code. One observation regarding my problem: What gives me an exception is when blueprint attempts to instantiate my class. In my class constructor I try to create

Re: Problems with Karaf 2.3.1 and Cxf

Another observation. In Cxf 2.6.3 feature descriptor, the feature cxf-specs include, among others, 2.2 versions of jaxb-api and jaxws-api. Since the corresponding api's are only on 2.1 level in Karaf 2.3.0 lib\endorsed, the bundles are used instead. But, Karaf 2.3.1 has updated the endorsed

Re: Problems with Karaf 2.3.1 and Cxf

Just checked the feature descriptor for Cxf 2.7.3. It still includes the 2.2 api's. I wonder if anyone has gotten this to work on Karaf 2.3.1 and, if so, how they did it. /Bengt 2013/4/2 Bengt Rodehav be...@rodehav.com Another observation. In Cxf 2.6.3 feature descriptor, the feature