[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346781#comment-15346781
]
Mikael Ståldal commented on LOG4J2-1010:
----------------------------------------
Don't get me wrong. I like this injector approach in general, it is better than
my idea of adding a parameter to {{ExtendedLogger.logMessage}} (so let's forget
about it).
We just have to sort out the details about how the interface should look, and
where it should be (log4j-api or log4j-core). Maybe [~ralphgoers],
[~garydgregory] or [~jvz] have some input on this?
BTW, I want it to be possible to inject String key-value pairs that can be
consumed by existing Layouts and Appenders not aware of this new feature, to
them it should look exactly like the current ThreadContext map.
BTW2, should we support injection of context stack as well, or can we consider
that deprecated (I have never used that)?
> 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
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
