I have had a look in the FAQ and in the archives but I cannot
find any discussion about why the Category class is being renamed
Logger.

I can understand that Logger may be a more descriptive name but
surely you cannot be changing the name of such a widely used class
just for this reason.

While it may be backwardly compatible for the most part (extensions
of Category aside) it will be removed at some time in the future
and at that point there will be two sets of incompatible versions
of log4j. While this does not matter for those people who can control
what version they run with there are somepeople (us for one) who
may not be able to control what version they run with which will
cause us a big problem.

Rather than remove Category completely you could provide a
compatability jar file which contains a Category class extended
from Logger (rather than the other way around as it is now)
which would probably fix most of the problems to do with
changing the name.

You could also provide an extension to the current stable version
of log4j which contains a Logger class based on the Category
class.

-- 
This message may contain confidential information and will be protected
by copyright. If this email isn't for you then we'd be grateful if you
could notify Volantis by return and delete it. You should not copy,
disclose or distribute any of its contents.

Any reply may be read by the recipient to whom you send it and others
within Volantis Systems Ltd.

Although we aim to use efficient virus checking procedures we accept no
liability for viruses and recipients should use their own virus checking
procedures.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to