[ https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13995287#comment-13995287 ]
Ralph Goers commented on LOG4J2-623: ------------------------------------ That is hardly surprising since the JSON spec doesn't define a "Map". However, you can find plenty of examples where people are validating Maps using the proper syntax. Remember, in JSON a "Map" is nothing more than an array with a String key and a value (where the value can be one or more objects). I am not in favor of forcing a non-standard JSON syntax for this. This has nothing to do with XML. The "standard" way to define a Map in XML is as you have specified it. It sounds to me like you are trying to force a square peg in a round hole. > Better structure of Thread Context Map in JSONLayout > ---------------------------------------------------- > > Key: LOG4J2-623 > URL: https://issues.apache.org/jira/browse/LOG4J2-623 > Project: Log4j 2 > Issue Type: Improvement > Components: Layouts > Affects Versions: 2.0-rc1 > Reporter: Mikael Ståldal > Assignee: Ralph Goers > Priority: Minor > Fix For: 2.0-rc2 > > > Currently, the Thread Context Map looks like this in JSONLayout: > {code:JavaScript|title=Current} > "Properties":[ > { > "name":"UserName", > "value":"admin" > }, > { > "name":"OrgName", > "value":"test" > } > ] > {code} > This does not properly make use of the JSON data format. Since the Thread > Context Map is a map, it should be represented as a JSON object. And why not > name it "mdc" rather than the quite vauge "Properties"? > {code:JavaScript|title=Suggested} > "mdc": { > "UserName":"admin", > "OrgName":"test" > } > {code} -- This message was sent by Atlassian JIRA (v6.2#6252) --------------------------------------------------------------------- To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org