[
https://issues.apache.org/jira/browse/LOG4J2-1795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831783#comment-15831783
]
Alexandru Ionita commented on LOG4J2-1795:
------------------------------------------
Well, I see your point now and, indeed, the procedure is quite
counter-intuitive.
Regarding the {{ParameterizedMessage}}'s parameters, I think it is wrong to
make those transient, since they are somehow aggregated with the message and
the message will make no sense if the parameters are missing. The LogEvent is
useless at the other end in that case, since those parameters carry the
intrinsic value of the log message, don't you think?
> LogEvent serialization deserialization
> --------------------------------------
>
> Key: LOG4J2-1795
> URL: https://issues.apache.org/jira/browse/LOG4J2-1795
> Project: Log4j 2
> Issue Type: Bug
> Components: Appenders
> Affects Versions: 2.7
> Reporter: Alexandru Ionita
> Labels: serializable
>
> Deserialization of a LogEvent that has been serialized with the
> Log4jLogEvent.serialize method fails after the serialized object went through
> a byte stream.
> Here is a test that demonstrates the issue:
> https://github.com/nucatus/LogEventSerializationPOC
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
