[ 
https://issues.apache.org/jira/browse/CMIS-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487510#comment-13487510
 ] 

Dilip MD commented on CMIS-420:
-------------------------------

Late but wanted to update this. Could not make OpenCMIS OSGI bundles to work 
with Websphere without endorsing JAX-WS jars. So used non osgi jars inside the 
web app lib folder (including websphere specific jar from 0.6.0)and loaded them 
using framework.properties to make it work.
                
> 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
>            Assignee: Florian Müller
>            Priority: Critical
>             Fix For: OpenCMIS 0.6.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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to