logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Glezen" <pgle...@us.ibm.com>
Subject Re: version change....
Date Mon, 29 Jan 2001 15:12:36 GMT
People should be aware that the last couple of major log4j releases have
involved name changes: the 1.0 release some particularly significant ones
(i.e. the whole package structure).  If you were careful to have most of
your initialization in one place and used import statements instead of
fully qualified package names in your source, you are relatively unscathed.
Otherwise the rework can be rather significant.

If you have a network of application servers sending logging events to
various listeners, this can be a problem.  Every place in the path of a
logging event must be updated at the same time since a serialized 0.9
LoggingEvent class is not compatible with a serialized 1.0 LoggingEvent
class.  Thus from the time you change the first app server to the time you
change the listener and everything in between, logging will fail (of course
you still have the local logs on the app server).

- Paul

Paul Glezen
IT Specialist
WebSphere Engagement Team
Tel: 818 539 3321
pglezen@us.ibm.com


Ceki Gülcü <cgu@urbanet.ch> on 01/29/2001 05:02:26 AM

Please respond to "LOG4J Developers Mailing List"
      <log4j-dev@jakarta.apache.org>

To:   "LOG4J Developers Mailing List" <log4j-dev@jakarta.apache.org>
cc:   Sallaram Madhu <sallaram.m@mellon.com>
Subject:  Re: version change....




Madhu,

As Anders Kristensen mentioned earlier, all existing versions of log4j are
compatible with JDK 1.1 or above, including JDK 1.2 and JDK 1.3.

It is recommended (but not necessary) that you upgrade to the latest
version of log4j. Newer versions are more feature rich. More importantly,
new versions fix any existing bugs in older versions. So even if you do not
use the newly introduced features, you are likely to gain by the bug fixes.
On the other hand, if you are happy with the existing log4j functionality,
there is no need to upgrade. Cheers, Ceki

ps: You can make a more educated decision on whether to upgrade or not, by
reading the HISTORY file: http://jakarta.apache.org/log4j/doc/HISTORY

At 17:24 26.01.2001 -0500, you wrote:
>Hi All,
>
>            We are using Log4j version 0.8.5 and java version 1.1.7.
>Now we are installing java 1.2.  Will Log4j 0.8.5 support to Java 1.2 ?
>Do i need to install latest version ? Please let me know.
>
>   Thanx,
>       -Madhu Sallaram
>
>
>*****************************************************************
>DISCLAIMER:   The information contained in this e-mail may be confidential
>and is intended solely for the use of the named addressee.  Access,
copying
>or re-use of the e-mail or any information contained therein by any other
>person is not authorized.  If you are not the intended recipient please
>notify us immediately by returning the e-mail to the originator.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-cvs-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-cvs-help@jakarta.apache.org

----
Ceki Gülcü - Independent IT Consultant

av. de Rumine 5            Tel: ++41 21 351 23 15
CH-1005 Lausanne        e-mail: cgu@urbanet.ch  or
Switzerland                     ceki_gulcu@yahoo.com


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




Mime
View raw message