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/07/24 22:47:56 UTC

DO NOT REPLY [Bug 11142] New: - org.apache.log4j.net.SocketServer doesn't work with DOMConfigurator

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=11142>.
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=11142

org.apache.log4j.net.SocketServer doesn't work with DOMConfigurator

           Summary: org.apache.log4j.net.SocketServer doesn't work with
                    DOMConfigurator
           Product: Log4j
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Other
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: shunter@mail.com


As the docs say, PropertyConfigurator isn't nearly as flexible as 
DOMConfigurator.  Is there a reason _not_ to allow this?  I've been using a 
simple (i.e. not bulletproof) fix (in 3 places):
 
    if (configFile.endsWith(".xml"))
        DOMConfigurator.configure(configFile);
    else PropertyConfigurator.configure(configFile);

Let me know _how_ you want this fixed for real (if it's not restricted for a 
reason) and I'd be happy to do it.

Regards -
  --Steve

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