This article describes how you can use a third-party Java™ API for XML Web services (JAX-WS) engine in WebSphere® Application Server V6.1. It describes how to deploy an application using an external third-party JAX-WS engine, as well as limitations and potential issues when using such third-party applications.
Some WebSphere Application Server (hereafter Application Server) users would like to leverage a third-party JAX-WS engine like Axis2 or Apache CXF by having these runtimes embedded in an application EAR file. There are several reasons you might want to do this, such as to use features specific to the third-party runtimes, to reuse code, or to achieve application consistency in a multi-vendor or multi-version environment.
Use of third-party JAX-WS runtimes has limitations and requires certain configuration changes. In some cases, it may also require manual intervention to resolve issues that occur during deployment and runtime. These limitations and issues vary based on the external runtime.
When such a third-party application is deployed on Application Server, the Application Server JAX-WS Web services engine must be disabled so it doesn’t conflict with the third-party implementation. Starting with WebSphere V6.1 Fixpack 29, configuration options were added to enable this on a per-application or per-server basis.
This article demonstrates how to use an application EAR with Axis2, Apache CXF, or Metro embedded in it with WebSphere Application Server V7.
- WebSphere does not claim support for any of the third-party JAX-WS runtimes. IBM ensures successful deployment of such applications only.
- This document does not imply IBM is endorsing the use of any of the third-party runtimes mentioned in this document on WebSphere Application Server.
|Article in PDF format||1001_thaker2.pdf||1.35MB|
|Sample Axis2 application||axis2.zip||18.3MB|
|Sample CXF application||CXFSampleOnWAS_Sample.ear||22.6MB|
|Sample Metro application||MetroOnWAS_Sample.ear||14.8MB|