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

David Boden commented on LOG4NET-55:
------------------------------------

Note that 1.2.10 doesn't support using a blank string for the null value.

This doesn't work:

  <appSettings>
    <add key="log4net.NullText" value=""/>
    <add key="log4net.NotAvailableText" value=""/>
  </appSettings>

Adding a space for the value instead of a blank string makes things work:
  <appSettings>
    <add key="log4net.NullText" value=" "/> <!-- Empty string not supported -->
    <add key="log4net.NotAvailableText" value=" "/> <!-- Empty string not 
supported -->
  </appSettings>

> 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.

Reply via email to