S
Sergei Shelukhin
Hi.
We have a web service that gets called using http (e.g. no SOAP calls,
SoapExtensions do not work) and we need to get information about
errors occuring in Web service methods. Web sefvice methods
themselves are nothing but a single line calls to BO methods; we want
to enable (or rather, re-enable from pre-WS times) logging and mailing
of the errors in Bo classes for WS calls.
ASP.NET however eats the exceptions propagating them to the client.
Is there any way to handle the errors apart from putting try...catch
in every method?
We have a web service that gets called using http (e.g. no SOAP calls,
SoapExtensions do not work) and we need to get information about
errors occuring in Web service methods. Web sefvice methods
themselves are nothing but a single line calls to BO methods; we want
to enable (or rather, re-enable from pre-WS times) logging and mailing
of the errors in Bo classes for WS calls.
ASP.NET however eats the exceptions propagating them to the client.
Is there any way to handle the errors apart from putting try...catch
in every method?