[
https://issues.apache.org/jira/browse/LOG4J2-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15260501#comment-15260501
]
Mikael Ståldal commented on LOG4J2-1347:
----------------------------------------
I have started some work to get rid of the (IMHO) misuse of serialization of
{{LogEvent}}. I think we should use the memento pattern more consistently
instead.
Check branch LOG4J2-1347. It still uses serialization, but now it is
encapsulated. Next step is to implement the new {{createMemento()}} methods
more efficiently.
> 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.
> The current 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: [email protected]
For additional commands, e-mail: [email protected]
