[
https://issues.apache.org/jira/browse/LOG4J2-2252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377946#comment-16377946
]
ASF subversion and git services commented on LOG4J2-2252:
---------------------------------------------------------
Commit e4d9b0d65218291b0eaf60e980fe368892ab5aca in logging-log4j2's branch
refs/heads/release-2.x from rpopma
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=e4d9b0d ]
LOG4J2-2252 (change log) Reusable LogEvents now pass the original format string
to downstream components like layouts and filters.
Closes #154
> Reusable events drop the original format string
> -----------------------------------------------
>
> Key: LOG4J2-2252
> URL: https://issues.apache.org/jira/browse/LOG4J2-2252
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Carter Douglas Kozak
> Assignee: Remko Popma
> Priority: Major
>
> MutableLogEvent and RingBufferLogEvent hold references to state from original
> messages, but they currently exclude the value of Message.getFormat().
> I would like to write a custom Layout implementation which is aware of the
> format string and parameters, which doesn't necessarily use the formatted
> message value.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
