[
https://issues.apache.org/jira/browse/LOG4J2-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13135089#comment-13135089
]
Ralph Goers commented on LOG4J2-36:
-----------------------------------
The Appender interface is the experimental Log4j 2.0 does not contain any
reference to Filters. AppenderBase does extend Filterable so that any appenders
extending it will have filtering support. Filterable manages a single Filter
which may be a CompositeFilter that contains several filters. Layout is part of
the Appender. I'm not clear on the significance of changing the name Appender
to Channel. I'm also not clear what the refactoring suggested above really
buys.
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
