Re: [Quickfixj-users] Confusion about why SLF4JLog changes aren't in the latest archive

[Ted G. <tg...@Co...>]

Isn't it always the case, you send a question and immediately find the
answer.  It turns out that quickfixj is still using slf4j1.3.0, while I am
using the 1.4.3 version.  The value of the INFO_INT constant was 1 in 1.3
and is 20 in 1.4.3.

So it appears that compiling the quickfixj jar against the slf4j1.3.0
version resulted in INFO_INT being set to 1, rather than reading the value
at runtime.

My apologies for any confusion,

Ted


-----Original Message-----
From: Ted Graham [mailto:tg...@Co...] 
Sent: Friday, October 05, 2007 9:09 AM
To: 'qui...@li...'
Subject: Confusion about why SLF4JLog changes aren't in the latest archive

I downloaded the latest (Sept 23rd ) release of quickfixj-core.jar.  When I
open it up and decompile the SLF4JLog.class, I find the following line
inside the log method:

	la.log(null, callerFQCN, 1, message, null);

Notice that it is passing 1 as the log level.  However, in the src download,
and in the subversion repository, it is passing
LocationAwareLogger.INFO_INT.  Now if I check this file's history in
Subversion, I see this file was changed on April 6, 2007.  

So why isn't the change to pass LocationAwareLogger.INFO_INT included in
quickfixj-core.jar?

I'm somewhat new to java and very new to quickfixj, so if I have
misunderstood, I'd appreciate an explanation.

Thanks,
Ted