Two valid requirements have been mentioned and need to be reconciled:
1. The need to avoid flooding the console log with debug-related messages. 2. The need to avoid losing potentially critical debugging information when an exception occurs (especially if the exception is not wrapped and re-thrown). One way to reconcile them is to send debug information (stack trace etc.) to a separate log (which could reside by default in a file) so that just the occurrence of a failure need be indicated on the console log. Glyn
