WSDL: Difference between revisions

30 bytes added ,  2 December 2007
m
bits
m (Cat WIP)
m (bits)
Line 31: Line 31:
There may be many more than these (look ant any Microsoft .Net service WSDL), but most services will define at least these ones as a minimum, although not always in exactly that form.
There may be many more than these (look ant any Microsoft .Net service WSDL), but most services will define at least these ones as a minimum, although not always in exactly that form.


===The service element===
===The "''service''" element===


Although the last of the children of the <description> element, this is the natural starting point for human WSDL readers.  There ''can'' be more than one service defined in a single WSDL document, which is sometimes sensible for describing different physical services which share the same logical definition (a service provider might provide the same service from a number of different network locations - i.e. servers - to provide redundancy, or multiple services might share some aspects, in particular data types, in common), however most commonly only a single service will be described.
Although the last of the children of the <description> element, this is the natural starting point for human WSDL readers.  There ''can'' be more than one service defined in a single WSDL document, which is sometimes sensible for describing different physical services which share the same logical definition (a service provider might provide the same service from a number of different network locations - i.e. servers - to provide redundancy, or multiple services might share some aspects, in particular data types, in common), however most commonly only a single service will be described.
Line 43: Line 43:




===The binding element===
===The "''binding''" element===


===the portType element===
===the "''portType''" element===


===The message elememt===
===The "''message''" elememt===


===The types element===
===The "''types''" element===