[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349583#comment-15349583
]
Mikael Ståldal commented on LOG4J2-1010:
----------------------------------------
* I think that most (if not all) custom injectors will want to keep the default
handling of configuration properties, and it is not optimal to have to copy the
code for that into all of them.
* Ideally the authors of asynchronous frameworks will include a Log4j context
injector. However, in practice I think that in many cases someone else needs to
do it since those authors will not bother. Having such injector is useful even
if the framework itself does not use Log4j. I agree that it would be good if
the user doesn't need to configure it though (neither in the configuration
file, nor through a system property).
* I don't see any obvious use case for multiple injectors, so we can keep it to
just one.
> 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
