Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
From: "Carsten Ziegeler" <cziegeler@s-und-n.de>
To: <cocoon-dev@xml.apache.org>
Subject: RE: cvs commit: xml-cocoon2/src/java/org/apache/cocoon Cocoon.java
Date: Thu, 12 Sep 2002 15:06:30 +0200
Message-ID: <GMEBIBHGAOFGJCDPJANDIEECFEAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
In-Reply-To: <3D808B6D.6070502@anyware-tech.com>
Importance: Normal
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="us-ascii"


Sylvain Wallez wrote:

> 
> Actually, this is something I was considering by looking at the priority 
> filter in logkit.xconf that directs all errors regardless their category 
> to the error log file. I also considered redirecting only "core" errors 
> to that file.
> 
> Referring to the definition of priorities (see 
> http://jakarta.apache.org/avalon/logkit/whitepaper.html), we see that a 
> warning is "A problem or conflict has occurred but it may be 
> recoverable, then again it could be the start of the system failing".
> 
> So we can consider that a low-level component that fails should issue 
> warnings instead of errors since it doesn't know if the error can be 
> recovered by a higher-level component. This also shows that the logging 
> priority is a relative concept that depends on the responsibility of a 
> component in the system.
> 
> So ok for warn !
> 
> So as a summary :
> - Logging _errors_ is reserved to high-level entities such as Cocoon and 
> CocoonServlet,
> - A component that fails _can_ log a _warning_ before throwing an 
> exception,
> - An exception that is catched and propagated _must not_ be logged, even 
> if wrapped in a CascadingException.
> 
> Do we agree on this ?
> 

Absolutely! - So, I can keep on removing things... :-)

Regards
Carsten


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