[
https://issues.apache.org/jira/browse/LOG4J2-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350232#comment-15350232
]
Gary Gregory edited comment on LOG4J2-1449 at 6/26/16 8:45 PM:
---------------------------------------------------------------
I am thinking of a way to allow a {{StackTraceElementFactory}} to come into
play without having to augment the Logger API.
Also, unrolling the location as "String methodName, String fileName, int
lineNumber" seems not OO to me. You could imaging other kinds of location
information containing for or less than that ;-)
Where would you plugin a {{StackTraceElementFactory}}?
was (Author: garydgregory):
I am thinking of a way to allow a {{StackTraceElementFactory}} to come into
play without having to augment the Logger API.
Also, unrolling the location as "String methodName, String fileName, int
lineNumber" seens not OO to me. You could imaging other kinds of location
information containing for or less than that ;-)
Where would you plugin a {{StackTraceElementFactory}}?
> Injectable location info
> ------------------------
>
> Key: LOG4J2-1449
> URL: https://issues.apache.org/jira/browse/LOG4J2-1449
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.6.1
> Reporter: Mikael Ståldal
> Priority: Minor
>
> In some JVM languages, such as Scala, it is possible to generate location
> info much more efficiently by using compile-time macros.
> It would be nice if it was possible to inject this location info into Log4j,
> and thus avoid the inefficient runtime stack inspection.
--
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
