| Summary | HTTP uses the 5xx series of status codes to indicate failure due to a server error. An INSTANCE MUST return a "500 Internal Server Error" HTTP status code if the response envelope is a Fault. |
|---|---|
| Article Number | 33897 |
| Environment | Artix 5.X JAX-WS Runtime All Supported Platforms |
| Question/Problem Description | When a java exception is thrown from a server, it returns a "500 Internal Server Error" HTTP status code. |
| Clarifying Information | |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | Artix 5.5 Java supports WS-I Basic Profile 1.1. See notes section for the release documents. In Jax-WS if a service declares custom faults then it gets translated as Java exceptions. All java exceptions thrown in an operation results as a SOAP fault. SOAP fault are the basic type of exception being able to carry SOAP related information. Faults that are not mapped to any standard exception will cause this exception to be thrown. Hence all Java exceptions will result in "500 Internal Server Error" HTTP status code. This is in adherence to WS-I basic profile WS-I Basic Profile states HTTP Server Error Status Codes. HTTP uses the 5xx series of status codes to indicate failure due to a server error. An INSTANCE MUST return a "500 Internal Server Error" HTTP status code if the response envelope is a Fault. See related notes section for the link. Service Specific Exception:
A service specific Java exception is mapped to a wsdl:fault element, a wsdl:message element with
a single child wsdl:part element and an XML Schema global element declaration
|
| Workaround | |
| Notes |
"Related Articles" :
|
| Attachment |
| Created date: | 08 August 2012 |
|---|---|
| Last Modified: | 12 February 2013 |
| Last Published: | 10 August 2012 |
| First Published date: | 08 August 2012 |
#KnowledgeDocs
#Orbix
