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/09/27 22:50:04 UTC

DO NOT REPLY [Bug 13099] New: - 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

           Summary: DOMConfigurator ignores category factory setting
           Product: Log4j
           Version: 1.2
          Platform: PC
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Configurator
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: douglasscottjackson@yahoo.com


When using the default heirarchy i.e. DOMConfigurator.configure(Element)
the <categoryFactory> tag has no effect.  The parseCategory method calls
getLogger(String) which will use the default LoggerFactory and not the
category factory specified in the <categoryFactory> tag.
The <categoryFactory> tag appears to have no effect whatsoever.

It would be nice if the defaultFactory in the Heirarchy class could be
modified via a setter or make it protected so an extending class can set
it.

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