From log4j-dev-return-11148-apmail-logging-log4j-dev-archive=logging.apache.org@logging.apache.org Thu Sep 15 17:53:17 2005 Return-Path: Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org Received: (qmail 24426 invoked from network); 15 Sep 2005 17:53:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Sep 2005 17:53:17 -0000 Received: (qmail 98374 invoked by uid 500); 15 Sep 2005 17:53:16 -0000 Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org Received: (qmail 98350 invoked by uid 500); 15 Sep 2005 17:53:15 -0000 Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Log4J Developers List" Reply-To: "Log4J Developers List" Delivered-To: mailing list log4j-dev@logging.apache.org Received: (qmail 98336 invoked by uid 99); 15 Sep 2005 17:53:15 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Sep 2005 10:53:14 -0700 Received: by ajax.apache.org (Postfix, from userid 99) id 2956913F; Thu, 15 Sep 2005 19:53:12 +0200 (CEST) From: bugzilla@apache.org To: log4j-dev@logging.apache.org Subject: DO NOT REPLY [Bug 36675] New: - Difficult to identify problems in JoranConfigurator X-Bugzilla-Reason: AssignedTo Message-Id: <20050915175312.2956913F@ajax.apache.org> Date: Thu, 15 Sep 2005 19:53:12 +0200 (CEST) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=36675 Summary: Difficult to identify problems in JoranConfigurator Product: Log4j Version: 1.3alpha Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: Configurator AssignedTo: log4j-dev@logging.apache.org ReportedBy: carnold@apache.org The existing configurators swallow exceptions that occur in processing the XML or properties file. While the silent approach is appropriate for default configuration. If an application is making explicit calls to the configurator, there should be some manner for it to make a call where exceptions will be propagated to the caller. See http://marc.theaimsgroup.com/?l=log4j-dev&m=110202005517575&w=2 ("Joran not reporting config errors", 12/04 on log4j-dev) and http://marc.theaimsgroup.com/?l=log4j-user&m=112674335019978&w=2 ("DOMConfigurator configure methods do not report failure", 9/05 on log4j-user). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org For additional commands, e-mail: log4j-dev-help@logging.apache.org