- From: Arthur Ryman <ryman@ca.ibm.com>
- Date: Wed, 22 Nov 2006 10:54:57 -0500
- To: Youenn Fablet <youenn.fablet@crf.canon.fr>
- Cc: www-ws-desc@w3.org, www-ws-desc-request@w3.org
- Message-ID: <OFB62589C9.24B19E38-ON8525722E.0057192F-8525722E.00576D6E@ca.ibm.com>
Yoeunn,
+1.
#none seems easy to bind, i.e. no input parameters. I guess you could also
achieve this using an empty element.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: 4169395063@fido.ca
Youenn Fablet <youenn.fablet@crf.canon.fr>
Sent by: www-ws-desc-request@w3.org
11/22/2006 10:41 AM
To
www-ws-desc@w3.org
cc
Subject
SOAP Response and IRI style
When the soap response MEP is used to bound an in-out operation, the
input being defined by a schema,
the input is serialized in the URI following the url-encoded
serialization (section 6.7.2).
This serialization requires the use of the IRI style which puts a
constraint on the kind of operations that can be bound to the soap
response mep.
It seems sensible to me that inout operations can be bound to the
soap-response mep if:
- the input message is a #none kind of message (I did not found any
text about this case by the way, I may have missed something)
- the input message is a #element kind of message with the element
schema following the IRI style constraints
Does this make sense?
Should we add some text in the specification to clarify this?
Youenn
Received on Wednesday, 22 November 2006 15:55:22 UTC