Cool, I am working on something similar. You use <cferror> to catch any error (unhandled errors in this case, but you could use it for all errors) Some of this stuff was discussed not so long ago on this list, you might want to do a little search in the archives.
I basically use something like Try Catch throw myApp.odbc.database.query End catch Finally check if we can recover from any of the errors starting at the end - rethrow - if not fixed then log it End try Ooh I use error codes for logging and some other things (apparently very bad, so that's a no no no ;-) Taco Fleur Tell me and I will forget Show me and I will remember Teach me and I will learn > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Jamie Lawrence Jenner > Sent: Friday, 16 July 2004 5:11 AM > To: CFAussie Mailing List > Subject: [cfaussie] global error handling > > > hi guys, > > i am thinking of creating a global (across many sites) > (basic) error handling cfc. Basically, how i see it > happening, is any errors which occur are caught, passed to > the error cfc, inputs error info into db, and outputs an > explanation to joe public. > > basically i am looking for some guidlines on how to implement > this. What methods are currently used? > > How can i catch (apart from using try catch) an error which > happens on all requests? onrequestend.cfm maybe? or within > application.cfm? > > cheers > > jamo > > > --- > You are currently subscribed to cfaussie as: > [EMAIL PROTECTED] To unsubscribe send a blank email to > [EMAIL PROTECTED] > Aussie Macromedia Developers: http://lists.daemon.com.au/ > --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
