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 "Matt Sicker (JIRA)" <ji...@apache.org> on 2016/03/01 01:15:18 UTC
[jira] [Updated] (LOG4J2-1300) Remove serializability from classes
that don't need it
[ https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Sicker updated LOG4J2-1300:
--------------------------------
Summary: Remove serializability from classes that don't need it (was: Make plugins consistently implement Serializable)
> 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. 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org