File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
A friendly place for programming greenhorns!
Big Moose Saloon
Register / Login
Win a copy of
EJB 3 in Action
this week in the
EJB and other Java EE Technologies
AxisFault not propagated
Joined: Apr 08, 2009
Apr 08, 2009 13:57:36
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
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?
All times are in JavaRanch time: GMT-6 in summer, GMT-7 in winter
| Powered by
Copyright © 1998-2014