logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-809) Move caller class reflection utils to API
Date Thu, 04 Sep 2014 18:50:51 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121754#comment-14121754

Matt Sicker commented on LOG4J2-809:

And it's still [in the JDK9 code as of now|http://hg.openjdk.java.net/jdk9/jdk9/jdk/file/tip/src/java.base/share/classes/sun/reflect/Reflection.java].

> 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

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message