[
https://issues.apache.org/jira/browse/LOG4J2-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037584#comment-17037584
]
ASF subversion and git services commented on LOG4J2-2703:
---------------------------------------------------------
Commit 65565d1043033a15c57efd5bab27e0f88e595e8e in logging-log4j2's branch
refs/heads/release-2.x from Volkan Yazıcı
[ https://gitbox.apache.org/repos/asf?p=logging-log4j2.git;h=65565d1 ]
LOG4J2-2703 Complex data type support for the default MapMessage JSON
formatter. (#339)
> MapMessage#getFormattedMessage() incorrectly formats Object's
> -------------------------------------------------------------
>
> Key: LOG4J2-2703
> URL: https://issues.apache.org/jira/browse/LOG4J2-2703
> Project: Log4j 2
> Issue Type: Bug
> Reporter: Volkan Yazici
> Priority: Minor
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The following code snippet
> {color:#0747a6}{{new MapMessage()}}
> {{ .with("key1", "val1")}}
> {{ .with("key2", Collections.singletonMap("val2.1", "val2.2"))}}
> {{ .getFormattedMessage(new String[]\{"JSON"});}}{color}
> produces
> {color:#0747a6}{{{"key1":"val1", "key2":"{val2.1=val2.2}"}}}{color}
> whereas
> {color:#0747a6}{{{"key1":"val1", "key2":{"val2.1":"val2.2}"}}}{color}
> was expected.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
