SOAP 1.2 Fault children qualified

[Sim Kim]

Hi All,

I created a WebService using SOAP 1.2 bindings and the SOAP Fault which I got looked like this :

 <S:Envelope xmlns:S="http://www.w3.org/2003/05/soap-envelope">
   <S:Body>
      <S:Fault xmlns:ns3="http://schemas.xmlsoap.org/soap/envelope/">
         <S:Code>
            <S:Value>S:Receiver</S:Value>
         </S:Code>
         <S:Reason>
            <S:Text xml:lang="en">Negative number cant be added!</S:Text>
         </S:Reason>
         <S :mrgreen: etail>
            <ns2:AddNumbersException xmlns:ns2="http://server.fromjava/">
               <detail>Numbers: -1, 0</detail>
               <message>Negative number cant be added!</message>
            </ns2:AddNumbersException>
            <ns2:exception class="fromjava.server.AddNumbersException>
               <message>Negative number cant be added!</message>
               <ns2:stackTrace>    

The chilren of Fault are qualified .

In SOAP 1.1 , I get the following message :

 <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
   <S:Body>
      <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
         <faultcode>S:Server</faultcode>
         <faultstring>Negative number cant be added!</faultstring>
         <detail>
            <ns2:AddNumbersException xmlns:ns2="http://server.fromjava/">
               <detail>Numbers: -1, 10</detail>
               <message>Negative number cant be added!</message>
            </ns2:AddNumbersException>
            <ns2:exception class="fromjava.server.AddNumbersException" >
               <message>Negative number cant be added!</message>             </ns2:exception>
         </detail>
      </S:Fault>
   </S:Body>
</S:Envelope>
   

Is this a change in SOAP 1.2 ?

[Peer Reynders]

SOAP 1.1
4.4 SOAP Fault

The http://schemas.xmlsoap.org/soap/envelope/ schema does not specify an 'elementFormDefault' attribute. That means that it defaults to "unqualified". This means that (local) subelements are not namespace qualified. Therefore faultcode, etc MUST be unqualified which is emphasized by the WS-I Basic Profile 1.0
4.1.3 SOAP Faults and Namespaces


SOAP 1.2
The http://www.w3.org/2003/05/soap-envelope/ schema specifies 'elementFormDefault="qualified"' which means that local subelements are namespace qualified. That means that the subelements of {http://www.w3.org/2003/05/soap-envelope/}Fault have to have a namespace prefix as their namespace isn't the default namespace.

The 'elementFormDefault' issue is discussed at length here. It is at this point that I really started to hate XML Schema ...

[Chintan Rajyaguru]

Also, it is important to note that the new exam uses Basic Profile 1.1, which still refers to SOAP 1.1 and states that the children of fault must be unqualified but the details tag under fault can have qualified elements. So, your first sample is SOAP 1.2 valid but not Basic Profile 1.1 compliant.

[Sim Kim]

But the exam also refers to SOAP 1.2 .
So how do we deal any such question in exam ?
[ November 13, 2008: Message edited by: Sim Kim ]

[Chintan Rajyaguru]

No right answer here but here is what I would do:
If it's an interoperability question, use SOAP 1.1
If it's a SOAP question use SOAP 1.2
If in doubt use SOAP 1.1 because that's what is referenced most of the time.

[Faraz Ali]

Hi Sim Kim,

Thanks for pointing out this issue. I fear that i studied SOAP 1.1. Now started reading SOAP 1.2. Here is a point about SOAP fault.

In SOAP 1.2, faultcode, faultstring, actor are changed to Code, Reason and Role. And it defines a new element Node.

Can you mention any good articles which describe the differences between SOAP 1.1 and 1.2? And what do you think how big is the change from 1.1 to 1.2?

Thanks,

[Sim Kim]

Here is one article which give the difference :

http://www.idealliance.org/papers/xmle02/dx_xmle02/papers/02-02-02/02-02-02.html