RE: Clarifying assertion for HTTP Location

"Jonathan Marsh" <[email protected]>
Newsgroups gmane.comp.web.services.description
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: [email protected] [mailto:[email protected]] On
Behalf Of John Kaputin (gmail)
Sent: Monday, December 18, 2006 3:56 AM
To: [email protected]
Cc: [email protected]
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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.