You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by bu...@apache.org on 2002/10/01 21:13:16 UTC

DO NOT REPLY [Bug 13099] - DOMConfigurator ignores category factory setting

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13099>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13099

DOMConfigurator ignores category factory setting





------- Additional Comments From asisser@lehman.com  2002-10-01 19:13 -------
I've noticed it too and this causes serious problems for me because I've 
subclassed the Logger class.  When the DOMConfigurator runs and tries to set 
the log level for specific categories, it ignores the categoryFactory and 
creates default log4j.Logger objects.  These choke my code when I go to load 
the appropriate Logger and cast it to my own Logger sub-class.  Not only is not 
setting the defaultFactory, it's not even using the LoggerFactory to create the 
Logger objects it needs during configuration.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>