Enabling a third-party JAX-WS application in WebSphere Application Server V7

This article describes how you can use a third-party Java API for XML Web services (JAX-WS) engine in WebSphere Application Server V7. 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.

Nikhil Thaker (nikhil.v.thaker@us.ibm.com), Advisory Software Engineer, IBM

Nikhil Thaker photoNikhil Thaker is an Advisory Software Engineer with IBM Software Group, and a member of the WebSphere Application Server team that developed the Web services JAX-WS implementation. He has more than nine years of experience in Enterprise Application Integration, and has focused on Web services for the past four years. He has worked with various IBM customers as an IT Specialist in Enterprise Application Integration in IBM Global Services. His industry experience includes automotive, health care, telecommunication and utilities.

You can reach Nikhil at nikhil.v.thaker@us.ibm.com.



13 January 2010

This article describes how you can use a third-party Java™ API for XML Web services (JAX-WS) engine in WebSphere® Application Server V7. 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.

Overview

Develop skills on this topic

This content is part of a progressive knowledge path for advancing your skills. See Building and deploying JAX-WS web services

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 Fixpack 7, 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 or Apache CXF embedded in it with WebSphere Application Server V7.

Note: WebSphere does not claim support for any of the third-party JAX-WS runtimes. IBM ensures successful deployment of such applications only. See the Tech Note for more information.

Downloads

DescriptionNameSize
Article in PDF format1001_thaker.pdf1.1MB
Sample Axis2 applicationaxis215.war21.5MB
Sample CXF applicationCXFSampleOnWAS_Sample.ear22.6MB
static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=WebSphere
ArticleID=461366
SummaryTitle=Enabling a third-party JAX-WS application in WebSphere Application Server V7
publish-date=01132010