[
https://issues.apache.org/jira/browse/LOG4J2-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15350662#comment-15350662
]
Mikael Ståldal commented on LOG4J2-1181:
----------------------------------------
I am looking at how to do flow tracing in the Scala API. Does this look good?
(Quick Scala intro: types goes after variables/methods/parameters,
{{Unit}} is like void in Java, {{AnyRef}} is like Object in Java, the {{*}} is
varargs)
{code}
def traceEntry(): EntryMessage
def traceEntry(params: Any*): EntryMessage
def traceEntry(message: Message): EntryMessage
def traceExit(): Unit
def traceExit[R](result: R): R
def traceExit(entryMessage: EntryMessage): Unit
def traceExit[R](entryMessage: EntryMessage, result: R): R
def traceExit[R](message: Message, result: R): R
{code}
> Scala wrapper for Log4j 2 API
> -----------------------------
>
> Key: LOG4J2-1181
> URL: https://issues.apache.org/jira/browse/LOG4J2-1181
> Project: Log4j 2
> Issue Type: New Feature
> Components: API
> Affects Versions: 2.4.1, 2.5, 2.6, 2.6.1
> Reporter: Mikael Ståldal
>
> Scala wrapper for Log4j 2 API which makes use of Scala features like macros
> and string interpolation.
> Inspired from [Typesafe's Scala
> Logging|https://github.com/typesafehub/scala-logging] but should use Log4j 2
> directly and expose its features.
--
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
