[
https://issues.apache.org/jira/browse/LOG4NET-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12708299#action_12708299
]
Ron Grabowski commented on LOG4NET-55:
--------------------------------------
Don't you want to know when something that's suppose to be there is missing? I
suppose there are times when one doesn't... Can you give an example of when
you'd use this? I could go either way on this.
> Allow default null text,"(null)", and default not available text, "NOT
> AVAILABLE", to be configurable.
> ------------------------------------------------------------------------------------------------------
>
> Key: LOG4NET-55
> URL: https://issues.apache.org/jira/browse/LOG4NET-55
> Project: Log4net
> Issue Type: Improvement
> Reporter: Ron Grabowski
> Assignee: Ron Grabowski
> Priority: Trivial
> Fix For: 1.2.10
>
> Attachments: ConfigurableNullTextAndNotAvailableText.patch,
> ConfigurableNullTextAndNotAvailableText2.patch
>
>
> "(null)" and "NOT AVAILABLE" are not settable by the user. Allow them to be
> settable via AppSettings keys:
> <add key="log4net.NullText" value="NULL-TEXT" />
> <add key="log4net.NotAvailableText" value="NOT-AVAILABLE-TEXT" />
> or attributes on the log4net node:
> <log4net nullText="NULL-TEXT" notAvailableText="NOT-AVAILABLE-TEXT">
> ...
> </log4net>
> or in code:
> log4net.Util.SystemInfo.NullText = "NULL-TEXT";
> log4net.Util.SystemInfo.NotAvailableText = "NOT-AVAILABLE-TEXT";
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
