Use the SOAP provider

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

The Web Services Invocation Framework (WSIF) SOAP provider supports SOAP 1.1 over HTTP. The SOAP provider uses Apache SOAP 2.3 for parsing and creating SOAP messages, but it is not limited to invoking services from Apache SOAP.

The WSIF SOAP provider supports...

• SOAP-ENC encoding.

• RPC style and Document style SOAP messages.

• SOAP messages with attachments.

The SOAP provider is not transactional.

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.

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

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

 

---