Anshuk Pal Chaudhari

Subscribe to Anshuk Pal Chaudhari: eMailAlertsEmail Alerts
Get Anshuk Pal Chaudhari: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Related Topics: Java EE Journal, Apache Web Server Journal, Open Web Magazine

J2EE Journal: Article

Web Service Invocation Framework

Adding wheels to Web services

Advantages and Disadvantages
Advantages

  • WSIF allows multiple bindings
  • It solves integration problems of various J2EE components using WSDL extensions.
  • It doesn't require an abstract description such as CORBA objects at the time exposing it, so it follows most of the rules related to Web services
  • WSIF forces the programmer to hide the complicated details from the one who accesses it, as it forces the programmer to write its own WSDL
  • Services can be used either by a set of stub classes (static) or by a dynamic interface invocation (dynamic)
  • It allows the developer to work with the same programming model regardless of how the service is implemented and accessed
  • It enables the developer to move away from the native APIs of the underlying service, and to interact with representations of the services instead
  • Also protocols, location, etc. can be changed without having to recompile the client code
Disadvantages
  • WSIF also follows the discovery model followed by Web services, so it also suffers from the performance degradation due to its reliance on XML in discovery
  • Centralized registry is for registering all of the new bindings done in WSIF, so this architecture is not good for mobile computing because it would require an accessible registry in every wireless network
  • This framework mainly depends on WSDL but WSDL extensions are not open standards, so providers might use multiple specifications of the same binding type, which also causes new interoperability problems
  • Tools required for generating stubs and skeleton, which handle asynchronous transport, are not available with WSIF
  • It doesn't have built-in support for transactions and security
Summary
We have witnessed that in order to handle different protocols, WSIF implements an extensible framework. It permits new modules to be added to a client runtime to sustain additional protocols. These new modules - WSIF Providers, handle all possible service requests for a given protocol. WSIF currently has providers for SOAP/HTTP, SOAP/JMS, EJB using RMI-IIOP, native JMS messaging, and legacy systems using the J2EE Connector Architecture to access systems, including CICS and IMS. In all of the aforementioned cases, we can see that the WSDL that we are writing keeps on changing according to the binding, but each time the client only has a minor change. The WSIF is just creating a layer on top of the application layer and keeping the WSDL as the centerpiece of information. It would have been better if there had been a way of generating the WSDL depending on what type of binding and protocol the client requires.

More Stories By Anshuk Pal Chaudhari

The authors are interning and/or working as part of the Web Services COE (Center of Excellence) for Infosys Technologies, a global IT consulting firm, and have substantial experience in publishing papers, presenting papers at conferences, and defining standards for SOA and Web services. The Web Services COE specializes in SOA, Web services, and other related technologies.

More Stories By Sandeep Gaikwad

The authors are interning and/or working as part of the Web Services COE (Center of Excellence) for Infosys Technologies, a global IT consulting firm, and have substantial experience in publishing papers, presenting papers at conferences, and defining standards for SOA and Web services. The Web Services COE specializes in SOA, Web services, and other related technologies.

More Stories By Ambar Verma

The authors are interning and/or working as part of the Web Services COE (Center of Excellence) for Infosys Technologies, a global IT consulting firm, and have substantial experience in publishing papers, presenting papers at conferences, and defining standards for SOA and Web services. The Web Services COE specializes in SOA, Web services, and other related technologies.

More Stories By V. Niranjan

The authors are interning and/or working as part of the Web Services COE (Center of Excellence) for Infosys Technologies, a global IT consulting firm, and have substantial experience in publishing papers, presenting papers at conferences, and defining standards for SOA and Web services. The Web Services COE specializes in SOA, Web services, and other related technologies.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.