This subject has been discussed many times in the past. Please refer to the archives.
No, it is not a bug. Subclassing logger class is discouraged. Consequently, the logger tag does not allow for a class attribute. However, you can get around this by various means which I am not going to disclose here as the means are deprecated, discouraged or both.
I recommend wrapping instead of sub-classing.
At 12:21 PM 7/14/2003 -0700, Sanjay Gupta (sanjaygu) wrote:
Hi,
I am trying to subclass Logger(Category) & LoggerFactory and use DOMConfigurator(log4j.xml). I ran into interesting problem. My stuff works fine when I configure the logger from program i.e. not using a xml or properties file. But when I use xml file, it turns out that <logger> tag does not have a way of specifying class so My subclassed Logger never gets instanciated. I digged deeper and figured out that <category> tag has "class" attribute. So, now I am confused. Should I subclass Logger or Category. If I should subclass Logger then how can I make sure that my subclassed Logger gets instanciated from the log4j.xml and not org.apache.log4j.Logger?
I think that it might be a bug?
Regards, -Sanjay
--
Ceki For log4j documentation consider "The complete log4j manual"
ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
