[
https://issues.apache.org/jira/browse/LOG4NET-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285444#comment-13285444
]
Dominik Psenner commented on LOG4NET-342:
-----------------------------------------
Oh, I just noticed that there is a "Configured" property in Hierarchy that
could be wrapped in Logger like this:
/// <summary>
/// Gets the flag that indicates if the repository of this
Logger has been configured.
/// </summary>
/// <value>
/// <c>true</c> if the repository of this Logger has been
configured.
/// </value>
/// <remarks>
/// <para>
/// Gets the flag that indicates if this repository has been
configured.
/// </para>
/// </remarks>
public bool Configured
{
get { return Hierarchy.Configured; }
}
> 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
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
