W3C home > Mailing lists > Public > www-ws-desc@w3.org > December 2006

RE: Clarifying assertion for HTTP Location

From: Jonathan Marsh <jonathan@wso2.com>
Date: Tue, 19 Dec 2006 14:47:55 -0800
To: "'John Kaputin \(gmail\)'" <jakaputin@gmail.com>, <www-ws-desc@w3.org>
Cc: <woden-dev@ws.apache.org>
Message-ID: <00ce01c723bf$baea6e40$3401a8c0@DELLICIOUS>
I don't think this binding supports mapping an output or fault to an HTTP
request message.  It only supports the in-out, in-only, and robust-in-only
MEPs, in which the input message maps to the HTTP request.

 

Jonathan Marsh -  <http://www.wso2.com> http://www.wso2.com -
<http://auburnmarshes.spaces.live.com> http://auburnmarshes.spaces.live.com

 

  _____  

From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of John Kaputin (gmail)
Sent: Monday, December 18, 2006 3:56 AM
To: www-ws-desc@w3.org
Cc: woden-dev@ws.apache.org
Subject: Clarifying assertion for HTTP Location

 

Part 2 section 6.7.1.1 Construction of the request IRI using the {http
location} property.

This section contains the assertion:

"Strings enclosed within single curly braces MUST be element names from the
instance data of the input message."

I assume 'input message' here refers generically to any input data for the
HTTP request (i.e. to a WSDL input, output or fault message element).   To
make this clearer and to keep it consistent with the description at
hyperlink "instance data", perhaps you could restate this something like:

"Strings enclosed within single curly braces MUST be element names from the
instance data of the input, output or fault message."

regards,
John Kaputin.
Received on Tuesday, 19 December 2006 22:47:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:43 GMT