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 "Remko Popma (JIRA)" <ji...@apache.org> on 2017/01/25 10:46:27 UTC
[jira] [Updated] (LOG4J2-1593) Concrete Filter implementations
should override equals and hashCode
[ https://issues.apache.org/jira/browse/LOG4J2-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma updated LOG4J2-1593:
--------------------------------
Fix Version/s: (was: 2.8)
2.8.1
> Concrete Filter implementations should override equals and hashCode
> -------------------------------------------------------------------
>
> Key: LOG4J2-1593
> URL: https://issues.apache.org/jira/browse/LOG4J2-1593
> Project: Log4j 2
> Issue Type: Improvement
> Components: Filters
> Reporter: Remko Popma
> Fix For: 2.8.1
>
>
> For {{CompositeFilter.remove(Filter)}} to work correctly, concrete Filter implementations should override {{equals}} and {{hashCode}}.
> This is because CompositeFilter uses List.remove(Object), comparing by equality. Applications that keep a reference to the Filter object that was registered will work, but for example registering and unregistering serialized and deserialized instances via JMX will not work without this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org