1 / 18

Understanding WSDL Styles in SOAP Binding: RPC and Document Methods

This resource provides an in-depth overview of various WSDL (Web Services Description Language) styles used in SOAP (Simple Object Access Protocol) binding, specifically RPC/encoded, RPC/literal, Document/encoded, and Document/literal. Each style is examined with examples, including Java method implementations and SOAP message structures. The advantages and disadvantages of each WSDL style are highlighted, giving insights into their usage scenarios. This document is especially useful for developers working with web services and SOAP APIs in understanding and choosing the appropriate WSDL style for their applications.

tiponya-gonzalez
Télécharger la présentation

Understanding WSDL Styles in SOAP Binding: RPC and Document Methods

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. www.eu-egee.org WSDLWhich WSDL Style ? EGEE is a project funded by the European Union under contract IST-2003-508833

  2. Types of WSDL SOAP binding • RPC/encoded • RPC/literal • Document/encoded • Document/literal

  3. Java method example public void myMethod (int x);

  4. RPC/Encoded WSDL <message name=“myMethodRequest”> <part name=“x” type=“xsd:int”/> </message> <message name=“empty”/> <portType name=“PT”> <operation name=“myMethod”> <input message=“myMethodRequest”/> <output message=“empty”/> </operation> </portType> Binding is RPC/encoded

  5. SOAP message <soap:envelope> <soap:body> <myMethod> <x xsi:type=“xsd:int”>value</x> </myMethod> </soap:body> </soap:envelope>

  6. Advantages/disadvantages • Advantages • Simple WSDL • Operation name appears in the message • Disadvantages • Type encoding information overhead • SOAP message cannot be validated except against WSDL

  7. RPC/Literal WSDL <message name=“myMethodRequest”> <part name=“x” type=“xsd:int”/> </message> <message name=“empty”/> <portType name=“PT”> <operation name=“myMethod”> <input message=“myMethodRequest”/> <output message=“empty”/> </operation> </portType> Binding is RPC/literal

  8. SOAP message <soap:envelope> <soap:body> <myMethod> <x>value</x> </myMethod> </soap:body> </soap:envelope>

  9. Advantages/Disadvantages • Advantages • WSDL is simple • Operation name appears in the message • Type encoding information is minimal • Disadvantages • Nearly all the definitions in WSDL so not independently validatable

  10. Document/encoded • Not implemented !

  11. Document/literal WSDL <types> <schema> <element name=“xElement” type=“xsd:int”/> </schema> </types> <message name=“myMethodRequest”> <part name=“x” element=“xElement”/> </message> <message name=“empty”/> <portType name=“PT”> <operation name=“myMethod”> <input message=“myMethodRequest”/> <output message=“empty”/> </operation> </portType>

  12. SOAP message <soap:envelope> <soap:body> <xElement>value</xElement> </soap:body> </soap:envelope>

  13. Advantages/Disadvantages • Advantages • No type encoding information • The body of the soap message is all defined in a schema and so can be validated independently • Disadvantages • WSDL is more complicated • Operation name is lost

  14. Document/wrapped WSDL <types> <schema> <element name=“myMethod”/> <complexType> <sequence> <element name=“x” type=“xsd:int”/> </sequence> </complexType> </element> </schema> <types> <message name=“myMethodRequest”> <part name=“parameters” element=“myMethod”/> </message> <message name=“empty”/> <portType name=“PT”> <operation name=“myMethod”> <input message=“myMethodRequest”/> <output message=“empty”/> </operation> </portType> WSDL schema has a wrapper around the parameters

  15. SOAP message <soap:envelope> <soap:body> <myMethod> <x>value<x> </myMethod> </soap:body> </soap:envelope>

  16. Characteristics • Input message has a single part • Part is an element • Element has the same name as the operation • Element’s complex type has no attributes

  17. Advantages/disadvantages • Advantages • No type encoding information • Soap body is defined in a schema – validation • Method name in the soap message • Disadvantages • WSDL is complicated • Generally this is the best style to use.

  18. When not to use document/wrapped • Document literal wrapped style does not allow for overloading • Cannot have two elements with the same name in XML (element has to have same name as operation) • In this case you may wish to use RPC/literal so that the operation name is available.

More Related