axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18024] - Bad client handling of HTTP 204 NO CONTENT response
Date Thu, 17 Jul 2003 16:32:03 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18024>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18024

Bad client handling of HTTP 204 NO CONTENT response





------- Additional Comments From stevel@apache.org  2003-07-17 16:32 -------
I seems to me that if we cannot parse a one way message, then yes, we should
signal  an error. Failure to execute is a different game, oneWay means you dont
need to know if it worked or not.

But I'd assume that the caller would need to know if it got to the endpoint, and
be prepared to catch an exception if it didnt. This is implicit in that the
client cod can throw things like connection refused, 404, etc, etc, and the
caller needs to handle it, even if the handling is just to swallow the IOException.

But I guess the bigger Q is what do the soapbuilders think? Why not ask them?

Mime
View raw message