Uncaught exception logged as DEBUG

[Christian Kesselheim <ck...@infeurope.lu>]

Hi!

I wonder why the AbstractEngine by defaults logs all uncaught 
exceptions (via commons logging) with the log level set to DEBUG!? 
Increasing the threshold for the whole class results in a log file 
cluttered with all different kind of tracing statements when having 
only the actual stack-trace for the exception would suffice.

What is the recommended approach for giving those exceptions a more 
prominent place in the servers logfile? Implement your own 
ExceptionAnalyzer? Increase the log level for 
org.apache.tapestry.engine.AbstractEngine to DEBUG? Or simply catching 
all exceptions in an appropriate base page class and log them yourself?

Thnx in advance.

Chris

-------------------------
infeurope S.A.
62, rue Charles Martel
L-2134 Luxembourg
Luxembourg
Tel: (+352) 25.22.33.1
Fax: (+352) 25.22.33.222

Web: www.infeurope.lu
-------------------------

Any views expressed are purely those of the writer and may not in any
circumstances be regarded as stating an official position of infeurope 
S.A.! 
  


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-user-help@jakarta.apache.org