[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432795#comment-15432795
]
Ralph Goers commented on LOG4J2-1010:
-------------------------------------
Now that is confusing. How is a user supposed to know when to use which?
I'm still also not clear on how they are different. If there is a LogEvent
don't they behave the same?
If the user should be able to choose between behaviors I would add a parameter
to the ThreadContextMapFilter. Otherwise get the values from the currently
configured context. Also, if you want to add an alias to the
ThreadContextMapFilter so that user's can use a shorter name I am fine with
that.
> Injectable context properties
> -----------------------------
>
> Key: LOG4J2-1010
> URL: https://issues.apache.org/jira/browse/LOG4J2-1010
> Project: Log4j 2
> Issue Type: Improvement
> Components: Core
> 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]
