logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1300) Remove serializability from classes that don't need it
Date Tue, 01 Mar 2016 00:23:18 GMT

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

Gary Gregory commented on LOG4J2-1300:

Fine with me.

> 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,
>    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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message