[
https://issues.apache.org/jira/browse/LOG4J2-1449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350217#comment-15350217
]
Mikael Ståldal edited comment on LOG4J2-1449 at 6/26/16 8:27 PM:
-----------------------------------------------------------------
I know [~ralphgoers] will hate me now, but I think that extra parameters to
{{ExtendedLogger.logMessage}} would be suitable for this:
{code}
void logMessage(String fqcn, Level level, Marker marker, Message message,
Throwable t, String declaringClass, String methodName, fileName, int
lineNumber);
{code}
(Better to not use {{java.lang.StackTraceElement}} here since it is final and
immutable, and would thus defeat garbage free logging.)
was (Author: mikaelstaldal):
I know [~ralphgoers] will hate me now, but I think that an extra parameter to
{{ExtendedLogger.logMessage}} would be suitable for this:
{code}
void logMessage(String fqcn, Level level, Marker marker, Message message,
Throwable t, StackTraceElement source);
{code}
> 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
