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

Posted to log4j-dev@logging.apache.org by "Ralph Goers (JIRA)" <ji...@apache.org> on 2012/10/02 22:01:08 UTC

[jira] [Closed] (LOG4J2-36) Appender interface should be refactored

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

Ralph Goers closed LOG4J2-36.
-----------------------------

    
> Appender interface should be refactored
> ---------------------------------------
>
>                 Key: LOG4J2-36
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-36
>             Project: Log4j 2
>          Issue Type: Wish
>          Components: Appenders
>            Reporter: Curt Arnold
>
> The Appender interface in log4j 1.2 (carried over in the rgoers contribution) requires an implementation to not only define its distinctive logging destination also but also a composite filter (the addFilter(), getFilter(), getFilters() method).  Because of that almost all custom appenders in log4j 1.2 extend from AppenderSkeleton to inherit the implementation of composite filter.  The appender interface should be refactored so it contains a reference to a generic Filter (which may or may not be a composite filter) and a Channel (or whatever we want to call the bit that makes one appender different from another).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org