RE: Mapping WSDL meps to the HTTP binding

The robust in-only can only reply with a fault, not a message, so I
would expect the HTTP code for the response to be 4xx, not 2xx. I
believe we already cover the expectation of the HTTP code in connection
with faults.

Tony Rogers
tony.rogers@ca.com

-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of youenn fablet
Sent: Thursday, 16 November 2006 0:55
To: www-ws-desc@w3.org
Subject: Mapping WSDL meps to the HTTP binding


Reading the HTTP binding specification I have the following comment.
Currently the mapping from WSDL meps to HTTP binding  messages is
described in section 6.4.1.
Basically it says that the wsdl input message is the http request
message and the wsdl output message, if any is the http response
message.
I wonder whether this description is sufficient for the inonly and
especially robust-inonly wsdl meps.
At least, we might need to specify the HTTP code to use in the response,
especially for the robust-inonly.
Should it be 200, 202 or left unspecified as it is currently?
Are there other things that need to be specified?
What do you think?
    Youenn

Received on Wednesday, 15 November 2006 21:42:58 UTC