I dont know the details, but 1. Throw an AxisFault or a SoapFault and it should go over the wire as a soapfault+ADs- Declare you throw java.rmi.RemoteException and you can throw these, BTW. All proxy services built from a WSDL declaration throw RemoteException automatically
2. To send other exceptions over the wire, try working with a recent (post 1.0 build) ----- Original Message ----- From: +ACI-Mitch Gitman+ACI- +ADw-mgitman+AEA-usa.net+AD4- To: +ADw-axis-user+AEA-xml.apache.org+AD4- Sent: Monday, November 18, 2002 3:16 PM Subject: Re: +AFs-want exceptions in Java interface+AF0- Well, I wound up working around the Axis tools+IBk- taking exception to Exception. I stripped the unwanted byproducts of java.lang.Exception from the WSDL that Java2WSDL had generated. Then WSDL2Java worked just fine. I guess I will just incorporate this editing of the .wsdl into my build. Still, there must be a more elegant solution. Something so basic as throwing an Exception in your Java interface should not require a workaround. Perhaps someone else on this list has had a similar experience. Mitch Gitman +ADw-mgitman+AEA-usa.net+AD4- wrote: I have a minimal Java interface that I want to expose as a web service. Most of the methods in this interface throw a custom exception derived from Exception. Ultimately, through my RPC web service, I want these exceptions to translate into SOAP faults. My understanding is that I don't have to be introducing AxisFault or SOAPFault objects into this interface.
