+

Search Tips   |   Advanced Search

 

WSIF Overview

 

The Web Services Invocation Framework (WSIF) provides a Java API for invoking Web services, independent of the format of the service or the transport protocol through which it is invoked.

This framework addresses all of the issues identified in Goals of WSIF. WSIF provides the following features:

WSIF provides runtime support for Web services, and for WSDL extensions and bindings, that were not known at build time. This capability is known as dynamic invocation. Using WSIF, a client application can choose dynamically the optimal binding to use for invoking Web service operations. For example, a Web service might offer a SOAP binding, and also a local Java binding so that you can treat the local service implementation (a Java class) as a Web service. If a client application is deployed in the same environment as the service, then this client can use the local Java binding for the service. This provides more efficient communication between the client and the service by making direct Java calls rather than indirect calls using the SOAP binding. WSIF provides this runtime support through the use of providers. The providers support Web services, WSDL extensions and bindings that were not known at build time by using the WSDL description to access the target service.

WSIF is designed to work both in an unmanaged environment (stand-alone) and inside a managed container. You can use the JNDI to find the WSIF service, or you can use the location described in the WSDL. For more conceptual information about WSIF and WSDL, see the following topics:

WSIF supports Internet Protocol V6, and Java API for XML-based Remote Procedure Calls (JAX-RPC) V1.1 for SOAP.


Sub-topics


WSIF architecture

WSIF and WSDL

WSIF usage scenarios

 

Related concepts


Goals of WSIF

 

Related tasks


Use WSIF to invoke Web services
Installing and managing WSIF
Working with the WSIF API
Learning about the Web Services Invocation Framework (WSIF)