logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Grabowski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-342) Add a way to prevent silent failure
Date Mon, 10 Jun 2013 22:24:20 GMT

    [ https://issues.apache.org/jira/browse/LOG4NET-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13679984#comment-13679984
] 

Ron Grabowski commented on LOG4NET-342:
---------------------------------------

The IsEnabled's come in handy when you want check at a higher level if particular logger/level
pair is enabled. Sometimes code takes a very different logic path when trace is enabled. That
determination is made separately from the actual tracing.

Do you expect log.IsConfigured to be called a lot outside of an application's startup code?
I have a feeling most applications will call it just once. I'd hate to clutter up the main
interface with a member that gets called infrequently and will always have the same value
across all ILogs. LogManager.GetRepository().Configured still seems good enough. As far as
discoverability goes, I fired up VS and found the property by navigating through a few small
intellisense lists:

 log.Logger.Repository.Configured

Let's assume log.IsConfigured==false, now where do I go? At some point they're going to have
to deal with the repository to figure out what the problem is. I say we keep them close to
the repository since that's what they're ultimately configuring and that's what they'll need
to inspect before using ILog instances.
                
> Add a way to prevent silent failure
> -----------------------------------
>
>                 Key: LOG4NET-342
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-342
>             Project: Log4net
>          Issue Type: New Feature
>            Reporter: Joachim Zobel
>            Assignee: Dominik Psenner
>            Priority: Minor
>             Fix For: 1.2.12
>
>
> I spent most of the day trying to find out why logging is not working on my dev system
but not on test. There should be a way to force error reporting by throwing (possibly unhandled)
exceptions. This could be done by adding a required flag to the appenders and another flag
that requires a least one working appender.
> I am not sure about a good way to implement this, I would just love it if my favourite
tool to end silent failure could stop failing silently. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message