Web Services Invocation Framework
The Web Services Invocation Framework (WSIF) supports a simple and flexible Java API (Application Programming Interface) 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 use different protocols. The software needs to be described using WSDL and have a binding included in its description, 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.
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
| Apache WSIF | |
|---|---|
| Developer | Apache Software Foundation |
| Stable release | 2.0
/ January 27, 2003 |
| Operating system | Cross-platform |
| Type | Web services |
| License | Apache License 2.0 |
| Website | ws.apache.org/wsif |
The Web Services Invocation Framework (WSIF) supports a simple and flexible Java API (Application Programming Interface) for invoking any Web Services Description Language (WSDL)-described service.[1][2]
Using WSIF, WSDL can become the centerpiece of an integration framework for accessing software running on diverse platforms which use different protocols. The software needs to be described using WSDL and have a binding included in its description,[clarification needed] 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.[citation needed]
See also
[edit]References
[edit]- ^ Zimmermann, Olaf; Tomlinson, Mark; Peuser, Stefan (2003-07-17). Perspectives on Web Services: Applying SOAP, WSDL and UDDI to Real-World Projects. Springer Science & Business Media. p. 358. ISBN 978-3-540-00914-6.
- ^ Alonso, Gustavo; Casati, Fabio; Kuno, Harumi; Machiraju, Vijay (2013-03-14). Web Services: Concepts, Architectures and Applications. Springer Science & Business Media. p. 194. ISBN 978-3-662-10876-5.
