[
https://issues.apache.org/jira/browse/LOG4J2-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14123726#comment-14123726
]
Matt Sicker commented on LOG4J2-809:
------------------------------------
I've also updated LogManager to take advantage of this class as well as to use
the ClassLoader of the Class provided to LogManager. This should help speed up
ClassLoaderContextSelector as well as make it work more correctly in Java EE
environments. In fact, should this idea work well, then the JNDI
ContextSelector won't be so important anymore!
> Move caller class reflection utils to API
> -----------------------------------------
>
> Key: LOG4J2-809
> URL: https://issues.apache.org/jira/browse/LOG4J2-809
> Project: Log4j 2
> Issue Type: Task
> Components: API
> Affects Versions: 2.1
> Reporter: Matt Sicker
> Assignee: Matt Sicker
>
> In particular, ReflectiveCallerClassUtility should be moved into the API
> inside the util package. This will provide a nice alternative for making a
> new Throwable each time.
> For an idea on why this can be useful, run the ReflectionBenchmark in
> log4j-perf and note the differences. It's rather significant.
> Since this would go in the util package, it would be a non-public API. It
> would make sense for some very, very common utility classes like this to be
> in there.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
