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.
Overview
As a result of this change in SOAP providers, previous WSIF clients might not work in either of the following cases:
- 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).
- The Web service was built upon the former (Apache SOAP) provider.
To get your legacy services working again, you have two options:
Procedure
- Change the default WSIF SOAP provider back to the former Apache SOAP provider (in which case any future invocations to a JAX-RPC compliant Web service will not work if that Web service uses parameter types xsd:date, xsd:dateTime, xsd:hexBinary or xsd:QName).
- Modify your services to use the current IBM Web Service SOAP provider.
Change 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