chemistry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Krishna Penugonda (JIRA)" <>
Subject [jira] [Commented] (CMIS-422) Open CMIS not supporting IBM Websphere JAX-WS
Date Mon, 22 Aug 2011 14:26:29 GMT


Krishna Penugonda commented on CMIS-422:

Thanks For your response. I hope refactoring is required at both OpenCMIS Server and Client
APIs. Also please let us know plans for incorporate IBM Websphere JAX-WS support in forthcoming

If we want to make this as one of the critical feature in next releases, How can we priorities
this to be included as part of immediate release or as a patch release?   

We need to plan accordingly based on this IBM Websphere JAX-WS support.

> Open CMIS not supporting IBM Websphere JAX-WS
> ---------------------------------------------
>                 Key: CMIS-422
>                 URL:
>             Project: Chemistry
>          Issue Type: Bug
>          Components: opencmis-client, opencmis-server
>    Affects Versions: OpenCMIS 0.4.0
>         Environment: IBM WebSphere Application Server 7.0.13
>            Reporter: Krishna Penugonda
>            Priority: Blocker
>              Labels: Dependencies
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> We are running two existing web services in our environment and both are using IBM Websphere
JAX-WS engine. Because of this we have tuned the IBM Websphere JAX-WS engine to get Maximum
throughput as per our requirements. The CMIS Server which was developed using OPENCMIS server
framework is dependent on SUN JAX-WS engine. 
> All our client application consumes two existing web services and the new CMIS Web service.
But Websphere runtime restricts the usage of application modules that use both IBM's JAX-WS
implementation and an external JAX-WS implementation in the same application.
> So, is there a way for OPENCMIS Server Framework and OPENCMIS Client Framework to make
it work with IBM Websphere JAX-WS engine without any dependencies on Sun JAX-WS?

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message