[Mono-bugs] [Bug 81886][Nor] Changed - SoapException / Fault does not deserialize detail field (expects namespace)

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by tekhedd at byteheaven.net.

http://bugzilla.ximian.com/show_bug.cgi?id=81886

--- shadow/81886	2007-06-15 19:00:58.000000000 -0400
+++ shadow/81886.tmp.16402	2007-06-15 20:32:48.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 81886
 Product: Mono: Class Libraries
 Version: 1.2
-OS: 
+OS: unknown
 OS Details: CentOS 4.2
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: Sys.Web.Services
 AssignedTo: atsushi at ximian.com                            
 ReportedBy: tekhedd at byteheaven.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -64,6 +64,22 @@
 namespace somehow? Possibly somebody is enough of a SOAP expert to know
 which part is broken? 
 
 My coworker assures me that this works in .NET, but I have not confirmed that.
 
 (Note, the same may apply to the Fault12Reader...)
+
+------- Additional Comments From tekhedd at byteheaven.net  2007-06-15 20:32 -------
+Update: on additional reading of the spec, it appears to be incorrect
+to write and expect a namespace on the "detail" element of soapenv:Fault.
+
+From the 1.1 spec: "When a MESSAGE contains a soap:Fault element its
+element children MUST be unqualified." 
+
+1) FaultReader shojld probably expect an empty namespace on the detail
+element.
+
+2) FaultReader should probably not write the detail element in the
+soap namespace.
+
+Am I right here? If someone confirms this I can easily make a patch.
+(Not that a change this simple really requires a patch...but..)