G
Guest
Hello NG!
Within the global.asax of my WebService I can catch unahandled exceptions:
Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs)
In my opinion an exception always is caused by a client-request. So is it
possible within that method to force excectly that request (which is maybe
one of some at the same time) to throw a (SOAP)-Exception (which can be
catched at the client) ?
My problem until now is, that ASP.NET tries to send an HTML-formatted error
description to the client, but there it can't be handled, because the
WebMethod call expects XML (SOAP) not HTML. So I see no chance to get the
"reel" exception on the client and present it to the user.
Thanks, D.Barisch
Within the global.asax of my WebService I can catch unahandled exceptions:
Sub Application_Error(ByVal sender As Object, ByVal e As EventArgs)
In my opinion an exception always is caused by a client-request. So is it
possible within that method to force excectly that request (which is maybe
one of some at the same time) to throw a (SOAP)-Exception (which can be
catched at the client) ?
My problem until now is, that ASP.NET tries to send an HTML-formatted error
description to the client, but there it can't be handled, because the
WebMethod call expects XML (SOAP) not HTML. So I see no chance to get the
"reel" exception on the client and present it to the user.
Thanks, D.Barisch