Chris, I do not throw the Axis Fault, I throw my own exception. It gets 'wrapped' in the Axis Fault. I can get the message out of the Axis Fault through the fault code and fault message accessors. That is what I am doing now...
On the client side, I have to catch a Axis Fault. I would prefer it if I could catch the explicit fault that I am throwing. (As this lends itself to figuring out what the error is, and so forth.) My problem is that I would like the Axis Fault 'deserialized' into the correct kind of fault. I realize that this is probably not handled in Axis right now. Are there plans to do so? Is there an easy change within the Axis code that I could make in order for this to take place? Thanks for you help, Barbara -----Original Message----- From: Chris Haddad [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 2:40 PM To: [EMAIL PROTECTED] Subject: RE: Fault Handling Barbara - The Axis framework currently does not map custom fault objects. If you do not throw an AxisFault, the framework will only map the base exception message (i.e. e.getMessage()). The faultcode and faultmessage will be set to a default Axis constant. Is the problem that you can't catch the exception, or that you are not getting back the expected faultcode and faultmessage? Is this on the server or client? Can you post the relevant code snippet? /Chris -----Original Message----- From: Barbara Noble [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 02, 2002 11:38 AM To: [EMAIL PROTECTED] Subject: Fault Handling Hello all, I am trying to understand how fault handling works within axis (with tomcat). I have a service, and it throws an exception. When I deploy the service, the exception is also seen on the client. It appears in the wsdl as the 'fault msg'. HOWEVER - when thrown, it seems that the exception is being mapped in an AxisFault to be passed to the client. I cannot seem to get at the exception that is thrown. I looked in the Architecture Guide for some enlightenment, but it is still under construction. Any help with this issue would be greatly appreciated. Thanks, Barbara Noble Software Engineer Sengent, Inc. Optimized Distributed Computing http://www.sengent.com [EMAIL PROTECTED] 561.417.0664 x106
