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/06/14 20:36:17 UTC

DO NOT REPLY [Bug 9879] New: - Hierarchy constructor is not backward compatible

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

Hierarchy constructor is not backward compatible

           Summary: Hierarchy constructor is not backward compatible
           Product: Log4j
           Version: 1.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Other
        AssignedTo: log4j-dev@jakarta.apache.org
        ReportedBy: eostrom@placeware.com


We use a third-party library ("realMethods") that uses Log4j, and also use 
Log4j in our own code.  I recently tried to upgrade to Log4j 1.2.1, which is 
supposed to be a drop-in replacement for 1.1.3, but it isn't.

The constructor for Hierarchy changed from Hierarchy(Category) to Hierarchy
(Logger).  This means the existing code that tries to pass a Category to the 
constructor can't be compiled.

RealMethods could change their library to work with Log4j 1.2 by switching from 
Category to Logger, but then it wouldn't work for people who are still using 
Log4j 1.1.  I believe Hierarchy should be able to accept a Category in its 
constructor; or, failing that, documentation of 1.2's backward compatbility 
(such as http://jakarta.apache.org/log4j/docs/download.html) should mention the 
issue.

Thanks.

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