Martin Poeschl <[EMAIL PROTECTED]> writes:
>Henning P. Schmiedehausen wrote:
>>- Commons Logging using log4j. This is ready, we use it all the time
>> here (couldn't live without) and is basically adding some startup
>> code to Turbine.java, some small glue code to the Velocity Service and
>> then a big replacement Log -> log and adding lines like this
>>
>> private static Log log = LogFactory.getLog(foo.class);
>>
>> to all the classes that need logging. That's why I asked about the
>> JDK 1.3 / JDK 1.4 incompatibilities regarding to direct class
>> references. If we really do have problems here, we must either offer
>> 1.3 and 1.4 compiled binary packages or use
>>
>> private Log log = LogFactory.getLog(this.getClass())
>>
>> which needs more memory as we have more objects and is less performant.
>> Opinions? I'd go for the "private static" option, mainly because building
>> with maven is really not critical and providing two binary distributions
>> is no problem either.
>>
>>
>will
>private static Log log = LogFactory.getLog(foo.class.getName());
>solve the problem??
Good question. I understood from the mail on the users list that all
direct class references are a problem from JDK 1.3 to JDK 1.4 I don't
see no difference between directly using foo.class and
foo.class.getName().
Anyone with deeper knowledge of the JDK here?
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen -- Geschaeftsfuehrer
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH [EMAIL PROTECTED]
Am Schwabachgrund 22 Fon.: 09131 / 50654-0 [EMAIL PROTECTED]
D-91054 Buckenhof Fax.: 09131 / 50654-20
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
