Re: Handling Exception in Web Services when using HttpGet protocol.
From: Sherif ElMetainy (elmeteny_at_thewayout.net)
Date: 05/25/04
- Next message: Simon: "When to update the database when moving through a series of forms"
- Previous message: Simon: "Ensuring a listbox has at least one value in it"
- In reply to: Sherif ElMetainy: "Handling Exception in Web Services when using HttpGet protocol."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 25 May 2004 22:19:45 +0300
I posted in the wrong newsgroup, sorry for the inconvenience. Still any help
would be appreciated. Thanks.
"Sherif ElMetainy" <elmeteny@thewayout.net> wrote in message
news:elFQEwoQEHA.1048@tk2msftngp13.phx.gbl...
> Hello
>
> I have an application with several web services. I want to be able to log
> all exception are thrown by any web method. Since the web services handler
> catches and swallows all exceptions, and send them to the client in a soap
> message, Global.asax's Application_Error method can't be used. So I made a
> SoapExtension class that override ProcessMessage method. That solution
> worked for HttpSoap protocol.
> The problem is that my application web.config also enables the HttpGet
> protoco because some clients needs it. When a client calls my web services
> using HttpGet, the soap extensions are not invoked, and also Context.Error
> is null. I can only know that an error occured in Application_EndRequest
> method by checking that Response.StatusCode is 500. But I don't know how
do
> I get information about the exception itself.
>
> Any help would be appreciated, thanks in advance.
>
> Best regards,
> Sherif
>
>
- Next message: Simon: "When to update the database when moving through a series of forms"
- Previous message: Simon: "Ensuring a listbox has at least one value in it"
- In reply to: Sherif ElMetainy: "Handling Exception in Web Services when using HttpGet protocol."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
