Using WSIF to invoke web services
You invoke a web service dynamically by using the WSIF API directly.
About this task
You specify the location of the Web Services Description Language (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.
Note: You should not use WSIF for new applications
in WebSphere® Application
Server, unless you are supporting an existing WSIF configuration.
You should instead adopt a more recent open standard, such as the Java™ API
for XML-Based Web Services (JAX-WS) programming model.
For more information about using the Web Services Invocation Framework (WSIF) to invoke web services, see the following topics:
Procedure
- Linking a WSIF service to the underlying implementation of the service.
- Developing a WSIF service.
- Using complex types.
- Using 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 WebSphere Application Server.
- Invoking a WSDL-based web service through the WSIF API.
- Running WSIF as a client