I'm also fairly new to Axis2 web services but I have been able to develop a service that includes two custom exceptions. Both my service and client use code generated by WSDL2Java (the Eclipse plug-in, but would expect the other version to product the same results). I'm using Axis2 1.3.
The actual Java exception classes simply extend java.lang.Exception and contain a reference to a MyCustomFault object which is not derived from AxisFault but from (in my case, since I'm using ADB) ADBBean. I believe that the codegen handles the conversion to and from SOAP faults MyCustomFaults and MyCustomFaultExceptions. Are you having these problems with generated code or are you hand-coding the lower-level parts of your service and/or clients? - Steve "Joseph P. Berglund" <[EMAIL PROTECTED]> wrote on 03/24/2008 04:22:50 PM: > I have had a similar problem. I am a fairly new user myself, but it > looks like the exception is always cast as an AxisFault when it > returns to the client. You could try extending the AxisFault class > for your custom exception. > ----- Original Message ---- > From: Adrián Cuartero <[EMAIL PROTECTED]> > To: [email protected] > Sent: Monday, March 24, 2008 2:47:32 PM > Subject: Capture custom exception > Hi all > > I keep trying throwing a custom exception and i've read there's a > problem capturing this exception in the client side. > > Anyone knows how to capture this custom exceptions? > > Thanks > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
