Some parts of this message have been removed.
Learn more about Nabble's
security policy.
Thank you for this issue. We tracked it as Issue 4491 [1]
in our short Last Call period. The Working Group was reluctant to add
this new functionality at this late date (and is unsure that the benefits are
clear). Accordingly it took no action on this issue.
The spec should be in Proposed Recommendation shortly, if you
disagree with the resolution of this issue please inform us as soon as
possible.
[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=4491
Jonathan Marsh - http://www.wso2.com - http://auburnmarshes.spaces.live.com
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/
