Contents
- 1 How are exceptions handled using soap faults in Java?
- 2 What is the purpose of the SOAP < fault > element?
- 3 What does the reason element in a SOAP node do?
- 4 How is the fault element defined in SOAP 1.2?
- 5 What to do in the case of a SOAP error?
- 6 How to get the HTTP status code from the SOAP response?
How are exceptions handled using soap faults in Java?
In JAX-WS, Java exceptions ( java.lang.Exception) that are thrown by your Java Web service are mapped to a SOAP fault and returned to the client to communicate the reason for failure. SOAP faults can be one of the following types:
What is the purpose of the SOAP < fault > element?
The SOAP element is used to transmit error and status information within a SOAP message. The element is a child of the body element. There can be only one element in the body of a SOAP message.
When is a SOAP fault returned to the sender?
The faults are returned to the sender only if request/response messaging is in use. If a Web service operation is configured as one-way, the SOAP fault is not returned to the sender, but stored for further processing. As illustrated in Figure 16-1, JAX-WS handles SOAP fault processing during SOAP protocol binding.
What does the reason element in a SOAP node do?
The element contains one or more elements, each of which contains information about the fault in a different language. Information regarding the actor (SOAP node) that caused the fault. Role being performed by actor at the time of the fault.
How is the fault element defined in SOAP 1.2?
The element is a child of the body element. There can be only one element in the body of a SOAP message. The SOAP element contents for SOAP 1.2 and 1.1 are defined in the following sections: The element for SOAP 1.2 contains the subelements defined in Table 16-1. Required?
How to handle a SOAP fault in WCF?
Attach the customized SOAP fault to the operations by using the FaultContractAttribute. Check for the error condition and raise the Customized SOAP fault in service operations. Handle the SOAP faults at the client side. Here I am going to explain all the above steps by using a sample WCF Service.
What to do in the case of a SOAP error?
In case of a SOAP error while processing the request, the SOAP HTTP server MUST issue an HTTP 500 “Internal Server Error” response and include a SOAP message in the response containing a SOAP Fault element (see section 4.4) indicating the SOAP processing error. An element in the SOAPBody object that contains error and/or status information.
How to get the HTTP status code from the SOAP response?
No exception and no SOAPFault means the return code was 200 to 206, all of which are “SUCCESS” – unfortunately the status entry from the HTTP headers in the HttpURLConnection object is explicitly not copied to the MIMEHeaders in the returned SOAPMessage // Header field 0 is the status line so we skip it.
What happens when the SOAP server sends an HTTP 500 error?
In case of a SOAP error while processing the request, the SOAP HTTP server MUST issue an HTTP 500 “Internal Server Error” response and include a SOAP message in the response containing a SOAP Fault element (see section 4.4) indicating the SOAP processing error. And from documentation on SOAPFault in the API.