Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Date: Tue, 6 Sep 2011 15:50:10 +0000 (UTC)
From: "Stefan Bodewig (JIRA)" <jira@apache.org>
To: log4net-dev@logging.apache.org
Message-ID: 
 <382355516.20886.1315324210139.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (LOG4NET-7) Detecting NoAppenderWarning
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/LOG4NET-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig updated LOG4NET-7:
---------------------------------

    Fix Version/s:     (was: 1.2.11)
                   1.2 Maintenance Release

> Detecting NoAppenderWarning
> ---------------------------
>
>                 Key: LOG4NET-7
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-7
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Core
>         Environment: From sourceforge - 785036
>            Reporter: Nicko Cadell
>            Assignee: Ron Grabowski
>             Fix For: 1.2 Maintenance Release
>
>
> It would be nice to be able to detect an event related
> to NoAppenderWarning. That is, one might want to take
> arbitrary actions when a logger category has no
> appenders attached to it, which is often caused by
> some kind of problem, usually related to configuration.
> Thanks for considering this suggestion. 
> Anonymous 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira