At 15:09 10.09.2001 -0400, Sam Ruby wrote:
>Ceki Gülcü wrote:
>>
>> After log4j 1.2 comes out users should not use the Category class at all.
>> The deprecation of Category.getInstance and Category.getRoot helps to push
>> that point across.
>
>If I am working on a project which is expected to come out after 1.2, what
>should I code to now. I asked you privately if I should code to Logger
>now, and you discouraged me.
>
>Now I am confused.
Hmm. I understand and am sorry about the confusion. As long as log4j 1.2
is not released, I still maintain that you should code for the Category class
and discourage you from coding for Logger. Mind you, it would probably work
just fine, but better safe than sorry. I rather not have the wider public serve
as guinea pigs just yet. Nevertheless, somebody has to test the new code
and it should be the log4j developers rather than the wider public --
that is why I am using a pre-alpha version of log4j in my own non-log4j projects.
After log4j 1.2 comes out, users should not (but may) write code using the Category
class.
Older code is guaranteed to work, i.e. we have 100% backward compatibility.
When log4j 1.2 comes out you can *gradually* replace
import org.apache.log4j.Category;
with
import org.apache.log4j.Logger;
and
Category x = Category.getInstance("some.name");
with
Logger x = Logger.getLogger("some.name");
How does that sound? Regards, Ceki
--
Ceki Gülcü - http://qos.ch
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
