[CXF-5259] XKMS client does not start in Eclipse RCP

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.7.7, 3.0.0-milestone1
• Component/s: XKMS
• Estimated Complexity: Unknown
• Assignee: Christian Schneider
• Reporter: Christian Schneider
• Created: 09/Sep/13 08:03
• Updated: 27/Sep/13 18:18
• Resolved: 10/Sep/13 14:08

Description

When starting xkms-client in Eclipse RCP there is an exception that the javax.xml.BindingProvider interface is not visible.

The error is a bit misleading. The BundleDelegatingClassloader sees the interface but loads it from a different classloader than the interface supplied to ProxyHelper by the JAXWS frontend.

The interface supplied by JAXWS comes from:
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@11b289f[org.apache.servicemix.specs.jaxws-api-2.2:2.2.0(id=72)]
This looks correct.

The interface from the BundleDelegatingClassloader has the Classloader null. The javadoc explains that this means it comes from the bootstrap classloader.

The error may be related to my recent change to ProxyHelper. A workaround is to add the javax.xml package to the imports of xkms-client.

Strangely the error only happens in Eclipse RCP buit not in karaf and not in pure equinox based on an extended DOSGi distro.