.NET treats soap faults as a SoapException. From the SoapException is an optional Detail element that you can use to parse the actual fault returned by the server. Even if the WSDL for the java webservice indicated the faults involved in their operation, .NET generators (WSDL.exe/VS.NET add web reference) don't even look at the soap:Fault elements and you have to do the processing manually.
Conversely, on a .NET webservice if you are implementing a specific WSDL that defines various soap:Faults, you need to manually construct the SoapException and set its Detail element. Adam.. > -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Ravi Veerla > Sent: Thursday, July 14, 2005 6:47 PM > To: [email protected] > Subject: Re: [ADVANCED-DOTNET] problem with soap faults from > a java/axis webservice > > could anybody find a solution to my problem. Where do i get > information on how .net framework would treat soap faults. i > read some where that .net framework would raise an exception > when it gets a soap fault as a response. > is it necessary that the exception class(that is in java) be > on the client side(.net). i did not find a definition for the > java exception classes in the wsdl to generate the client > side stubbed code. > > any information/advice will be greatly appreciated. =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
