The user guide for Axis 1.4 states:

*"If a method is marked as throwing an Exception that is not an instance or
a subclass of java.rmi.RemoteException, then things are subtly different.
The exception is no longer a SOAP Fault, but described as a wsdl:fault in
the WSDL of the method. According to the JAX-RPC specification, your
subclass of Exception must have accessor methods to access all the fields in
the object to be marshalled and a constructor that takes as parameters all
the same fields (i.e, arguments of the same name and type). This is a kind
of immutable variant of a normal JavaBean. The fields in the object must be
of the datatypes that can be reliably mapped into WSDL.*

*If your exception meets this specification, then the WSDL describing the
method will describe the exception too, enabling callers to create stub
implementations of the exception, regardless of platform."*

Is there more details on how to implement/configure this?  Better yet, is
there an example for this using Axis 1.x?

Regards,

Josh

Reply via email to