You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2008/05/20 00:22:54 UTC

DO NOT REPLY [Bug 45042] New: Need a reliable way to detect misconfiguration

https://issues.apache.org/bugzilla/show_bug.cgi?id=45042

           Summary: Need a reliable way to detect misconfiguration
           Product: Log4j
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configurator
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: sdeboy@iname.com


For folks who kick off log4j configuration programmatically (or via
DOMConfigurator.configureAndWatch), it would be helpful for application code to
be able to detect that configuration was not successful (unable to parse,
configuration file missing).

Maybe a configurator.addConfigurationErrorHandler method which calls back when
a misconfiguration occurs?


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org