[
https://issues.apache.org/jira/browse/LOG4J2-623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996256#comment-13996256
]
Joern Huxhorn commented on LOG4J2-623:
--------------------------------------
If you are interested: [this|http://pastebin.com/zFCdVGNd] is an example of the
Lilith JSON.
Take a look at the encoder/decoder over at
[GitHub|https://github.com/huxi/lilith/tree/master/lilith-data/logging-json-serializer/src/main/java/de/huxhorn/lilith/data/logging/json].
It's using Jackson (which is available under Apache license).
I have yet to see any use of JSON Schema in the wild. The usual parsers
(Jackson, Boon, GSON) certainly don't support it and if it doesn't support
key-value maps like the above then it's useless anyway.
> 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: [email protected]
For additional commands, e-mail: [email protected]
