Allow to inherit appenders in config file
-----------------------------------------

                 Key: LOG4NET-139
                 URL: https://issues.apache.org/jira/browse/LOG4NET-139
             Project: Log4net
          Issue Type: New Feature
          Components: Appenders
            Reporter: Steve Wagner
            Priority: Minor


In my log4net configuration file i use several rolling file appenders like this:

        <appender name="RootLogFileAppender" 
type="log4net.Appender.RollingFileAppender">
                <file value="logs\rolling-log.txt" />
                <maxSizeRollBackups value="10" />
                <maximumFileSize value="5MB" />
                <rollingStyle value="Size" />
                <staticLogFileName value="true" />
                <layout type="log4net.Layout.PatternLayout">
                        <conversionPattern value="%date [%thread] %-5level 
%logger [%ndc] - %message%newline" />
                </layout>
                <filter type="log4net.Filter.LoggerMatchFilter">
                        <LoggerToMatch value="Foo" />
                        <AcceptOnMatch value="False" />
                </filter>
                <filter type="log4net.Filter.LoggerMatchFilter">
                        <LoggerToMatch value="Bar" />
                        <AcceptOnMatch value="False" />
                </filter>
        </appender>

But for each log file i have to define the full RollingFileAppender again and 
again and again. So it would be good if i defined the base appender once, 
inherit all other from it and set only the new filename. This could look like 
this:

        <appender name="FooFileAppender" BasedOn="RootLogFileAppender">
                <file value="logs\foo-log.txt" />
        </appender>
        
        <appender name="BarFileAppender" BasedOn="RootLogFileAppender">
                <file value="logs\bar-log.txt" />
        </appender>

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