Use the SOAP provider

The SOAP provider allows WSIF stubs and dynamic clients to invoke SOAP services.

 

Overview

The Web Services Invocation Framework (WSIF) SOAP provider supports SOAP 1.1 over HTTP.

The SOAP provider is JSR 101/109 compliant and uses Web Services for J2EE for parsing and creating SOAP messages.

Note: The current WSIF default SOAP provider (the IBM Web Service SOAP provider) does not fully interoperate with services that are running on the former (Apache SOAP) provider. This restriction 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. For more information see WSIF SOAP provider: working with legacy applications.

The SOAP provider supports:

• SOAP-ENC encoding.

• RPC style and Document style SOAP messages.

• SOAP messages with attachments.

The SOAP provider is not transactional.

The SOAP provider does not support the WSIF synchronous timeout. The SOAP provider uses the default client timeout value that is set for Web Services for J2EE.

If you have a Web service that you expect multiple clients to use connecting over SOAP, then before you deploy the service set up your application deployment descriptor file dds.xml to handle multiple connections correctly. For more information, see WSIF troubleshooting tips.

 

What to do next

For an example of the sort of code changes that need to be made in the WSDL file for a SOAP provider, see the following topics:

• The SOAP over JMS provider - writing the WSDL extension.

• SOAP messages with attachments - Writing the WSDL extensions.

 

See also

WSIF SOAP provider: working with legacy applications

 

Related Tasks

Using the JMS providers
Using the Java provider
Using the EJB provider

 

---

 

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.