Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - Invocation framework (WSIF) > Use WSIF to invoke web services > Link a WSIF service to the underlying implementation of the service > Link a WSIF service to a SOAP over HTTP service
WSIF SOAP provider: working with existing 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 because 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.
As a result of the change from the Apache SOAP provider to the IBM Web Service SOAP provider, 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. See the Type Mappings section of WSIF - Known restrictions.
- The web service was built upon the Apache SOAP provider.
To get your existing services working again, we 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 web services to use the IBM Web Service SOAP provider.
Related
Modify web services to use the IBM Web Service SOAP provider
Change the default WSIF SOAP provider
Link a WSIF service to a SOAP over HTTP service