Thanks for replying guys. I am not able to understand the situtaion like: 1. My web service is throwing an exception(user defined exception related to my business logic:something not found etc) then in this case a soap fault is getting generated with fault string as the exception string. 2.Is this the case of soap fault? 3.Do this soap fault resulting into http 500 Internal server error. 4.can you please let me know any authentic document where i can find that soap fault gets created when web service throws customized exceptions. 5.How can i prove this to my management,they are not able to understand this.They are saying that in case of exception also the http code should be 200 ,because this is the OK case for the application as application has behaved properly and sent No data found exception.
Please anybody help me out in this. Thanks. *With Regards* *Santosh Kumar* <http://www.aricent.com/> <http://www.aricent.com/> On Wed, Apr 10, 2013 at 4:04 PM, Andreas Veithen <andreas.veit...@gmail.com>wrote: > 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 > >
