Christian Schneider created CXF-5259:
----------------------------------------
Summary: XKMS client does not start in Eclipse RCP
Key: CXF-5259
URL: https://issues.apache.org/jira/browse/CXF-5259
Project: CXF
Issue Type: Bug
Components: XKMS
Reporter: Christian Schneider
Assignee: Christian Schneider
Fix For: 3.0.0, 2.7.7
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
