[jira] [Comment Edited] (LOG4J2-1300) Make plugins consistently implement Serializable

["Ralph Goers (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171528#comment-15171528 ] 

Ralph Goers edited comment on LOG4J2-1300 at 2/29/16 7:30 AM:
--------------------------------------------------------------

Why do you care? What is the use case for serializing these objects?


was (Author: ralph.goers@dslextreme.com):
Why do you care? Hat is the use case for serializing these objects?

> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org