I would need custom exceptions too and, as Sacha said, it's not a good idea to build a strong dependency to Axis classes. In my project I have to implement an API which offers an web service and I would like to let a customer decide what SOAP middleware to be used. Right now it's strongly tied to webMethods/TME GLUE. But I would like to support Axis too, the only thing is, I could not get custom exceptions working ...
Just to mention: in GLUE (both sides, server and client use GLUE) I have now a web service working, where on the client side even RuntimeExceptions, for example java.lang.IllegalArgumentException, do appear correctly. Merten > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Monday, March 29, 2004 10:26 AM > To: [EMAIL PROTECTED] > Subject: Re: custom exceptions > > > Have you tried extending AxisFault? That's what we do and > it seems to > work well enough... > > Hi. > > Thanx for reply. I don't think it is a right way. It strictly > tides You to > axis architecture of Your service. In my situation I want to have web > service interface to EJB deployed on JBoss. Methods of this bean uses > their own exception hierarchy and it's impossible to extend AxisFault. > > As I see, Nelson Minar has similar problem - could You tell mi what is > this Utils.convertException method? I can't find it in axis 1.1 api. > > MJS > >
