Web Services Invocation Framework: Difference between revisions

Content deleted Content added
See also: per WP:SEEALSO, this section must not contain red links
No edit summary
Tags: Visual edit Mobile edit Mobile web edit
Line 22:
The '''Web Services Invocation Framework''' (WSIF) supports a simple [[Java (programming language)|Java]] API for invoking [[Web services]], no matter how or where the services are provided. The framework allows maximum flexibility for the invocation of 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 and using widely varying protocols. The only precondition is that the software needs to be described using WSDL, and to have included in its description a binding 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 service or a local Java class.
 
== Structure ==