logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Francois Beaulac (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4NET-553) DebugAppender configuration should give the possibility to disable outputting loggerName as category
Date Wed, 08 Feb 2017 12:50:42 GMT

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

Jean-Francois Beaulac commented on LOG4NET-553:
-----------------------------------------------

I think your idea is much better than mine. It is more flexible while allowing my usecase
and still preserving the current behavior.

> DebugAppender configuration should give the possibility to disable outputting loggerName
as category
> ----------------------------------------------------------------------------------------------------
>
>                 Key: LOG4NET-553
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-553
>             Project: Log4net
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 2.0.7
>            Reporter: Jean-Francois Beaulac
>         Attachments: OutputCategoryParam-DebugAppender.cs.patch
>
>
> The DebugAppender always uses the {{System.Diagnostics.Debug.Write(string,string)}} overload
passing in the loggername as the category parameter.
> It should be possible to omit the category parameter if having the loggername as category
is not desired.
> Attached is a patch implementing the desired new feature, which would be activated by
configuration:
> {code:xml}
> <appender name="DEBUG" type="log4net.Appender.DebugAppender">
>     <outputCategory value="false"/>
>     <layout type="log4net.Layout.PatternLayout">
> 	  <conversionPattern value="%-5level: %message%newline"/>
>     </layout>
>   </appender>
> {code}
> In my patch, the outputCategory parameter defaults to true, so the behavior doesnt change
unless the new configuration is used.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message