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 running on the former (Apache SOAP) provider. To get your legacy services working again, you can either modify your Web services to use the current IBM Web Service SOAP provider as described in this topic, or you can change the WSIF default provider back to Apache SOAP.
Overview
To modify a legacy Web service, use the assembly tool to complete the following steps and thereby generate new deployment artifacts for access to the service from the IBM Web Service provider:
Procedure
- Import into the Workspace the project that contains your legacy Web services.
- For every legacy SOAP service in the project, repeat the following steps :
- From the pop-up menu for your_service.wsdl, select Generate Deploy Code.
- In the Generate Deploy Code window, change the Inbound Binding Type from SOAP to IBM Web Service.
- Click Finish.
- Export the EAR file that contains all of the deployment artifacts for the IBM Web Service Web service.
Related tasks
Change the default WSIF SOAP provider
WSIF SOAP provider: working with legacy applications