[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15346670#comment-15346670
]
Remko Popma edited comment on LOG4J2-1010 at 6/23/16 4:08 PM:
--------------------------------------------------------------
Ah! No, what I had in mind is to put this interface in the
{{org.apache.logging.log4j.core.impl}} package, which is where the
LogEventFactory is. The {{ContextInjector}} interface is intended to be used by
objects that either create or initialize LogEvents, so this is a log4j-core
concept.
It decouples the LogEvent context data from the log4j-api ThreadContext, which
gives you the freedom to swap in context data from Scala Locals.
was (Author: rem...@yahoo.com):
Ah! No, what I had in mind is to put this interface in the
{{org.apache.logging.log4j.core.impl}} package, which is where the
LogEventFactory is.
> 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
