SOAP Fault Message Example

When the code within a Web service raises an exception anywhere in the Web services stack, the exception is caught and transformed into a SOAP fault message.

For instance, the following example illustrates a particular case where mustUnderstand has been set to 1; and therefore, the header is interpreted as being mandatory. However, the corresponding filter and handler to process the header was not defined. This causes a SOAP fault message to be returned.

The format of the Siebel SOAP fault message for this example follows:

  <?xml version="1.0" encoding="UTF-8" ?> 
	- <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
			- <SOAP-ENV:Body>
				- <SOAP-ENV:Fault>
						<faultcode>SOAP-ENV:MustUnderstand</faultcode> 
						<faultstring>Unable to process SOAP Header child element
 							'newns:AnotherUselessHeader' with 'mustUnderstand="1"'(SBL-EAI-08000)
  							</faultstring>
						- <detail>
 						- <siebelf:errorstack xmlns:siebelf="http://www.siebel.com/ws/fault">
 						- <siebelf:error>
  							 <siebelf:errorsymbol /> 
  							  <siebelf:errormsg>Unable to process SOAP Header child element
    								 'newns:AnotherUselessHeader' with 'mustUnderstand="1"'(SBL-EAI-08000)
     							</siebelf:errormsg> 
   							 </siebelf:error>
   							</siebelf:errorstack>
  						</detail>
					</SOAP-ENV:Fault>
				</SOAP-ENV:Body>
			</SOAP-ENV:Envelope>

For more information on SOAP fault handling, see About SOAP Fault Schema Support.