[
https://issues.apache.org/jira/browse/CMIS-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Florian Müller resolved CMIS-754.
---------------------------------
Resolution: Won't Fix
Assignee: Florian Müller
> CMIS provided JAX-WS/JAXB engine compatibility issues when using IBM Webshere
> server
> ------------------------------------------------------------------------------------
>
> Key: CMIS-754
> URL: https://issues.apache.org/jira/browse/CMIS-754
> Project: Chemistry
> Issue Type: Bug
> Components: opencmis-client-bindings
> Affects Versions: 0.2.0-incubating
> Environment: Websphere 7.0
> JRE1.6
> Linux
> Reporter: KRISHNA SAI MULPURI
> Assignee: Florian Müller
> Priority: Critical
>
> 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(org.apache.axis2.jar).
> 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 problem is it picks
> BindingProvider implementation from axis2.jar present in websphere/plugins
> folder instead of sun's implementation of binding provider.
> If i remove axis2.jar from plugins folder then everything works fine. without
> removing is there any solution ?
> I have seen that client-bindings provided from version 0.7.0 but is there a
> way to fix this issue in 0.2.0 itself ?
> Please help us and suggest a solution in getting these issues resolved.
> Thanks in advance.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
