Hi Carsten,

On Wed, Dec 19, 2001 at 04:29:50PM +0100, Carsten Ziegeler wrote:

> 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).
> 
> Opinions?

	I agree with you mate, b). Also, in several places exceptions are
	caught, logged and then rethrown (and potentially re-logged
	elsewhere), which b) could cover too if we wanted (eg. only log
	at the most highest handler).

	Cheers,

	Marcus

-- 
        .....
     ,,$$$$$$$$$,      Marcus Crafter
    ;$'      '$$$$:    Computer Systems Engineer
    $:         $$$$:   ManageSoft GmbH
     $       o_)$$$:   82-84 Mainzer Landstrasse
     ;$,    _/\ &&:'   60327 Frankfurt Germany
       '     /( &&&
           \_&&&&'     Email : Marcus.Crafter@managesoft.com
          &&&&.        Business Hours : +49 69 9757 200
    &&&&&&&:

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org