[
https://issues.apache.org/jira/browse/LOG4J2-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15443390#comment-15443390
]
Remko Popma commented on LOG4J2-1010:
-------------------------------------
That would not solve the problem and would add a new one:
* The {{inject}} method is meant to return an object that is safe to pass to
another thread. If the original context data is not a copy-on-write structure
the {{inject}} method must make a copy. For filters we want to avoid making
that copy, hence we must introduce a new method with different semantics.
* If the {{ContextDataInjector}} is not going to merge the configuration
properties, who will?
The second problem may be solvable, but I think we need a new method anyway to
solve the first problem.
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
