??? I'am using the axis version provided with the jdbuilder webservice
development kit. ( Beta 1 Release )
And custom exception handeling work.
There are limitation, the class generated with the wdsl, should not
contains any fields. And if the class is modified, It have to have a
default constructor.
But it works,
By custom exception handling, does not simply mean, throwing exception that
have other fields that the AxisFault ?
Heiko Braun :
You have to trace the remote call in the debbuger to known what's
happening.
The AxisFault Exception is created using the class name provided in the
message message body ( some where in SoapFaultBuilder:endElement )
Since the dynamic class instanciation is surounded by a empty try-catch. If
the axis is unable to clear the exception class, it will fall back to a
axisfault.
It is the way that I detected that an Custom Exception must have a default
constructor.
Dominique
|---------+--------------------------->
| | <Geza.Szocs@noki|
| | a.com> |
| | |
| | 10/09/02 01:36 |
| | PM |
| | Please respond |
| | to axis-user |
| | |
|---------+--------------------------->
>-------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: <[EMAIL PROTECTED]>
|
| cc: (bcc: Dominique Gallot/BRU/MASTERCARD)
|
| Subject: RE: custom exception not thrown anymore
|
>-------------------------------------------------------------------------------------------------------------------------------|
It is strange that you could catch your own exception, because as far as I
know
custom exception handling is not implemented neither in beta3 nor in 1.0. :
(
(I may have miss something myself though)
> hi,
> i have a client which works on wsdl generated files.
> the stub method i am calling throws a custom exception
> produced on the server side:
>
> public org.company.MyExcp askSomething(String question throws
> java.rmi.RemoteException, org.company.MyExcp;
>
> i was able to catch this exception prior to axis 1.0,
> but since i moved to axis 1.0 it always turns out as a
> AxisFault instead of org.company.MyExcp.
>
> did i miss something between beta 3 and 1.0 ?
> does anyone have an idea where to start looking?
