[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349624#comment-15349624
]
Mikael Ståldal commented on LOG4J2-1010:
----------------------------------------
A system property would work, but it would also be inconvenient.
BTW, for me it will not be a *Scala* context injector. It will be a Finagle
context injector.
So this context injector should be kept separate from, and orthogonal to, the
Scala API.
This is not specific to Scala. It could be useful to make context injectors for
e.g. [Akka for Java|http://doc.akka.io/docs/akka/2.4.7/java.html], or [async
Servlets|https://docs.oracle.com/javaee/7/tutorial/servlets012.htm].
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
