> -----Original Message----- > From: Jim Murphy [mailto:[EMAIL PROTECTED] > Sent: Thursday, September 16, 2004 1:05 PM > To: [EMAIL PROTECTED] > Subject: Re: .NET interorperability issue? > > I'm not sure the exception throwing semantics you expect are > supported across toolkits and particularly with the .NET > client. Though .NET certainly has its own exception > propagation convention. SOAP 1.1 [1] doesn't have much to > say on the matter. > > Can anyone else comment on this? I know its something thats > kinda cool with Axis client and Axis Servers but should we > expect it to interop? > > Jim Murphy > Mindreef, Inc. > > [1] - http://www.w3.org/TR/2000/NOTE-SOAP-20000508/#_Toc478383507
Well, it definetly won't interop with platforms that don't have exceptions (like COM). I'd highly recommend that you use soap faults as they were intedended and return your own faultcode qnames, rather than returning a generic faultcode qname and burying the real fault info in the detail, e.g. <soapenv:Fault xmlns:sf="http://www.simon.fell.com/faults";> <faultcode>sf:InvalidStartDate</faultcode> <faultstring>The start date parameter must be within the last 12 months</faultstring> <detail /> </soapenv:Fault> Every toolkit that I've seen allows easy access to the faultcode Qname value. Cheers Simon
