This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
If you look at: http://docs.oasis-open.org/ws-rx/wsrm/200702/wsrm-1.2-spec-os.html#_Toc163438671 you'll see there's table that show how both soap11 and soap12 sender/receiver are mapped. We only show soap12 - we need to add soap11.
Created attachment 948 [details] proposal Proposal is in the word doc. It consists of: - a minor wording change - add a row to the soap fault table - remove the "S12:" from each fault we define and do this for all specs that defined faults
resolved as proposed
It seemed like a easy change. But after taking a closer look I have this question: Accourding to WS-Addressing 1.0 SOAP Binding [1] cited by WS-E, the SOAP 1.1 fault messages do not contain Code property (whereas SOAP 1.2 does). Therefore, defining Code property for SOAP 1.1 has no effect on the wire. Proposal 1: keep the Code property by saying that we extend [1]. We also need to update the SOAP 1.1 fault message template to include the [Code]. One way is to bind it to <faultactor>[Code]</faultactor>. Proposal 2: remove the Code property from the SOAP 1.1, i.e. CWNA. [1] http://www.w3.org/TR/ws-addr-soap/#id2270287
Actually, I'd prefer to just remove those lines of text from the spec. Meaning remove: - - - - For SOAP 1.2, the [Code] property MUST be either "Sender" or "Receiver". These properties are serialized into text XML as follows: <table> SOAP Version Sender Receiver SOAP 1.2 s12:Sender s12:Receiver </table> - - - - - We don't need the mapping table since each Code property already has either s12:Sender or s12:Receiver - this makes the table pointless.
Proposal in comment #4 works for me too.
Thru the mailing list the group agreed to do comment #4
Please make my changes