Use WSIF to invoke Web services
You invoke a Web service dynamically by using the WSIF API directly.
Overview
You specify the location of the WSDL file for the service, the name of the operation to invoke, and any operation arguments. All other information needed to access the Web service (the abstract interface, the binding, and the service endpoint) is available through the WSDL.
This kind of invocation does not require stub classes and does not need a separate compilation cycle.
More information on using the Web Services Invocation Framework (WSIF) to invoke Web services is provided in the following topics:
Procedure
- Link a WSIF service to the underlying implementation of the service.
- Develop a WSIF service.
- Use complex types.
- Use WSIF to bind a JNDI reference to a Web service .
- Pass SOAP messages with attachments using WSIF.
- Interact with the J2EE container in WAS.
- Run WSIF as a client.
Linking a WSIF service to the underlying implementation of the service
Developing a WSIF service
Use complex types
Using WSIF to bind a JNDI reference to a Web service
Passing SOAP messages with attachments using WSIF
Interacting with the J2EE container in WAS
Running WSIF as a client
Related tasks
Learning about WSIF
Installing and managing WSIF
Working with the WSIF API
Web Services Invocation Framework (WSIF): Enabling Web services