This week's book giveaway is in the OO, Patterns, UML and Refactoring forum.
We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line!
See this thread for details.
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


JavaRanch » Java Forums » Java » Web Services
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://aspose.com/file-tools
 
subject: AxisFault not propagated
 
It's not a secret anymore!