";
class="samples.faults.NoSuchEmployeeFault"
type="tns:NoSuchEmployeeFault"
xmlns:tns="http://faults.samples"/>
> -Original Message-
> From: Stuart Barlow [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 20, 2003 8:07 AM
>
Other than the effort required to configure Axis, I don't see why it would
make much difference.
> If I have a Java interface that I am going to be turning into
> a web service (with AXIS and the Java2WSDL and WSDL2Java tools).
>
> Should I define a hierarchy of exception classes that could be
>
Well Im attempting the second approach. But with no success.
Would I be right in thinking that AXIS is still not able to
transport custom exceptions from the server to the client?
At present I am just getting an AxisFault exception on the client.
My exception dervives from Exception until I run th
If I have a Java interface that I am going to be turning into
a web service (with AXIS and the Java2WSDL and WSDL2Java tools).
Should I define a hierarchy of exception classes that could be
thrown from the server. e.g.
Exception <--- MyServiceException
MyServiceException < InvalidOperationExcep
