[
https://issues.apache.org/jira/browse/LOG4J2-2107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248678#comment-16248678
]
ASF subversion and git services commented on LOG4J2-2107:
---------------------------------------------------------
Commit 93a7235da78c562026993cdc4e3e5775c47e8099 in logging-log4j2's branch
refs/heads/master from [~ckozak]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=93a7235 ]
LOG4J2-2107: MapMessage allocation-free pattern conversion
Fixes an issue causing MessagePatternConverter to greedily format
MapMessage instances as StringBuilderFormattable ignoring format.
> MapMessage should support both StringBuilderFormattable and MultiformatMessage
> ------------------------------------------------------------------------------
>
> Key: LOG4J2-2107
> URL: https://issues.apache.org/jira/browse/LOG4J2-2107
> Project: Log4j 2
> Issue Type: Bug
> Components: Layouts
> Affects Versions: 2.9.1
> Reporter: Carter Douglas Kozak
> Assignee: Mikael Ståldal
> Fix For: 2.10.0
>
>
> Currently MessagePatternConverter will not respect the format, writing the
> MapMessage directly to a shared StringBuilder using the default encoding.
> We need to implement a "MultiFormatStringBuilderFormattable" type with "void
> formatTo(String[] formats, StringBuilder buffer);"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
