logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (LOG4J2-1347) AsyncAppender - Allow serialization of custom LogEvents
Date Sun, 03 Apr 2016 04:35:25 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-1347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Remko Popma resolved LOG4J2-1347.
---------------------------------
    Resolution: Not A Problem

John, thanks for the reply. I'm resolving this ticket as "not a problem" for now, please close
it if that is okay, but also feel free to re-open if I misunderstood.

Feedback, patches or change requests are always welcome!

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


Mime
View raw message