--Original Message-
> From: Wally Dennis [mailto:[EMAIL PROTECTED]<[EMAIL PROTECTED]>
> ]
> Sent: Fri 7/11/2008 12:24 PM
> To: axis-user@ws.apache.org
> Subject: Re: returning meaningful errors for bad xml
>
> Are you using SOAP 1.1 or 1.2? I couldn't find specific
AIL PROTECTED]>
07/11/2008 12:31 PM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
RE: returning meaningful errors for bad xml
Ok, so how do i set it up so in my example below i tell the client exactly
what went wrong, not just the famous microso
ubject: Re: returning meaningful errors for bad xml
Are you using SOAP 1.1 or 1.2? I couldn't find specific mention of this
in the 1.2 spec, but according to section 6.2 of the SOAP 1.1 spec
(http://www.w3.org/TR/2000/NOTE-SOAP-2508/#_Toc478383507), "In case of
a SOAP error while pr
ions it MUST be done with an HTTP 500.
"Slepecki, Willie" <[EMAIL PROTECTED]>
07/11/2008 11:49 AM
Please respond to
axis-user@ws.apache.org
To
axis-user@ws.apache.org
cc
Subject
returning meaningful errors for bad xml
im building a web service using axis2 with jibx
im building a web service using axis2 with jibx as the data binder.
what i need to do is return meaningful messages when i receive a bad xml
document or a doc that doesn't comply with the rules of the schema (values not
included in the enumerations, etc). i just spent the past 3 days chasing do
