[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347633#comment-15347633
]
Ralph Goers commented on LOG4J2-1010:
-------------------------------------
OK - I've read this whole thing:
1. I never really like the context stack and only brought it over because Log4j
1 has it. Frankly, I'd be afraid applications would get the stack out of sync.
So I don't think what you are proposing needs to support a stack.
2. I didn't like adding a parameter to logMessage. Glad you have discarded the
idea.
3. I have no problem with the interface proposed by Remko. I believe it belongs
in Core.
> Injectable context properties
> -----------------------------
>
> Key: LOG4J2-1010
> URL: https://issues.apache.org/jira/browse/LOG4J2-1010
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.2
> Reporter: Mikael Ståldal
> Assignee: Remko Popma
> Fix For: 2.7
>
> Attachments: properties.patch
>
>
> It would be useful to have a way to inject context properties into a
> {{LogEvent}}, as an alternative to {{ThreadContext}}.
> In an asynchronous environment, using ThreadContext as currently implemented
> is not so useful since JVM threads might not be coupled to the logical flow
> of the application.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
