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.
+1
Carsten Ziegeler wrote:
> 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...
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
