[
https://issues.apache.org/jira/browse/LOG4J2-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker closed LOG4J2-1763.
-------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.8)
Turns out that there's a bug in JDK 7 that prevents caller sensitive methods
like {{getCallerClass(int)}} from working properly via MethodHandle. Oh well. :(
> Use MethodHandle instead of Method in ReflectionUtil
> ----------------------------------------------------
>
> Key: LOG4J2-1763
> URL: https://issues.apache.org/jira/browse/LOG4J2-1763
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Reporter: Matt Sicker
> Assignee: Matt Sicker
>
> Since Log4j requires Java 7, performance-sensitive use of reflection can
> generally be replaced with the MethodHandle API. This is almost as good as
> direct access to the underlying method and only requires a single security
> access check on creation rather than on every invocation of the method.
--
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
