I believe that, at the very least, the server-side exceptions should be SoapFault or BaseFault, depending on whether WSRF is used in the WSDL. It would also be nice to have wsdl2java generate the fault classes for custom fault types, since all that is involved is sub-classing [SoapFault|BaseFault] and adding the constructors of the base class. Can you open a JIRA item for this? It will be low priority for 2.2, probably going into 2.3, because Andrew already has a full plate on wsdl2java stuff.
In the meantime, adding your custom faults can be done manually by subclassing the BaseFault class - all you have to do is add the constructor(s) and you're ready to go. On the client side, I believe the faults should remain as SoapFaults since the methods may throw networking/WS-A faults as well as your custom faults. Dan "Baseer Khan \(bakhan\)" <[EMAIL PROTECTED]> wrote on 02/08/2007 02:15:38 AM: > I have a general question on How are faults handled in Muse Client and > Server. > > For a given operation X defined as some porttype in a wsdl that throws > faults F1 and F2 I see the following happening when wsdl2java is run - > > On Server Side: > 1) All operations defined as some capability are shown as throwing > generic Exception. > > On Client Side: > 1) All operations defined as part of Proxy are shown as throwing > SoapFault. > > In either of these cases I do not see code for Faults F1 and F2 added by > wsdl2java. > > Questions - > > How should faults be handled on server and client in view of > WS-BaseFaults Specification? General outline or guidelines would be much > appreciated. > > > Thanks. > > --Baseer > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
