You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Florian Müller (JIRA)" <ji...@apache.org> on 2011/08/18 11:57:27 UTC
[jira] [Commented] (CMIS-420) CMIS provided JAX-WS/JAXB engine
compatibility issues when using IBM Webshere server
[ https://issues.apache.org/jira/browse/CMIS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086921#comment-13086921 ]
Florian Müller commented on CMIS-420:
-------------------------------------
Try setting the classloader delegation to "parent last".
> CMIS provided JAX-WS/JAXB engine compatibility issues when using IBM Webshere server
> ------------------------------------------------------------------------------------
>
> Key: CMIS-420
> URL: https://issues.apache.org/jira/browse/CMIS-420
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-server
> Affects Versions: OpenCMIS 0.4.0
> Environment: Websphere 7.0
> JRE1.6
> Spring 2.5.5
> Linux
> Reporter: Krishna Penugonda
> Priority: Critical
> Fix For: OpenCMIS 0.4.0
>
>
> We have created CMIS services as per the OpenCMIS package from Apache Chemistry. Since OpenCMIS uses the Sun JAX-WS/JAXB runtimes, we are seeing conflicts between Sun's implementation of JAX-WS and WebSphere 7's JAX-WS runtime.
> When processing SOAP faults within the OpenCMIS package, we get ClassCastExceptions where it's clear that WebSphere's JAXB implementation is being used instead of Sun's JAXB implementation. The exact error is:
> Caused by: java.lang.ClassCastException: com.ibm.xml.xlxp2.jaxb.JAXBContextImpl incompatible with com.sun.xml.bind.api.JAXBRIContext
> at com.sun.xml.ws.fault.SOAPFaultBuilder.<clinit>(SOAPFaultBuilder.java:544)
> at java.lang.J9VMInternals.initializeImpl(Native Method)
> Please help us and suggest a solution in getting these issues resolved.
> Thanks in advance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira