aspose file tools
The moose likes Web Services and the fly likes AxisFault not propagated Big Moose Saloon
  Search | Java FAQ | Recent Topics
Register / Login


Win a copy of The Mikado Method this week in the Agile and other Processes forum!
JavaRanch » Java Forums » Java » Web Services
Reply Bookmark "AxisFault not propagated" Watch "AxisFault not propagated" New topic
Author

AxisFault not propagated

Mathilde Samting
Greenhorn

Joined: Apr 08, 2009
Posts: 1
Hi,

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.


Thanks

Matthias
 
I agree. Here's the link: http://ej-technologies/jprofiler - if it wasn't for jprofiler, we would need to run our stuff on 16 servers instead of 3.
 
subject: AxisFault not propagated
 
Similar Threads
error about AXIS implementation
Why cannot my own Handler work?
Axis in WSAD
AXIS 1.4 Call.invoke() - (401)Unauthorized
How to use custome exceptions with axis2?