HTTP error codes are different from SOAP Faults. According to the WS-I Basic Profile:
3.4.7 HTTP Server Error Status Codes HTTP uses the 5xx series of status codes to indicate failure due to a server error. R1126 An INSTANCE MUST return a "500 Internal Server Error" HTTP status code if the response envelope is a Fault. SOAP defines four standard fault codes: - Client: indicates a user exception; the client must fix the request before resubmitting - Server: indicates a server problem rather than a user exception; client should be able to resubmit the request without change - VersionMismatch: the SOAP namespace doesn't match - MustUnderstand: the server didn't know how to process a required header block (Note that Axis's use of the fault code Server.UserException makes no sense -- if it's a user exception it should return the Client fault code. Also the WS-I Basic Profile says use of the dot notation is NOT RECOMMENDED.) The actual content in the fault string is application-specific. Anne On 6/28/05, Kor Liah <[EMAIL PROTECTED]> wrote: > Hi, > > The fault String as I see contains a "free text" > Are there any constants that I can compare it too or should I just look > for substrings I expect to be there like "500" for Http error code 500? > > Thanks. > > > > > > Liah Kor > > Comverse > > VxV Insight4 > > Tel: 03-6452309 > > > > -----Original Message----- > From: Anne Thomas Manes [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 28, 2005 1:51 PM > To: [email protected] > Subject: Re: Detecting exact fault from AxisFault. > > You get that information from the fault string. > > On 6/27/05, Kor Liah <[EMAIL PROTECTED]> wrote: > > > > > > > > Hi, > > > > I would like to know if there is a way to distinguish between > > different axis faults for example to know whether an axis fault is for > "connection refused" > > , "bad request" > > > > or "request time out" (except taking it from the fault string). > > > > > > > > Liah Kor > > > > Comverse > > > > VxV Insight4 > > > > Tel: 03-6452309 > > > > > > > ______________________________________________________________________ > This email message has been scanned by PineApp Mail-Secure and has > been found clean. > > > >
