#8 R0004: Contradiction with SOAP 1.2 HTTP binding

[David]

R0004 says:

A SERVICE SHALL at least implement the Responding SOAP Node of an HTTP one-way Message Exchange Pattern where the SOAP ENVELOPE is carried in the HTTP Request and the HTTP Response has a Status Code of 202 Accepted.

The requirment relaxes dwps:R0030 in the sense that a service is allowed to respond with SOAP fault messages. However, some SOAP fault messages require the service to set an HTTP status code other than 202, according to [1]. This contradicts with R0004, so I suggest to rephrase the requirement or cut the status code out:

A SERVICE SHALL at least implement the Responding SOAP Node of an HTTP one-way Message Exchange Pattern where the SOAP ENVELOPE is carried in the HTTP Request and an HTTP Response MESSAGE can contain a SOAP fault.

or

A SERVICE SHALL at least implement the Responding SOAP Node of an HTTP one-way Message Exchange Pattern where the SOAP ENVELOPE is carried in the HTTP Request.

[1] https://www.w3.org/TR/2007/REC-soap12-part2-20070427/#http-bindrespnode

[Stefan Schlichting]

Proposed change of requirement

A SERVICE SHALL at least implement the Responding SOAP Node of an HTTP one-way Message Exchange Pattern where the SOAP ENVELOPE is carried in the HTTP Request and the HTTP Response has either a Status Code of 202 Accepted or contains a SOAP FAULT in case of an error.

Add a note: That in case of a SOAP FAULT the HTTP status code indicate an error.