There is no one spot to put a catch that will get everything.
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Hob Spillane Sent: Wednesday, October 31, 2007 9:36 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Handling uncaught errors Has anyone found any creative solutions to this? I'm trying to create a logger that traps all exceptions that aren't caught anywhere else in the application and logs them back to the server for analysis. I'd very much like to accomplish this without having to add hundreds of try-catch blocks scattered about our code. -Hob --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "sonicmarkf" <[EMAIL PROTECTED]> wrote: > > Hello, > > I am looking for the best approach to trap, at the application level, > any system/application uncaught errors. > > We have a fairly robust error/exception handling implementation to > communicate to our user's errors that might arise in the > communication and processing of application's data etc.... > > However, we would also like to provide in our application user > feedback on any potential uncaught errors. Nothing fancy but just > enough to let them know a problem has occurred and also - most > importantly - to allow us the ability to log the error so we can > address it. > > Has anyone tackled this problem? I searched the list and could not > find any threads on the subject. > > Thanks for any ideas. > > Mark >
