Gul, AFAIK, you have nowhere to introduce the possible/optional fault in WSDL 1.1 for the in-only MEP. And, robust-in-only MEP is applicable only to WSDL 2.0. Therefore, AFAIK again :), you cannot let your client expect an exception from the service if you use WSDL 1.1.
Instead of <fault>, WSDL 2.0 introduces <outfault> element that can be used for robust-in-only MEP. Hope this[1] perfect document helps you out. Regards, Ali Sadik Kumlali [1] http://www.pacificspirit.com/Authoring/async/async-scenarios.html ----- Original Message ---- From: Gul Onural <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, November 6, 2006 7:48:32 PM Subject: RE: AxisFault and fault definition in the wsdl Thanks Ali. You mentioned that <wsdl:fault> cannot be used with in-only MEP. What is the right thing to do with the in-only MEP to let the client know about the exception which occurred in the service ? Can <wsdl:fault> be used for the robust-in-only MEP? -----Original Message----- From: Ali Sadik Kumlali [mailto:[EMAIL PROTECTED] Sent: Monday, November 06, 2006 10:50 AM To: [email protected] Subject: Re: AxisFault and fault definition in the wsdl Gul, Please see my comments inline. Regards, Ali Sadik Kumlali >----- Original Message ---- >From: Gul Onural <[EMAIL PROTECTED]> >To: [email protected] >Sent: Monday, November 6, 2006 5:20:37 PM >Subject: AxisFault and fault definition in the wsdl >AxisFault and fault definition in the wsdl >- If I want my service implementation methods (operations in wsdl terms) to throw AxisFault >how do I define this in the wsdl ? Do I need to use wsdl:fault ? Is there such an example ? <!-- WSDL 1.1 --> <portType name="AccountServicesPortType"> <operation name="OpenAccount"> <input message="tns:OpenAccountSoapIn" /> <output message="tns:OpenAccountSoapOut" /> <fault name="BusinessException" message="tns:BusinessExceptionSoapFault" /> </operation> </portType> Please note that, this is only applicable to in-out(two way) services. You cannot use <wsdl:fault> with in-only MEP. Also, WSDL2Java can happily handle <wsdl:fault>. >- If my service methods throw AxisFault, and if my client is not >written in Axis2, what needs >to be done in the client code to catch these exceptions? If service sends and error back, client will get an SOAPFault not and AxisFault. So, it doesn't matter whether the service side throws AxisFault or XYZException. But, SOAP stack used at service side must be able to create a SOAPFault from the exception thrown by the backend system. >- What is the relationship between SOAPFault and AxisFault ? No direct relation. Axis2 creates SOAPFault when it gets an AxisFault and sends it to caller. >Gul --------------------------------------------------------------------- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
