This looks like the same material I've seen before. Default init oesn't
seem to work. Keep getting an error message unless I explicitly
initialize it somewhere, which is a real problem in my multi-entry
system (test cases, servlets, client aps). Just this weekend I went back
to a home-brew static Log class for this very reason.
On Saturday, June 9, 2001, at 11:54 AM, Ceki Gülcü wrote:
>
> Hi Goug,
>
> The user manual in the just released log4j 1.1.2 has a section on
> default initialization, in particular initialization under Tomcat. Be
> sure to read:
> http://jakarta.apache.org/log4j/docs/manual.html#defaultInit
>
> Hope this helps, Ceki
>
>> Hi,
>
>> I am trying to replace the System.out.println() logging in my custom
>> tag library with log4j (using jakarta 3.2.1). I have added
>> Category.getInstance() calls in each tag but I am not sure where I
>> should add the log4j initialisation code. Do I just have a static
>> initialisation block in one of the tags I think will get loaded
>> quickly ? I tried this and I can see messages from the static block in
>> the log file but not messages from other classes - I am not sure why
>> not. But this doesn't seem a very clean way of initialising log4j but
>> I am not sure what else I can do.
>>
>> Any clues to point me in the right direction would be much
>> appreciated. What I am really aiming for is a way of logging all
>> activity from several custom tag libraries in a single log file.
>>
>> Regards
>
>
>
> --
> Ceki Gülcü
>
>
