IBM does not provide support for third-party Web service
engines. IBM supports the specifications required to communicate between
Web service engines. Note, using third-party Web service engines in the
same runtime as the WebSphere Application Server Web service engine might
work, but failures in the third-party product are handled first by the
third-party product's support group. Any issues which are suspected to be
WebSphere Application Server issues require data from the third-party
product support group showing the interface with the WebSphere Application
Server and how this interface contributes to the failure in the
third-party product. If an issue in a third-party Web service engine is
not due to a defect in the WebSphere Application Server but the customer
wishes to continue using the third-party Web service engine, the customer
should refer to IBM services.
From the WebSphere Application Server V5.1 Information Center:
"What is the relationship between the Apache Axis component of the Web
services technology preview available with WebSphere Application Server
V5.0 and Web Services for J2EE?"
The current Web services technology leveraged the work that IBM
contributed to the Apache Axis code base. The Web Services for J2EE
support included with WebSphere Application Server V5.0.2, and continuing
on into Version 5.1 and 5.1.1, is derived from Apache Axis, but has
diverged and contains many IBM-specific features to enhance performance,
scalability, reliability, interoperability, and integration with the
WebSphere Application Server.
The following standards are supported by the Web Services for J2EE
component of WebSphere Application Server Versions 5.0.2, 5.1 and 5.1.1:
- SOAP Version 1.1
- Web Services Description Language (WSDL) Version 1.0
- Web Services for J2EE (JSR-109) Version 1.0
- Java™ API for XML-Based RPC (JAX-RPC) Version 1.0
- SOAP with attachments API for Java™ (SAAJ) Version
1.1
|