commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 9845] - Default LogFactory Implementation fails for Log4J : ClassCastException
Date Sat, 26 Apr 2003 22:08:42 GMT
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=9845>.
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=9845

Default LogFactory Implementation fails for Log4J : ClassCastException

craig.mcclanahan@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From craig.mcclanahan@sun.com  2003-04-26 22:08 -------
Marking as closed, because as far as I can tell this works correctly with 1.0.3.

As a side note, one cause for ClassCastException problems would be having
commons-logging classes available from more than one class loader, and not being
careful to ensure that all the c-l classes are loaded from the same class
loader.  A class "foo" loaded from class loader A and a class "foo" loaded from
class loader B are not the same class, even if the bytecodes happen to be identical.
Attempts to do assignments or casts between them will fail.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message