[
https://issues.apache.org/jira/browse/BROOKLYN-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14230010#comment-14230010
]
Hadrian Zbarcea commented on BROOKLYN-92:
-----------------------------------------
On the slf4j topic, I'll look around, I don't remember seeing one single
reference. I'll look for one.
One of the improvements in slf4j is the syntax using the format. The idea was
that using string concatenation to provide the log string was causing the
reallocation to take place regardless if logging will actually be performed. In
slf4j, the formating of the log message is only done if logging is enabled for
that level, so the if*Enabled call is already made in the implementation of
slf4j and hence not necessary outside as a guard.
That said [log4j 2.0|http://logging.apache.org/log4j/2.x/manual/] is gaining a
lot of momentum as well, something to keep an eye on.
> Support for customized brokerName for ActiveMQ
> ----------------------------------------------
>
> Key: BROOKLYN-92
> URL: https://issues.apache.org/jira/browse/BROOKLYN-92
> Project: Brooklyn
> Issue Type: Improvement
> Reporter: Hadrian Zbarcea
> Fix For: 0.7.0-M2
>
>
> Mandatory feature for more complex topologies, like networks of brokers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
