Network Deployment (Distributed operating systems), v8.0 > Develop and deploying applications > Develop web services - Invocation framework (WSIF)
Use WSIF to invoke web services
You invoke a web service dynamically by using the WSIF API directly.
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.
You should not use WSIF for new applications in WAS, unless you are supporting an existing WSIF configuration. You should instead adopt a more recent open standard, such as the JAX-WS programming model.
For more information about using the Web Services Invocation Framework (WSIF) to invoke web services, see 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.
- Example: Passing SOAP messages with attachments by using WSIF.
- Interacting with the Java EE container in WAS.
- Invoke a WSDL-based web service through the WSIF API.
- Run WSIF as a client
Related
Link a WSIF service to the underlying implementation of the service
Develop a WSIF service
Interacting with the Java EE container in WAS
Invoke a WSDL-based web service through the WSIF API
Run WSIF as a client
Web Services Invocation Framework (WSIF)
WSIF and WSDL
Use complex types
Use WSIF to bind a JNDI reference to a web service
Related
Example: Passing SOAP messages with attachments by using WSIF