logging-log4j-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raúl Carazo <rcar...@bilbomatica.es>
Subject Re: log4j 1.2 not fully compatible with 1.1
Date Fri, 09 Aug 2002 06:20:03 GMT
    It's true (as far as I can see), but there's a good way to avoid it...

    If you create a class to extend Category and another for
CategoryFactory, you can use them ofr logging, instead of Category. But if
you need to change something (like the extension to Logger and
LoggerFactory), you just need to change this classes, not every class...

----- Original Message -----
From: "Doug" <ummmmm22@yahoo.com>
To: <log4j-user@jakarta.apache.org>
Sent: Thursday, August 08, 2002 4:34 PM
Subject: log4j 1.2 not fully compatible with 1.1


> i just wanted to vent my frustration at my realization
> that backwards compatibility was not maintained for
> users who have implemented custom
> Category/CategoryFactory/Priority classes, which we
> did.
>
> i realize this is a non-recommended practice, but it
> made good sense in our case.  the framework supported
> it, and still does, but in an incompatible fashion.
> this is forcing us to either change all of our code or
> stay at the 1.1 level (which has known bugs in it like
> for RollingFileAppender).  sigh.
>
> - doug
>
> __________________________________________________
> Do You Yahoo!?
> HotJobs - Search Thousands of New Jobs
> http://www.hotjobs.com
>
> --
> To unsubscribe, e-mail:
<mailto:log4j-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail:
<mailto:log4j-user-help@jakarta.apache.org>


--
To unsubscribe, e-mail:   <mailto:log4j-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:log4j-user-help@jakarta.apache.org>


Mime
View raw message