I notice it also supports lazy evaluation of the logging data. That is, you can
write:
logger.debug("Some data: {}", anObject)
Without worrying about the time to convert anObject to a string. That will
remove a lot of code like:
if (logger.isDebugEnabled()) {
}
That alone seems worth it.
Ari
On 29/3/17 4:52pm, Andrus Adamchik wrote:
> Also AFAIK commons-logging does not support MDC [1]. The use of MDC may
> improve Cayenne transaction tracking in the logs.
>
> Andrus
>
> [1] https://logback.qos.ch/manual/mdc.html
>
>> On Mar 28, 2017, at 1:53 AM, Mike Kienenberger <[email protected]> wrote:
>>
>> On Mon, Mar 27, 2017 at 6:20 PM, Aristedes Maniatis <[email protected]>
>> wrote:
>>> * using log4j or other library
>>
>> Pick one logging library (ie, log4j). Add the "log to log4j from slf4j" jar.
>> For all other logging libraries, add "log to slf4j from *" jars.
>>
>> It's pretty much that simple, although really badly designed logging
>> libraries like java.util.logging may require extra steps or run
>> poorly.
>>
>>
>>> * having other libraries in the classpath with different versions of slf4j
>>
>> the slf4j api is pretty much backward compatible no matter what
>> version you use, and jars don't inline slf4j. So you can just pick
>> whatever version you like, generally the latest slf4j version
>> available.
>
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
