chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dilip MD (Commented) (JIRA)" <>
Subject [jira] [Commented] (CMIS-420) CMIS provided JAX-WS/JAXB engine compatibility issues when using IBM Webshere server
Date Thu, 10 Nov 2011 11:56:51 GMT


Dilip MD commented on CMIS-420:

Did this issue solved? I'm also facing below error with Websphere while connecting to Alfresco
using Webservices. However, atompub connection works fine.

Caused by: java.lang.VerifyError: JVMVRFY013 class loading constraint violated; class=com/sun/xml/ws/client/WSServiceDelegate,

> CMIS provided JAX-WS/JAXB engine compatibility issues when using IBM Webshere server
> ------------------------------------------------------------------------------------
>                 Key: CMIS-420
>                 URL:
>             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: incompatible
with com.sun.xml.bind.api.JAXBRIContext
> at<clinit>(
> 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:!default.jspa
For more information on JIRA, see:


View raw message