WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

WSIF SOAP provider: working with legacy applications

The current WSIF default SOAP provider (the IBM Web Service SOAP provider) does not fully interoperate with services that are designed to run on the former (Apache SOAP) provider. This is due to the fact that the IBM Web Service SOAP provider is designed to interoperate fully with a JAX-RPC compliant Web service, and Apache SOAP cannot provide such a service.

Why and when to perform this task

As a result of this change in SOAP providers, previous WSIF clients might not work in either of the following cases:
  1. The Web service uses any of the following parameter types: xsd:date, xsd:dateTime, xsd:hexBinary or xsd:QName (for more information, see the Type Mappings section of WSIF - Known restrictions).
  2. The Web service was built upon the former (Apache SOAP) provider.

To get your legacy services working again, you have two options:

Steps for this task




Sub-topics
Changing the default WSIF SOAP provider
Modifying Web services to use the IBM Web Service SOAP provider

Related tasks
Linking a WSIF service to a SOAP over HTTP service

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsf_soap_io.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)