RE: Proposal to Include whttp:code to the output of the binding operation

Specifically, you'd like to see a  way to describe the "201 Created" and
"304 Not Modified" responses of PUT and POST?  FTR, there's nothing that
prevents those codes from being used with and in-out mep - though those
values are constrained when using the in-only and robust-in-only meps [2].

 

So, while adding whttp:code to binding operations might help in generating
server-side stubs, does it provide any information useful to the client?

 

[1] http://ietfreport.isoc.org/all-ids/draft-ietf-atompub-protocol-14.txt

[2]
http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20-adjuncts.html
?content-type=text/html;%20charset=utf-8#http-operation-decl-dest

 

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 keith chapman
Sent: Sunday, April 22, 2007 11:01 PM
To: www-ws-desc
Subject: Proposal to Include whttp:code to the output of the binding
operation

 

Hi all,

I wonder whteher its too late, but I think its import that it makes its way
into the spec. I was playing around with APP trying to write a WSDL for it
(Use it as a WSDL 2.0 demo). During this I came across a limitation which I
guess WSDL 2.0 should address. The HTTPBinding allows a user to set a HTTP
code on a fault but it does not allow a user to specify a http code on a
response. This is a trick that we missed.

I would like to propose the inclusion of whttp:code property to the output
of the binding operation. This will be critical for the HTTPBinding to be
succesfull. 

Thanks,
Keith.

-- 
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/