Thanks, I should have added more detail. The interesting thing is we are learning quickly the differences between OSGi classloading and TCCL.
This application if you will is running in Day WCM which uses the Felix OSGi container. We are currently building a bundle that makes a web service call using the JaxWsProxyFactoryBean. We have CXF, Spring, and the other dependency bundles loaded into the Felix container. The interesting part is that when we make the web service invocation, the JaxWsProxyFactoryBean appears to utilize schema files located in one of the jars to make the dynamic invocation. When CXF framework attempts to find this schemas relative to the current classloader, it appears the OSGi/Felix bundle classloader is used (and since it is Day...it tries to find the schemas in the JCR repository and not the CXF jar files). Thanks for the help and I will take a look at the 2.3.1 Release Notes. -- View this message in context: http://cxf.547215.n5.nabble.com/OSGi-bug-javax-xml-ws-WebServiceException-Could-not-find-wsdl-binding-operation-tp3293584p3295290.html Sent from the cxf-user mailing list archive at Nabble.com.
