This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
ws-eventing says: All fault messages defined in this specification MUST be sent according to the rules described in WS-Addressing section 4. They are sent to the [fault endpoint], if present and valid. Otherwise they are sent to the [reply endpoint] if present. If neither is present faults may be sent to the [source endpoint]. This duplicates WS-Addressing, is technically wrong w.r.t the source endpoint and we can't mandate that faults are sent - just transmitted. Proposal: Remove this paragraph.
actually, its worse, the next paragraph has this: Endpoints compliant with this specification MUST include required message information headers on all fault messages. Fault messages are correlated as replies using the [relationship] property as defined in WS-Addressing. which should be removed too. WS-Transfer uses this text: All fault messages defined in this specification MUST be sent according to the rules and usage described in WS-Addressing 1.0 SOAP Binding Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults. which we could use if people really wanted to have something. Either way, we should make all WSRA specs consistent with whatever we decide.
resolved with: WS-Transfer uses this text: All fault messages defined in this specification MUST be sent according to the rules and usage described in WS-Addressing 1.0 SOAP Binding Section 6 for encoding SOAP 1.1 and SOAP 1.2 faults.