logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-1347) AsyncAppender - Allow serialization of custom LogEvents
Date Fri, 01 Apr 2016 15:53:25 GMT

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

Ralph Goers commented on LOG4J2-1347:
-------------------------------------

I suspect that it is because the thread needs a copy of the event with message formatting
done, not the event itself.

> AsyncAppender - Allow serialization of custom LogEvents
> -------------------------------------------------------
>
>                 Key: LOG4J2-1347
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1347
>             Project: Log4j 2
>          Issue Type: Improvement
>            Reporter: John Strickler
>            Priority: Minor
>
> This request is for an improvement to AsyncAppender to allow sublasses of Log4jLogEvent
to be serialized without losing their specific type.
> Currently functionality, is that AsyncAppender will serialize all subclasses back to
a true instance of Log4jLogEvent.  In the process, all extra information is lost that was
provided by the subclass.
> _AsyncAppender, line 156:_
> bq. final Serializable serialized = Log4jLogEvent.serialize(coreEvent, includeLocation);
> *Use Case*
> Subclasses of Log4jLogEvent that contain the authenticated principal to be logged.



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


Mime
View raw message