Revision as of 10:49, 16 May 2008 edit M4gnum0n (talk \| contribs) Extended confirmed users 7,593 edits no links and long intro ← Previous edit		Revision as of 17:38, 18 June 2008 edit undo Mathiastck (talk \| contribs) Extended confirmed users 3,659 edits →Why should I use WSIF?: this shouldn't be a copy of http://ws.apache.org/wsif/ Next edit →
Line 42: WSIF defines additional binding extensions so that EJBs, local java classes, software accessible over message queues using the JMS API and software that can be invoked using the Java Connector architecture can also be described in WSDL. WSIF is packaged with providers that allow transparent invocation of such software given the corresponding WSDL description. == ~~Why~~Description ~~should I use~~of WSIF? == 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.

Web Services Invocation Framework: Difference between revisions