Linking a WSIF service to a SOAP over HTTP service
The SOAP provider allows WSIF stubs and dynamic clients to invoke SOAP services. Add WSDL extensions to your Web service WSDL file so that the service can use the SOAP provider.
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.
The current WSIF default SOAP provider (the IBM Web Service SOAP provider) does not fully interoperate with services 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 to connect 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.
To link a WSIF service to a SOAP over HTTP service, extend the service WSDL file in accordance with the code examples given in the following topics:
Procedure
- Example: Writing the WSDL extension that enables your WSIF service to access a SOAP over JMS service.
The WSDL binding extension for SOAP over JMS varies only slightly from the SOAP over HTTP binding.
- Example: Writing the WSDL extensions for SOAP attachments.
WSIF SOAP provider: working with legacy applications
Related tasks
Linking a WSIF service to a JMS-provided service
Linking a WSIF service to the underlying implementation of the service
Related Reference
Example: Writing the WSDL extension that enables your WSIF service to invoke a method on a local Java object
Example: Writing the WSDL extension that enables your WSIF service to invoke an enterprise bean