Carsten, all, >-----Original Message----- >From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] >Sent: Wednesday, December 19, 2001 4:30 PM >To: Cocoon-Dev >Subject: [RT]: When to log exceptions > > >Hi, > >I would like to know, if we should define a policy for logging exceptions. >Currently, sometimes exceptions are logged when they are raised, sometimes >when they are catched and sometimes they aren't logged at all.
Funny I had the same idea today. I wanted to write an RT today or tomorrow ;). >This leads to the problem, that you get the same exception more than once >in the log or you never see it (ok, the first alternative is of course the >better one );). > >Now, if we stick to a simple rule, we could easily have all exceptions in >the log and these only once which would make reading the log files a little >bit easier. So, there are two alternatives: >a) always log an exception when it's raised but not when it's catched >b) always log an exception when it's catched but not when it's raised > >I'm +1 on b). +1 for b) Always with the complete StackTrace?? Gerhard >Opinions? > -------------------------- Hey! It compiles! Ship it! -------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
