[LOG4J2-1593] Concrete Filter implementations should override equals and hashCode

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Filters
• Assignee: Unassigned
• Reporter: Remko Popma
• Created: 18/Sep/16 08:52
• Updated: 02/Apr/17 20:09

Description

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.

Issue Links

• is depended upon by: LOG4J2-1594 Add support for adding and removing Filters via JMX