Using a third-party JAX-WS web services engine
In certain situations you might need to set up a third-party JAX-WS web services engine. For example, you must set up a third-party JAX-WS web services engine if you need to deploy applications that use a single run time across various application servers such as WebSphere® Application Server, JBoss, and WebLogic, or if you want to build JAX-WS web services applications using third party JAX-WS run time such as CXF, Axis2, and Metro.
Before you begin
Use of a third-party JAX-WS run time has limitations. It also requires mandatory configuration changes, and in some cases, it requires manual intervention to resolves issues that occur during deployment and when you run the application. These limitations and issues vary based on the third-party JAX-WS run time you decide to use. You should understand the limitations for the third-party JAX-WS run time you are preparing to use before you configure your system to use that implementation.
- The WebSphere Application Server run time restricts usage of application modules that use both the JAX-WS implementation provided with WebSphere Application Server, and an external JAX-WS implementation in the same application EAR file. You must use either the JAX-WS implementation provided with WebSphere Application Server or the external implementation in a single application EAR file. This limitation ensures that the run time WebSphere Application Server does not conflict with the external third-party JAX-WS implementation.
- You must remove any conflicting JAR files from your application library before you deploy an application that uses an external JAX-WS implementation. Most of the external third-party JAX-WS run times include some JAR file libraries that are already installed on WebSphere Application Server. This situation causes conflicts in your application library.
- After an application that uses a third-party JAX-WS run time is deployed on WebSphere Application Server, it is not recognized as a service client or
provider. Therefore, you cannot attach application level policy sets to these applications. You must
rely on external run times support quality of service. Following is a list of WebSphere Application Server features that are not available if you decide to
deploy and run application that uses third-party JAX-WS implementations:
- WS-Security, WS-RM, and WS-Transactions policy sets
- WSDM
- JNDI lookup to retrieve JAX-WS Service or Port Instance.
About this task
When you deploy an application EAR file with a third-party JAX-WS implementation on WebSphere Application Server, the WebSphere Application Server run time must ensure the use of the third-party engine, and disable the use of the existing WebSphere Application Server JAX-WS web services engine.
WebSphere Application Server does not claim support for any of the third-party JAX-WS run times, but has tested the deployment and execution of applications that use such runtimes.
You must complete the following steps before you can use an external JAX-WS run time in an application.
Procedure
Results
What to do next
- Deploy and run an application EAR file with a third-party JAX-WS implementation on WebSphere Application Server.