You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Matt Sicker (JIRA)" <ji...@apache.org> on 2017/01/04 04:58:58 UTC
[jira] [Reopened] (LOG4J2-1763) Use MethodHandle instead of Method
in ReflectionUtil
[ https://issues.apache.org/jira/browse/LOG4J2-1763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Sicker reopened LOG4J2-1763:
---------------------------------
Reopening as there appears to be a bug in JDK 7 but not JDK 8 with the current implementation.
> 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
> Fix For: 2.8
>
>
> 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org