File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Web Services and the fly likes AxisFault not propagated Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of EJB 3 in Action this week in the EJB and other Java EE Technologies forum!
JavaRanch » Java Forums » Java » Web Services
Bookmark "AxisFault not propagated" Watch "AxisFault not propagated" New topic

AxisFault not propagated

Mathilde Samting

Joined: Apr 08, 2009
Posts: 1

my Eclipse Ganymede generated AXIS Client throws a SAX Exception if the service I am calling returns a soap:Fault.

That means that the application exception info is gone once the AXIS stuff returns to my client, leaving only the SAX Exception.

How can I configure AXIS, so that it can cope with application exceptions.

The only thing I found was to implement my own handler, and making it throw an AxisFault with the desired exception info.
But thats not propagated to my client code either.


I agree. Here's the link:
subject: AxisFault not propagated
Similar Threads
Axis in WSAD
error about AXIS implementation
How to use custome exceptions with axis2?
AXIS 1.4 Call.invoke() - (401)Unauthorized
Why cannot my own Handler work?