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: 3 suggestions
Date: Thu, 5 Sep 2002 15:24:26 +0200
Message-ID: <GMEBIBHGAOFGJCDPJANDMEHMFDAA.cziegeler@s-und-n.de>
MIME-Version: 1.0
Importance: Normal
In-reply-to: <3D7758D4.4060706@apache.org>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset="US-ASCII"

Nicola Ken Barozzi wrote:


> >
> > But there was no consensus on if we should log when the
> exception is thrown
> > or when it is catched and consumed (and not rethrown). I prever the last
> > way and someone else prefered the first solution. So, it's still as it
> > is and you get an exception logged more than once - blowing up the log.
>
> It should be logged when it is consumed, because you can never tell if
> you catch a new exception or an already rethrown one.
>
> BTW, do we really need to log exceptions in the components?
>
> I would really like to see the errors caught ONLY by Cocoon.java, and
> logged there. It would reduce the problems we are having a LOT.
>
That's what I suggested years ago...

Carsten


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