cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <>
Subject RE: cvs commit: xml-cocoon2/src/java/org/apache/cocoon
Date Thu, 12 Sep 2002 05:41:26 GMT

Sylvain Wallez wrote:
> >
> > In the above case, it is starting to throw something, so it's ok, and 
> > even good, that something is logged.
> > It's not the exception being logged, but the event that will cause the 
> > exception to be thrown. 
> That's exactly what I mean.
> Carsten, what do you think ?
Sorry, but I don't agree here. There is a reason for the thrown exception
and the common handling of this is to put this reason into the message
of the exception.
When this exception is logged you see the reason/message/event that
caused the exception.
If you do log the event apart from the exception, then you will again
get two entries: one with the sole event and one with the exception
which is then the same text. And that's disturbing.

We tought many new cocooners over the last months and they always very
absolutely confused and actually got lost by the mass of messages
appearing in the log when one single exception is thrown, because
that single event is/was logged several times. So I still think,
logging once is enough.
This works of course only if the exception is logged somewhere -
this musg be guaranteed.


To unsubscribe, e-mail:
For additional commands, email:

View raw message