Revision as of 20:53, 3 January 2007 edit Gaius Cornelius (talk \| contribs) Administrators 169,502 edits m Fix Capitalisation Typos: acessible → accessible, using AWB ← Previous edit		Revision as of 19:55, 25 January 2007 edit undo 129.55.200.20 (talk) →WSDL bindings for EJBs, JMs, JCA... Next edit →
Line 23: Clients can then utilize any new implementations and can 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. == WSDL bindings for EJBs, ~~JMs~~JMS, JCA... == 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 should I use WSIF? ==

Web Services Invocation Framework: Difference between revisions