At 15:18 11.06.2002 +0100, Paul Duffin wrote: >As has been illustrated in other posts log4j does not have a very >good history when it comes to binary compatability.
What has been illustrated was: 1) Category.assert was replaced with Category.assertLog without deprecation. First, no one has ever complained about this. Second, it was done because "assert" is a new JDK 1.4 reserved keyword. 2) LoggingEvent.getThrowableInformation() used to return a String but now returns a ThrowableInformation. The exact quote in John's email is: > After a bit of head scratching we get the source for log4j 1.2 and add > in the needed Category.assert method and everything seems OK until one > of our users opens the rarely used logging window and we get a stack > trace because LoggingEvent.getThrowableInformation() used to return a > String but now returns a ThrowableInformation. We are beginning to > suspect that this problem is going to be a nightmare to resolve. This conveniently ignores the fact that LoggingEvent is an internal log4j class. Damned if you do, damned if you don't. -- Ceki -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>