The Web Services Invocation Framework (WSIF) API supports the invocation of services defined in WSDL. WSIF is intended for use in both WSIF clients and Web service intermediaries.
The WSIF API is driven by the abstract service description in WSDL; it is completely independent of the actual binding used. This independence makes the API more natural to work with because it uses WSDL terms to refer to message parts, operations, and so on.
The WSIF API was designed for the WSDL usage model: Pick a port that supports the port type needed, then invoke the operation by providing the necessary abstract input message consisting of the required parts, without worrying about how the message is mapped to a specific binding protocol.
Other Web service APIs, for example SOAP APIs, are not designed on WSDL, but for a specific binding protocol with its associated syntax; for example, target URIs and encoding styles.
The WSIF API main interfaces are described in the following topics...
- Creating a message for sending to a port (the WSIFMessage interface).
- WSIF API reference: Finding a port factory or service (the WSIFService interface and the WSIFServiceFactory class).
- WSIF API reference: Using ports (the WSIFPort interface and the WSIFOperation interface).
You must ensure that your application uses only one thread to call WSIF.
For additional technical details of the WSIF API, see the WSIF Javadoc.
See AlsoGoals of WSIF
An overview of WSIF
Web Services Invocation Framework (WSIF): Enabling Web services
Using WSIF to invoke Web services
WSIF system management and administration
WSIF API reference: Creating a message for sending to a port
WSIF API reference: Finding a port factory or service
WSIF API reference: Using ports