You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Isaac Devine (JIRA)" <ji...@apache.org> on 2011/08/17 09:29:27 UTC

[jira] [Updated] (LOG4NET-38) EventLogAppender: Add support for setting the Category on Event Log messages.

     [ https://issues.apache.org/jira/browse/LOG4NET-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Isaac Devine updated LOG4NET-38:
--------------------------------

    Attachment: add_category_for_EventLogAppender.patch

Patch which adds support to the EventLogAppender to include the Category, just like EventID is current able to be set.

Defaults to having a Category of 0 as that is what windows defaults to anyway.

> EventLogAppender: Add support for setting the Category on Event Log messages.
> -----------------------------------------------------------------------------
>
>                 Key: LOG4NET-38
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-38
>             Project: Log4net
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 1.2.9
>            Reporter: Nicko Cadell
>            Assignee: Ron Grabowski
>            Priority: Minor
>             Fix For: 1.2.11
>
>         Attachments: add_category_for_EventLogAppender.patch
>
>
> The EventLog supports Categories for each message. A category is a short integer.
> This could either be implemented as a fixed category value defined on the appender at config time, or as a value read from the LoggingEvent properties. The second option is more flexible as it allows the category to be specified for each message, a default category could still be specified in the appender configuration to allow for scenario 1 as well.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira