Hi,
When we try to pair site for SRM, we got this kind of error: "Failed to acquire token from SSO server."
From the log, we can find
Caused by: javax.xml.bind.JAXBException: class org.oasis_open.docs.ws_sx.ws_trust._200512.RequestSecurityTokenType nor any of its super class is known to this context.
at com.sun.xml.internal.bind.v2.runtime.JAXBContextImpl.getBeanInfo(JAXBContextImpl.java:564)
at com.sun.xml.internal.bind.v2.runtime.XMLSerializer.childAsRoot(XMLSerializer.java:471)
at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.write(MarshallerImpl.java:308)
at com.sun.xml.internal.bind.v2.runtime.MarshallerImpl.marshal(MarshallerImpl.java:236)
at javax.xml.bind.helpers.AbstractMarshallerImpl.marshal(AbstractMarshallerImpl.java:130)
at com.vmware.vim.sso.client.impl.processors.request.RequestBuilderImpl.marshallJaxbElement(RequestBuilderImpl.java:255)
... 98 common frames omitted
In our plugin project,we export those packages.
Export-Package:
...
org.oasis_open.docs.ws_sx.ws_trust._200512;version="1.0.1.SNAPSHOT";
uses:="javax.xml.bind.annotation,
org.oasis_open.docs.wss._2004._01.oasis_200401_wss_wssecurity_secext_1_0,
org.oasis_open.docs.wss._2004._01.oasis_200401_wss_wssecurity_utility_1_0,
javax.xml.ws.wsaddressing,
javax.xml.bind,
javax.xml.namespace,
org.w3c.dom,
com.rsa.names._2009._12.std_ext.ws_trust1_4.advice",
Obviously the package that causes the OSGI wiring issues DOES get exported from this bundle which causes disturbance in bundle classloader wirings.
Currently, we are using the shipped wsdl of VMware Managment SDK to generated the source code/packages for reference in our plugin project, which cause the conflict with SRM plugin.
So we are searching to use the internal VMware ssoClient jar just as SRM do instead of export packages.
When we were using internal ssoClient jar, we got many of dependency issue. We want to refer to SRM's dependency chains.
The question is how the SRM handle the dependency chains when using ssoClient?