logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-599) Support lambda functions (or similar) for log message parameters
Date Mon, 10 Aug 2015 06:21:46 GMT

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

Gary Gregory commented on LOG4J2-599:
-------------------------------------

About {{entry(Object...)}}: {{Object}} does not do anything interesting for arrays. Printing
the default toString for an [] array is pretty useless.

At work, I've had to come up with a custom entry/exit flow logger to get around this and other
flow tracing issues. I clearly do not want to do an {{Arrays.toString()}} unless a given level
is enabled. Without using {{Supplier}}, there is no on-liner shorthand for this like we have
for other {{Logger}} calls.

Presenting a flow logger alternative is a topic for a different Jira/thread of course.

> Support lambda functions (or similar) for log message parameters
> ----------------------------------------------------------------
>
>                 Key: LOG4J2-599
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-599
>             Project: Log4j 2
>          Issue Type: Brainstorming
>          Components: Core
>            Reporter: Matt Sicker
>            Assignee: Remko Popma
>            Priority: Minor
>              Labels: Java8
>             Fix For: 2.4
>
>
> It would be nice if we could support 0-param lambda functions (or the equivalent: interfaces
with a single empty-parameter message call), or more simply, allow Runnables (or something
similar) to be passed which will be dynamically executed if the log message is enabled.
> The use case here is that although string construction of the log message is a performance
issue that is already solved quite well, the problem of adding in information to the log message
that makes other calculations still needs to be wrapped in an if check.
> I'm not sure if it'd be best to just use Runnable, or create a new interface, or try
to emulate how Java 1.8 lambdas work via an interface with a single method defined. The details
here would still need to be fleshed out, but I think this sort of feature could be rather
handy (especially in a Java 1.8+ environment, or in Groovy/Scala/etc.).



--
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


Mime
View raw message