Linking a WSIF service to the underlying implementation of the service

A Web Services Invocation Framework (WSIF) service is linked to the underlying service through a WSIF provider. A provider is an implementation of a WSDL binding that can run a WSDL operation through a binding-specific protocol. Providers implement the interface between the WSIF API and the actual implementation of a service.

Providers are pluggable within the WSIF framework, and are registered according to the namespace of the WSDL extension that they implement. Some providers use the Java EE model to use Java EE services. If a provider is available, but its required class libraries are not, then the provider is disabled.

To use the providers that are supplied with WAS, see the following topics:

 

• Link a WSIF service to a SOAP over HTTP service.
• Link a WSIF service to a JMS-provided service (SOAP over JMS, or native JMS).
• Link a WSIF service to a local Java application.
• Link a WSIF service to a service implemented as an enterprise bean.

Linking a WSIF service to a SOAP over HTTP service
Linking a WSIF service to a JMS-provided service
Example: Writing the WSDL extension that enables the WSIF service to invoke a method on a local Java object
Example: Writing the WSDL extension that enables the WSIF service to invoke an enterprise bean

 

Related tasks

Develop a WSIF service
Interacting with the Java EE container in WAS
Use complex types
Use WSIF to bind a JNDI reference to a Web service
Running WSIF as a client
Use WSIF to invoke Web services