For the exception, I assume that the expected behavior in .NET is something like this:
1. Import fault type 2. Derive fault type from SoapException 3. Allow catch to be as specific as the "fault" or as generic as Exception. As for the throws declaration, didn't C++ beat Java to the idea? ;) 'course, the implementation is a wee bit different. As for why C# doesn't have the throws declaration, I think I remember seeing a discussion on why on the dotnet list hosted at discuss.develop.com. Anyhow I think I've ranged far enough off topic now. Sorry for the diversion. -----Original Message----- From: Oliver Suciu [mailto:[EMAIL PROTECTED]] Sent: Friday, April 19, 2002 1:30 PM To: [EMAIL PROTECTED] Subject: Re: .Net ignores <wsdl:fault>? Yes, but wsdl.exe doesn't generate the exception classes, so I can't catch an exception more specific than SoapException. It actually doesn't matter cuz I don't even get exceptions propagated properly to an Axis client -- looks like the current state of the art is not ready yet for <fault>... -- Oliver PS: Just found out that C# has no equivalent to the Java "throws" declaration -- interesting... Scott Seely wrote: > > At this point in time, what .NET will do is receive the data and make it > visible to the client code as XML through the details element (IIRC). > > -----Original Message----- > From: Oliver Suciu [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 19, 2002 10:49 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: .Net ignores <wsdl:fault>? > > Hi all, > > (Sorry, this one is somewhat geared towards .Net...) > > I've got an Axis service that throws an exception, and WSDL2Java > correctly generates a <wsdl:fault> for the <wsdl:operation>. > > However, the .Net wsdl.exe seems to completely ignore the <fault>, > and no corresponding client-side code is generated. > > Has anybdoy got this working? > Anybdoy looked into .Net interop with respect to <fault>? > > Thanks, > > -- Oliver
