JBossDeveloper

I am in the last sprint of the project (which explains my delay), so upgrading at this point is considered risky.  Although, if I am unable to resolve the issue, then we might be pushed into this option.

Is there a defect that you could point me to?  I could use that as my reasoning for upgrading.

Edited by: bellator on May 2, 2011 4:03 PM

Hi,

As I mentioned before, the workaround is that you edit

$SMX_HOME/system/org/apache/camel/karaf/apache-camel/${camel-version}/apache-camel-${camel-version}-features.xml

replace

The error is introduced by mvn:org.apache.geronimo.specs/geronimo-jaxws_2.1_spec/1.0, which shouldn't be here at all.

Freeman

Freeman,

I looked back through all versions in version control of that file and I have never had the geronimo-jaxws line in my file.  As such I am not sure that would be the issue.  I have attached the file for your reference.  Maybe I missed something or this could materialize in another bundle reference you might see.

I can say this now: the issue has failed to be reproducable in our environments now even with the same build.  I want to point to the something like a class loader ordering but I don't want to do so blindly.  Any other thoughts?

I apprecaite your help and let me know if you need any other information.

Hi,

Is it possible that you happen to install geronimo-jaxws bundle or some bundle include META-INF/services/javax.xml.ws.spi.Provider file which point to axis2 provider(this is how JAVA SPI works), but you're not aware of that? So that if the bundle point to axis2 provider load first, you see the problem.

Anyway, you can specify a java system property like -Djavax.xml.ws.spi.Provider=org.apache.cxf.jaxws.spi.ProviderImpl to your servicemix start script which ensure always load cxf as jaxws provider.

Hope this helps.

Freeman