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 2014/09/21 19:10:34 UTC

[jira] [Closed] (LOG4J2-809) Move caller class reflection utils to API

     [ https://issues.apache.org/jira/browse/LOG4J2-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sicker closed LOG4J2-809.
------------------------------

Pushed to master.

> 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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org