Hello,
Thanks Sunil, I have already seen people subclassing AxisFault, but I refuse doing such a thing.
MyException is a "ServiceException", and should know anything about being published with Axis.
Imagine just tomorrow I decide to move onto some other framework to publish/call Web Services.
Then what, should I subclass some other different FrameworkFault? Of course not.
My idea is to get grip of that XML provided in the AxisFault on the client Stub, unwrap MyException and throw it,
so that the stub throws true MyException instances (or RemoteExceptions, if some ConnectRefused-like occurs)
In all, I�ll keep on trying, and thanks a lot for your comment.
Mariano.
Sunil Kothari wrote:
No, you don't have to do it manually. Just make sure that your WSDL correctly reflects the structure of MyException. I found that java2wsdl tool somehow misses the structure of application-specific exceptions. To get hold of the exception use try-catch mechanism. Note that MyException should subclass AxisFault.
If you still have problems then let me know so that I can send you a sample code.
I hope that helps.
Sunil Kothari
----- Original Message -----
From: Mariano Eloy Fern�ndez <[EMAIL PROTECTED]>
Date: Wednesday, February 23, 2005 1:45 pm
Subject: Re: How do I deserialize the detail field in AxisFault to build MyException?
Hi,
Some additional notes.
The XML comes in a protected attrbute called faultDetails, inaccesible.The public detail field is null.
The question stands, How do I build MyException from this AxisFault?
Thanks,
Mariano.
Mariano Eloy Fern�ndez wrote:
XML inHello,
I am working with Axis 1.1
I have a class MyException extends Exception thrown in the Web Service. Both De/Serializer are provided for MyException.
An AxisFault is received in the client with MyException as an
the detail field of AxisFault.manually?
How do I build MyException from that XML? Do I have to do it
Then what's the MyExceptionDe/Serializer for?
Thanks,
Mariano Eloy Fern�ndez.
