W3C home > Mailing lists > Public > www-ws@w3.org > January 2005

Distinction between procedure-oriented and document-oriented wsdl

From: Robert Mark Bram <relaxedrob@optusnet.com.au>
Date: Sat, 01 Jan 2005 16:33:45 +1100
To: w3c-ws <www-ws@w3.org>
Message-ID: <opsjwsejd7ov81ve@mail.optusnet.com.au>

Hi All!

What is the practical difference between procedure-oriented and 
document-oriented wsdl?

I found the following scant description of the distinction between the two:

==
This enumeration allows the user to specify whether the message being 
transmitted is procedure-oriented or document-oriented. Procedure-oriented 
messages contain parameters and return values, while document-oriented 
messages contain documents.
==
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemwebservicesdescriptionsoapbindingstyleclasstopic.asp
==

But to my understanding, procedure-oriented and document-oriented is only 
revealed at the binding level. This means you still have to define a 
portType with operations that have input, output and fault messages - 
which in turn have parameters.

So what practical difference is there between a procedure and document 
oriented message when both are tied to an abstract operation that has 
input messages (with parameters) and output messages (that are return 
values)?

Any advice is most welcome!

Rob
:)

-- 
Robert Mark Bram
http://phd.netcomp.monash.edu.au/RobertMarkBram/default.asp
B.Comp.(Systems Development/Business Systems)
B.Net.Comp.(Hons)
Doctor of Philosophy Student

School of Network Computing
Faculty of Information Technology
Monash University
Peninsula Campus
McMahons Rd
Frankston, VIC 3199
AUSTRALIA
Received on Saturday, 1 January 2005 05:33:19 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 3 July 2007 12:25:48 GMT