WSDL (Web Services Description Language) is an XML format for describing web services and how they can be accessed, with definitions for the data types, messages, operations and bindings. It has two layers - a service definition layer that describes operations and messages, and a binding layer that specifies protocols and data formats. An example WSDL document is provided that shows the typical structure and elements used.

3. Binding information about transport protocol to be used

5. Message types

6. Operations

8. Data format

9. Example : WSDL

10. Example : WSDL

11. Example : WSDL

12. Example : WSDL

13. Example : WSDL

14. < definitions > <!-- root WSDL element --> < types > <!-- defines data types to be transmitted --> </ types > < message > <!-- defines messages to be transmitted -> </ message > < portType > <!-- defines operations (functions) to be supported --> </ portType > < binding > <!-- defines how will the messages be transmitted on the wire --> </ binding > < service > <!-- defines location of web service --> </ service > </ definitions > Example : WSDL

16. targetNamespace attribute in an imported WSDL document's <definitions> element must be the same as the value of the namespace attribute in the WSDL <import> element importing the WSDL document. Definitions – Import

19. Validates the particular wire format

20. Must be namaspeces defines in the targetnamespace or xsd:schema element or namespace in xsd:import

23. Solicit-response : The operation can send a request and will wait for a response.

24. Notification : The operation can send a message but will not wait for a response. Definitions – Messages - Port-type

25. 1. Definitions : <definitions .... > <types> <xsd:schema .... />* </types> </definitions> 2. Definitions : <xsd:element name=&quot;MyArray1&quot; type=&quot;tns:MyArray1Type&quot;/> <xsd:complexType name=&quot;MyArray1Type&quot;> <xsd:sequence> <xsd:element name=&quot;x&quot; type=&quot;xsd:string&quot; minOccurs=&quot;0&quot; maxOccurs=&quot;unbounded&quot;/> </xsd:sequence> </xsd:complexType> Example : Definitions

26. 1. Message : <message name=&quot;OrderMsg&quot;> <part name=&quot;productName&quot; type=&quot;xs:string&quot;/> <part name=&quot;quantity&quot; type=&quot;xs:integer&quot;/> </message> 2. Message : type -> RPC <message name=&quot;GetBulkBookPriceRequest&quot;> <part name=&quot;isbn&quot; type=&quot;xsd:string&quot;/> <part name=&quot;quantity&quot; type=&quot;xsd:int&quot;/> </message> 3. Message : element -> Document <message name=&quot;SubmitPurchaseOrderMessage&quot;> <part name=&quot;order&quot; element=&quot;sd:purchaseOrder&quot; /> </message> 4. Message : fault <message name=&quot;InvalidArgumentFault&quot;> <part name=&quot;error_message&quot; element=&quot;sd:InvalidIsbnFaultDetail&quot; /> </message> Example : Message

27. 1. Port-type : one-way <wsdl:definitions .... > <wsdl:portType .... > * <wsdl:operation name=&quot;nmtoken&quot;> <wsdl:input name=&quot;nmtoken&quot;? message=&quot;qname&quot;/> </wsdl:operation> </wsdl:portType > </wsdl:definitions> 2. Port-type : request - response <wsdl:definitions .... > <wsdl:portType .... > * <wsdl:operation name=&quot;nmtoken&quot; parameterOrder=&quot;nmtokens&quot;> <wsdl:input name=&quot;nmtoken&quot;? message=&quot;qname&quot;/> <wsdl:output name=&quot;nmtoken&quot;? message=&quot;qname&quot;/> <wsdl:fault name=&quot;nmtoken&quot; message=&quot;qname&quot;/>* </wsdl:operation> </wsdl:portType > </wsdl:definitions> Example : Port-type

28. 3. Port-type : solicit-response <wsdl:definitions .... > <wsdl:portType .... > * <wsdl:operation name=&quot;nmtoken&quot; parameterOrder=&quot;nmtokens&quot;> <wsdl:output name=&quot;nmtoken&quot;? message=&quot;qname&quot;/> <wsdl:input name=&quot;nmtoken&quot;? message=&quot;qname&quot;/> <wsdl:fault name=&quot;nmtoken&quot; message=&quot;qname&quot;/>* </wsdl:operation> </wsdl:portType > </wsdl:definitions> 4. Port-type : notification <wsdl:definitions .... > <wsdl:portType .... > * <wsdl:operation name=&quot;nmtoken&quot; parameterOrder=&quot;nmtokens&quot;> <wsdl:output name=&quot;nmtoken&quot;? message=&quot;qname&quot;/> </wsdl:operation> </wsdl:portType > </wsdl:definitions> Example : Port-type

30. Style must be either a RPC/Literal binding or a Document/Literal binding

31. location attribute in a <soapbind:address> element must be unique within a WSDL document

32. HTTP response from a web service operation using the one-way message exchange pattern must have an empty body

33. client of a web service operation using the one-way message exchange pattern must ignore any SOAP messages returned. Such a response just indicates that the message has reached the receiver

34. One or more WSDL documents may contain more than one WSDL <binding> elements that refer to one and the same WSDL <portType> element

35. WSDL document must have the same set of operations as the WSDL <portType> element to which the binding refers

36. SOAP message that is inconsistent with its WSDL document, it must check for “VersionMismatch”, “MustUnderstand” and “Client” fault conditions in that order. Binding

39. must contain exactly one par t accessor element for each of the WSDL <part> elements bound to the envelope's corresponding <soapbind:body> element

41. Example : Binding

42. Example : Binding Header

47. Notification : endpoint send an output message Service - Port-type

48. <portType name=&quot;StockQuotePortType&quot;> <operation name=&quot; GetLastTradePrice &quot;> <input message=&quot;tns:GetLastTradePriceInput&quot;/> <output message=&quot;tns:GetLastTradePriceOutput&quot;/> </operation> </portType> Example : Port-type

49. <service name=&quot;StockQuoteService&quot;> <documentation>My first service</documentation> <port name=&quot;StockQuotePort&quot; binding=&quot;tns:StockQuoteBinding&quot;> <soap:address location=&quot;http://example.com/stockquote&quot;/> </port> </service> Example : Service