I guess my problem is that the error message isn't really clear, I'm in
a situation of putting an API out there to third parties, and so I've
gone with a pretty strict API to make message validation easier, but I'm
finding ADB error messages to be rather terse and uninformative. So I'm
kind of
Sorry wrong thread
From: Geoff Peart [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2007 9:04 AM
To: axis-user@ws.apache.org
Subject: RE: wsdl2java question
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent
complex validation scenario's?
From: Amila Suriarachchi [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2007 12:13 AM
To: axis-user@ws.apache.org
Subject: Re: Improved Error Response for Bad Requests on ADB
On 8/31/07, Geoff Peart [EMAIL PROTECTED
: Friday, August 10, 2007 6:00 PM
To: axis-user@ws.apache.org; Geoff Peart
Subject: RE: Improved Error Response for Bad Requests on ADB
This is a known bug in Axis2 1.2 but seems to be resolved in 1.3.
Regards,
Jorge Fernández
Geoff Peart [EMAIL PROTECTED] escribió:
Using the default Data Binding
Using the default Data Binding, a badly formed request gets meaningless
runtime exceptions making it difficult for a client to develop and debug
their application. Is there a way to either override this behaviour, or
plug-in better error handling? I don't want to get in and edit the
generated
Is there more detailed information available on authoring the
service.xml file? What I'm specifically attempting is to include my
copies of the WSDL and XSD in the AAR and have them referenced by the
?WSDL and ?XSD request parameters.
What further complicates my issue is that my XSD imports a
