Web Services Invocation Framework: Difference between revisions

Content deleted Content added
more serious than that
SmackBot (talk | contribs)
m Date maintenance tags and general fixes
Line 1:
{{Cleanup-rewrite|date=July 2008}}
{{longintro|date=May 2008}}
{{Infobox_Software
Line 25:
 
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 you need to describe your software using WSDL, and include in its description a binding that your client's WSIF framework has a provider for. WSIF defines and comes packaged with providers for local java, [[EJB]], [[JMS]], and [[JCA]] protocols. That means you can define an EJB or a JMS-accessible service directly as a WSDL binding and access it transparently using WSIF, using the same API you would for a SOAP service or even a local java class.
 
 
== WSIF Structure ==
Line 74 ⟶ 73:
 
{{Apache}}
 
[[Category:Web service specifications]]
[[Category:Web services]]