Web Services Invocation Framework: Difference between revisions

Revision as of 09:58, 26 July 2023

Revision as of 16:50, 18 February 2024

Line 20:

The '''Web Services Invocation Framework''' (WSIF) supports a simple and flexible [[Java (programming language)|Java]] API for invoking any [[Web Services Description Language]] (WSDL)-described service.

Using WSIF, WSDL can become the centerpiece of an integration framework for accessing software running on diverse platforms which uses different protocols. The software needs to be described using WSDL and have a binding included in its description{{Clarify|reason=The preceding statement refers to the WSDL (Web Services Description Language) and establishes a connection to it by categorizing it as "software." However, it highlights the absence of a detailed explanation or reference to WSDL within the article. Consequently, there is a requirement for a link that provides a description of WSDL to supplement the information presented.|date=July 2020}} ,that the client's WSIF framework has a provider for. WSIF defines and comes packaged with providers for local Java, [[Enterprise JavaBeans]] (EJB), Java Message Service (JMS), and [[Java EE Connector Architecture]] (JCA) protocols, which means that a client can define an EJB or a [[Java Message Service]]-accessible service directly as a WSDL binding and access it transparently using WSIF, using the same API one would use for a [[SOAP|SOAP service]] or a local Java class.

== Structure ==

In WSDL, a binding defines how to map between the abstract ''PortType'' and a real service format and protocol. For example, the SOAP binding defines the encoding style, the ''SOAPAction'' header, the namespace of the body (the targetURI), and so forth.

WSDL allows multiple implementations for a Web service and multiple ports that share the same PortType. In other words, WSDL allows the same interface to have bindings to services likesuch as SOAP and [[General Inter-ORB Protocol|IIOP]].

WSIF provides an API to allow the same client code to access any available binding. AsSince the client code can be written to the PortType, itthe canchoice beof awhich deploymentport orand configurationbinding settingit (oruses acan codebe choice)determined whichby portdeployment, andconfiguration bindingsettings, itor uses.code

The WSIF uses ''providers'' to support these multiple WSDL bindings. A provider is a piece of code that supports a WSDL extension and allows invocation of the service through that particular implementation. WSIF providers use the J2SE JAR service provider specification, making them discoverable at [[Run time (program lifecycle phase)|runtime]].

Clients can utilize new implementations and delegate the choice of port to the infrastructure and runtime, which allows the implementation to be chosen on the basis of quality of service characteristics or business policy.

== Bindings for EJBs, JMS, and JCA ==

WSIF defines additional binding extensions so that [[Enterprise JavaBean]] (EJBs), local Java classes, software accessible over [[message queue]]s using the [[Java Message Service]] (JMS) API, and software that can be invoked using the [[Java EE Connector Architecture|Java Connector architecture]] can also be described in WSDL. WSIF is packaged with providers that allowenable transparent invocation givenbased on the corresponding WSDL description..

== Description ==

WSIF enables developers to interact with abstract representations of Web services through their WSDL descriptions instead of working directly with the Simple Object Access Protocol (SOAP) APIs, which is the usual programming model. With WSIF, developers can work with the same programming model regardless of how the Web service is implemented and accessed.

WSIF allows stubless or completely dynamic invocation of a Web service, based upon examination of the metadata about the service at runtime. It also allows updated implementations of a binding to be plugged into WSIF at runtime, andallowing the calling service to defer choosing a binding until runtime.

It is closely based on WSDL soenabling it canto invoke any service that can be described in the language.

If a complicated enterprise software system consists of various pieces of software, developed over a period of decades—EJBs, legacy apps accessed using Java's connector architecture, SOAP services hosted on external servers, old code accessed through messaging middleware—it is necessary to write software applications that use all these pieces to do useful things, where the differences in protocols, and mobility of software, etc. conflict with oneeach anotherother.

If the software is moved to a different server, the code breaks. The SOAP libraries used change—for example, when one movestransitioning from using Apache SOAP to Apache Axis—asAxis, as it usesemploys a now-deprecated SOAP API. Something that was previously accessible as an EJB is now available through messaging middleware via JMS—again, the code that uses the software must be fixed, or if one has an EJB which is offered as a SOAP service to external clients. Using SOAP results in a performance penalty compared to accessing the EJB directly.

WSIF fixesresolves these problemsissues by allowingenabling WSDL to be usedserve as a normalized description of disparate software, and allowsallowing users to access this software without depending on a specific protocol or ___location. The separation of the API from the actual protocol also means there is flexibility—protocols, ___location, etc. can be switched without having to recompile client code. If an externally available SOAP service becomes available as an EJB, users can use RMI/IIOP by changing the service description (the WSDL), without making any modification in applications that use the service. WSDL's extensibility, its capability to offer multiple bindings for the same service, deciding on a binding at runtime, etc. can be exploited.

== Differences between WSIF and Axis ==