[
https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker updated LOG4J2-1300:
--------------------------------
Description: Appenders and Filters are already supposed to be Serializable
based on the abstract classes. This is not feasible based on the use of many
non-serializable JDK classes (e.g., OutputStream, Buffer). As LogEvent, Logger,
and MessageFactory (implementations) all implement Serializable without
requiring everything else, then there's no need to serialize appenders,
filters, and all the other plugin objects that are never serialized anywhere.
(was: Appenders and Filters are already supposed to be Serializable based on
the abstract classes. Following this to its logical conclusion, pretty much
every plugin has to be serializable. Most of these already are or could be
supported through their abstract classes. Some of these classes are using
non-serializable classes which need to also implement Serializable or provide a
serialization proxy.)
> Remove serializability from classes that don't need it
> ------------------------------------------------------
>
> Key: LOG4J2-1300
> URL: https://issues.apache.org/jira/browse/LOG4J2-1300
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders, Core, Filters, Layouts, Lookups, Pattern
> Converters, Plugins
> Affects Versions: 2.5
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Fix For: 2.6
>
>
> Appenders and Filters are already supposed to be Serializable based on the
> abstract classes. This is not feasible based on the use of many
> non-serializable JDK classes (e.g., OutputStream, Buffer). As LogEvent,
> Logger, and MessageFactory (implementations) all implement Serializable
> without requiring everything else, then there's no need to serialize
> appenders, filters, and all the other plugin objects that are never
> serialized anywhere.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
