This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11899 - All: fault section table is missing both soap versions
Summary: All: fault section table is missing both soap versions
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: All (show other bugs)
Version: CR
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
Depends on:
Reported: 2011-01-28 01:37 UTC by Doug Davis
Modified: 2015-06-20 16:35 UTC (History)
1 user (show)

See Also:

proposal (43.50 KB, application/msword)
2011-02-01 19:27 UTC, Doug Davis

Description Doug Davis 2011-01-28 01:37:00 UTC
If you look at:
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.
Comment 1 Doug Davis 2011-02-01 19:27:47 UTC
Created attachment 948 [details]

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
Comment 2 Robert Freund 2011-02-01 20:45:35 UTC
resolved as proposed
Comment 3 Li Li 2011-02-01 22:24:39 UTC
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.

Comment 4 Doug Davis 2011-02-01 23:50:45 UTC
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:
SOAP Version 	Sender 	        Receiver
SOAP 1.2 	s12:Sender 	s12:Receiver 
- - - - - 

We don't need the mapping table since each Code property already 
has either s12:Sender or s12:Receiver - this makes the table
Comment 5 Li Li 2011-02-02 19:32:28 UTC
Proposal in comment #4 works for me too.
Comment 6 Doug Davis 2011-02-07 23:51:01 UTC
Thru the mailing list the group agreed to do comment #4
Comment 7 Jackie 2015-06-20 16:34:36 UTC
Please make my changes
Comment 8 Jackie 2015-06-20 16:35:24 UTC
Please make my changes