Nicola Ken Barozzi wrote: > > Carsten Ziegeler wrote: > >>-----Original Message----- > >>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > >>Sent: Thursday, September 05, 2002 11:30 AM > >>To: [EMAIL PROTECTED] > >>Subject: 3 suggestions > >> > >> > >>3) src-path in the exceptions from the parsers > >> > >>As it stands, it is difficult to determine which of the sources > >>in a pipe that the parser compains about. Isn\'t it possible to > >>wrap the exceptions so that info on what part of the process that > >>did fail? > >> > > > > Actually the exceptions are wrapped but unfortunately there is no > > evaluation of all possible wrapping exceptions at the top level. > > > > The logging of exceptions is an issue which comes up from time > > to time but has never been really solved. Currently, one single > > exception is logged more than once because it is logged when > > it is thrown, it is logged when it is rethrown and it is logged > > when it is catched. > > I made several month ago the suggestion to log exceptions only > > when they are catched - but not when they are thrown or rethrown. > > They can be logged when they are thrown/rethrown when the component > > is in debug mode. > > This would make the logs much more cleaner and if then the evaluating > > code you suggest above is added at the top level, that would be cool. > > But unfortunately there was no agreement about this... > > Hmmm... the exceptions should cascade, so actually how-when it's > rethrown should not be an issue to understand where the problem comes > from, no? > Yes.
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. Carsten --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
