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 [EMAIL PROTECTED] 2003-04-01 10:34 ------- Hi, I want to add a comment to help your understand of the table on the last message. Here's the the background. .........*.........*.........*.........*.........*.........*.........* [Definition of SOAP Envelope] A SOAP message is an XML document that consists of a mandatory SOAP envelope, an optional SOAP header, and a mandatory SOAP body. (from: <http://www.w3.org/TR/2000/NOTE-SOAP-20000508/>) +-----<SOAP Envelope>-----+ | | | ....<SOAP Header>.... | | : : | | : (OPTIONAL) : | | :...................: | | | | +----<SOAP Body>----+ | | | | | | | (REQUIRED) | | | | | | | +-------------------+ | +-------------------------+ [The message style of the HTTP bindings] +-----------------------------+ |[Request-Line | Status-Line] | <--- [HTTP Header] | *(message-header CRLF) | +-----------------------------+ CRLF +-----------------------------+ | +-----<SOAP Envelope>-----+ | <--- [HTTP Massage] | | | | | | ....<SOAP Header>.... | | | | : : | | | | : (OPTIONAL) : | | | | :...................: | | | | | | | | +----<SOAP Body>----+ | | | | | | | | | | | (REQUIRED) | | | | | | | | | | | +-------------------+ | | | +-------------------------+ | +-----------------------------+ [Responsibility for the handling of the payload] *(Legend) SI: SOAP Intermediary RT: JAX-RPC RunTime Service SH: JAX-RPC SOAP Message Handlers WS: Web Services of the target endpoint +----------------------+-------------------+------------------+ | Targets |Handling capability| Remarks | +======================+===================+==================+ | HTTP Header | IS | RT | SH | WS | (samples) | | +--------------------+----+----+----+----+------------------+ | |Request-Line |Yes |Yes | - | - |POST /WS HTTP/1.1 | | |Status-Line |Yes |Yes | - | - |HTTP/1.1 200 OK | | |SOAPAction |Yes |Yes | - | - |SOAPAction: "" | | |(Others) |Yes |Yes | - | - | - | +----------------------+-------------------+------------------+ | HTTP Message | IS | RT | SH | WS | (samples) | | +--------------------+----+----+----+----+------------------+ | |SOAP Envelope | - |Yes | - | - |<Envelope> | | |SOAP Header Node |Yes |Yes |Yes | - |<Header> | | |SOAP Header Contents|Yes | - |Yes | - | - | | |SOAP Body Node | - |Yes |Yes | - |<Body> | | |SOAP Body Contents | - | - |Yes |Yes | - | +----------------------+-------------------+------------------+ (Points): - A SOAP Envelope should be handled by the runtime system. ==> The SOAP Message will be null when the runtime doesn't generate a SOAP envelope. - A SOAP Body Content should be handled only by user programs such as Web Services or handler impl. ==> The contents should be null when the end-point is a void return type, furthermore, the handler doesn't exist or the handler doesn't create any SOAP elements. Any comments and helps will be appreciated. Best Regards, Toshi (Toshiyuki Kimura) <[EMAIL PROTECTED]> R&D Headquarters NTT DATA Corporation
