WAS v8.5 > Develop applications > Develop web services - Invocation framework (WSIF) > Use WSIF to invoke web services > Linking a WSIF service to the underlying implementation of the service > Linking 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:

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 Apache SOAP provider.

To get your existing services working again, we have two options:

• 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 the web services to use the IBM Web Service SOAP provider.

Subtopics

• Change the default WSIF SOAP provider
  The WSIF default SOAP provider (the IBM Web Service SOAP provider) is designed to interoperate fully with a JAX-RPC compliant web service, and therefore the default provider does not fully interoperate with services that are running on the former (Apache SOAP) provider. To get your existing services working again, we can either modify the web services to use the current IBM Web Service SOAP provider, or we can change the WSIF default provider back to Apache SOAP as described in this topic.
• Modify web services to use the IBM Web Service SOAP provider
  The current WSIF default SOAP provider (the IBM Web Service SOAP provider) is designed to interoperate fully with a JAX-RPC compliant web service, and therefore the current default provider does not fully interoperate with services that are running on the former (Apache SOAP) provider. To get your existing services working again, we can either modify the web services to use the current IBM Web Service SOAP provider as described in this topic, or we can change the WSIF default provider back to Apache SOAP.

+

Search Tips   |   Advanced Search