Tags

,

links:
http://msdn.microsoft.com/en-us/library/ms996486.aspx
http://www.tutorialspoint.com/wsdl/wsdl_example.htm
http://www.ibm.com/developerworks/library/ws-whichwsdl/ (why doc/lit)

summary:
– WSDL has quite a few building blocks which the latter ones build upon previous ones
– divides into “abstract” and “concrete” sections
– “abstract” layers has “types”, “messages” and “portType” (similar to interface)
– “message” is like functions api but only 1 api hence only 1-way and singular
– “portType” groups multiple apis together and hence plural and bi-directional (in and out)
– “binding” = implementation of “portType”

details:
– types (abstract), name of data types and their definition in xml schemas
– message (abstract), name of message types and their part/parameters, using types. message -> type(s) + parameter(s)/part(s)
– portType/interface (abstract), see name interface hence it has a set of methods/operations, and each operation has “input” and/or “output”, using “message”.
– portType -> in message(s) + out message(s)
– binding (concrete), attr “use” set to “literal” meaning using the abtract definition literally. When “style” set to “document” meaning xml document style. Using portType/interface.
– i.e. binding -> portType + style/use + soap -> concreate
– service (concrete), service -> port(s)/endPoint(s) + binding +uri location

Advertisements