[
https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171943#comment-15171943
]
Matt Sicker commented on LOG4J2-1300:
-------------------------------------
I was thinking about this since last night, and I'd actually prefer to remove
Serializable from most of the classes (including ones that were previously
released as Serializable). Logger is serializable using a proxy that doesn't
require anything besides a string and a MessageFactory. Really, the only things
that need to be serializable are LogEvent, Logger, and MessageFactory (that's
the only three I remember, could be more, but those are the base).
The reason why I started doing this was because every Appender or Filter that
uses the abstract class is already claiming to be Serializable, so I was trying
to normalize that.
> Make plugins consistently implement Serializable
> ------------------------------------------------
>
> 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. 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
