[Seaside] Handling errors - staging/production
Boris Popov, DeepCove Labs
boris at deepcovelabs.com
Mon May 30 17:46:04 UTC 2011
We implement our own subclass of WAHtmlErrorHandler which logs the exception and sends email notification before presenting an error page to the browser,
| app |
app := WAAdmin register: self asApplicationAt: 'online'.
app filter configuration at: #exceptionHandler put: WebErrorHandler.
WebErrorHandler>>handleDefault: ex
Manager
notifyUnhandledException: ex
in: self
fatal: false.
super handleDefault: ex.
Hope this helps,
-Boris
-----Original Message-----
From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-bounces at lists.squeakfoundation.org] On Behalf Of Francois Stephany
Sent: 30 May 2011 13:42
To: seaside at lists.squeakfoundation.org
Subject: [Seaside] Handling errors - staging/production
What is the preferred way to handle errors on a production seaside application? Is there some kind of http://www.hoptoadapp.com/ to handle applications crashes/walkback?
How do you typically do to handle errors?
Cheers,
Francois
_______________________________________________
seaside mailing list
seaside at lists.squeakfoundation.org
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
More information about the seaside
mailing list