On Tue, 2005-02-15 at 10:31 +0100, Michael Marks wrote: > Hello Ian, > > thank you very much for answering so detailed to my WS-RF-newbie-questions. > It clarifies a lot > > the use of document-literal message-style in the WS-RF and Web Services in > general. > > Regarding question #1: I believe, the use of inputs with zero parts is > useful especially in > > case of WS-RF. As the WS-Resource we talk to is identified by > wsa:ReferenceProperties(until > > yet, we'll see what the RefProp-Removal-Discussion will bring), we can send > messages to a > > service using this identified WS-Resource without the need of any other > parameter. > > An example could be: > > An E-Shop provides a ShoppingCart as WS-Resource. The ShoppingCart can be > created, > > modified(adding,deleting articles), destroyed and finally ordered. Asuming > the > > creation-operation of a ShoppingCart-Resource takes the customer-identity as > a parameter and > > the stateful resource is bound to the identified customer after creation - > say by a > > ResourceProperty "eshop:customerID". There would be no need for providing > any other information > > to the ShoppingCart.order() - operation. (I'm not sure, if this is a > real-world example, as > > normally a ShoppingCart is created without identifying the customer. The > binding to the > > ordering customer is m,ost often done at ordertime (see amazon).) But I > believe, it's a > > question of modeling the underlying workflow. > > At the moment, a developer has no chance to model the example described > above with the WS-RF.
I'm not quite sure what makes you say that, can you elaborate? /Sam -- Sam Meder <[EMAIL PROTECTED]> The Globus Alliance - University of Chicago 630-252-1752 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
