Hi Amila,
Sorry for the late response but I've been very busy last days trying to finish
my final project to get my degree.
Yes it is true that when there is a NPE the excepcion should be thrown as Axis2
fault. As you can see, in exception A, the message contains an Axis2 fault and
is well
<<
expected element name>>"
And use fully qualified names with namesapce. please see the
ADBBeanTemplate.xsl.
Amila.
Has anyone else tackled complex validation scenario's?
>
>
>
>
> --
>
> *From:* Amila Suriarachchi [mailto:[EMAI
Has anyone else tackled 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,
ructure, and do my validation in code, or leave my 3rd
parties with obscure error messages?
I'm hoping there is a 3rd choice I've missed?
Thanks
-
From: Jorge Fernandez [mailto:[EMAIL PROTECTED]
Sent: Friday, August 1
; I'm hoping there is a 3rd choice I've missed?
>
>
>
> Thanks
>
>
> --
>
> *From:* Jorge Fernandez [mailto:[EMAIL PROTECTED]
> *Sent:* Friday, August 10, 2007 6:00 PM
> *To:* axis-user@ws.apache.org; Geoff Peart
> *Subject:* RE: I
gust 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
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, a
badly formed request gets meaningless
runtime exceptions making it difficult for a client to develop and debug
their application
