That behavior is required by the SOAP specs [1]: "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."
Andreas [1] http://www.w3.org/TR/2000/NOTE-SOAP-20000508 On Wed, Apr 10, 2013 at 11:47 AM, santosh kumar <2408.sant...@gmail.com> wrote: > Hi, > > I am facing an issue with Axis2 framework. > I am using Apache Tomcat version 7.0.25 on which i have deployed my web > service. > The issue faced is : > > 1. whenever my service throws any exception Axis throws the same exception > in XML format correctly but in RAW data we see > > HTTP/1.1 500 Internal Server Error > Server: Apache-Coyote/1.1 > Content-Type: text/xml;charset=UTF-8 > Transfer-Encoding: chunked > Date: Wed, 10 Apr 2013 08:48:13 GMT > Connection: close > > I want to know is it correct behaviour of Axis2 that in case of any > exception it should throw Error 500 (Internal Server Error). > Ideally it should throw Http code 200 along with the XML information > containing the exception raised by web service, because communication is > proper. > > If its the correct behavior then do we have any option to change this > behavior of Axis 2. > > Please suggest some valuable tips as i am stuck with it . > > With Regards > Santosh Kumar > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
