SOAP Fault Process (SAP Library - Development Manual)

SOAP Fault Process

The following mechanisms are implemented by the PRT Web services architecture, to handle exceptions if such occurs during the SOAP message processing:

A Method Invocation on the Server Generates an Exception

This graphic is explained in the accompanying text

If an exception is thrown during the invocation of the Web service’s method, this exception is converted automatically to a SOAP fault message with the following structure:

<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:fault="http://www.w3.org/2001/12/soap-faults">

<SOAP-ENV:Body>

<SOAP-ENV:Fault>

<faultcode>%TYPE_ERROR% </faultcode>

<faultstring>%DESCRIPTION_ERROR%</faultstring>

<faultactor>%[SERVER_NAME] COMPONENT NAME%</faultactor>

<stackTrace >%JAVA_STACKTRACE%</stackTrace>

</detail>

</SOAP-ENV:Fault>

</SOAP-ENV:Body>

An External WEB Service Returns a SOAP Fault Message

This graphic is explained in the accompanying text

When a Web Service portal proxy service invokes a Web service method (1),

the PRTSOAP Call class in the PRT SOAP Framework generates the SOAP Request (2).

In the case when an error occurs in the Web Service Server (3)

during the SOAP process, a SOAP Fault message is generated by the Web service and returned as response (4).

The PRTSOAP Call converts the SOAP fault message into a PRTFault Exception (extends SOAPServiceException) (5), and throws it to the Web Portal Service Proxy.