Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 83209 invoked by uid 500); 5 Sep 2002 12:59:54 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 83197 invoked from network); 5 Sep 2002 12:59:53 -0000 Message-ID: <3D775506.8060205@apache.org> Date: Thu, 05 Sep 2002 14:58:46 +0200 From: Nicola Ken Barozzi Reply-To: nicolaken@apache.org Organization: Apache Software Foundation User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: cocoon-dev@xml.apache.org Subject: Re: 3 suggestions References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Carsten Ziegeler wrote: >>-----Original Message----- >>From: ola.berg@arkitema.se [mailto:ola.berg@arkitema.se] >>Sent: Thursday, September 05, 2002 11:30 AM >>To: cocoon-dev@xml.apache.org >>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? -- Nicola Ken Barozzi nicolaken@apache.org - verba volant, scripta manent - (discussions get forgotten, just code remains) --------------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org For additional commands, email: cocoon-dev-help@xml.apache.org