Throwing custom exceptions in web services using VS.Net

[Gian U. Uy]

I created a custom exception for my web service using VS.Net and it's
ASP.Net web service tools. Its base class derived from System.Exception and
I have a WinForm client that references the web service. But when I
referenced my Web Service, it did not pick up our custom exception class so
that the application could catch the exception in its actual class not by
the System.Exception class.

Is this possible?

 

[Dave Beauchemin [MVP]]

The way the .NET Framework currently works with web services (by default) is
to wrap web service exceptions in a SOAP exception. This is for standards
compliance, because the SOAP recommendation requires that exceptions or
errors be wrapped appropriately. If your web service were to communicate
with other applications (think interoperability), this would be the desired
effect.

Unfortunately, when working in a Microsoft-only environment, this can be
somewhat annoying. I've found that the best work-around to this is to create
a custom class which extracts the actual error and throws the base exception
in the callee application (which in your case would be the custom
exception).

Ultimately, the best place for custom exceptions is in your WinForms
application, not in the web service, IMHO.
--


Dave Beauchemin
Microsoft MVP, MCP
www.webdotmag.com

 

[Jan Tielens]

Hi

Some time ago, I created a solution for this problem. It is possible to put
extra information in the Detail node in the SOAP enveloppe. You can find
more info here:
http://www.microsoft.com/belux/nl/msdn/community/columns/jtielens/soapexcept
ions.mspx

Jan

 

[Gian U. Uy]

Thanks guys!!!

Hi

Some time ago, I created a solution for this problem. It is possible to put
extra information in the Detail node in the SOAP enveloppe. You can find
more info here:
http://www.microsoft.com/belux/nl/msdn/community/columns/jtielens/soapexcept
ions.mspx

Jan

default)