ceki 01/08/06 07:53:06 Modified: docs critique.html critique2.html Log: Changes to critique*.html files. Revision Changes Path 1.20 +14 -9 jakarta-log4j/docs/critique.html Index: critique.html =================================================================== RCS file: /home/cvs/jakarta-log4j/docs/critique.html,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- critique.html 2001/07/30 20:32:09 1.19 +++ critique.html 2001/08/06 14:53:06 1.20 @@ -15,20 +15,24 @@ <hr> <p>I consider it quite distasteful to criticize other people's work, especially in public. However, since the logging API included in JDK -1.4 will be potentially considered as the "standard", I feel compelled -to react. I am not alone in my criticism of JSR47, Greg Davis has his -own set of <a -href="http://www.swzoo.org/documents/miscellaneous/jsr047/";>comments</a>. +1.4 will be considered by many as the "standard", I feel compelled to +react. I am not alone in my criticism of JSR47, Greg Davis has his own +set of <a +href="http://www.swzoo.org/documents/miscellaneous/jsr047/";>comments</a>. Please +also see the <a href="critique2.html"><b>follow up</b></a> to this +article. + <p>The JDK 1.4 logging API is a result of the <a href="http://jcp.org/aboutJava/communityprocess/review/jsr047/index.html";>JSR47 -effort</a>, led by Graham Hamilton. +effort</a>, led by Graham Hamilton. <p>Before delving into the details, some historical perspective is in order. I am the founder of the log4j project. I participated in the specification of the JSR47 API, although not as an expert. In 1999, I -was still working for IBM and big blue had already Chris Barlock as a -member in the JSR47 experts group. Chris is the author of <a +was still working for IBM and could not join the experts group because +big blue had already Chris Barlock as a member in the JSR47 experts +group. Chris is the author of <a href="http://www.alphaworks.ibm.com/tech/loggingtoolkit4j";>IBM's logging toolkit for Java</a>. @@ -41,7 +45,6 @@ formatter and layout will be used interchangeably in the remainder of this document. - <p>Even after a casual review it should be apparent that the log4j and JSR47 APIs are <em>very</em> similar. For one, they are the only logging APIs which are based on a named hierarchy. If you understand @@ -555,7 +558,9 @@ computing platform. Sun deserves credit for their ongoing investment. They have also introduced a number of amazingly innovative APIs. However, no one gets it right <em>all</em> the time. + +<p>Please also see the <a href="critique2.html"><b>follow up</b></a> +to this article. -<p> </body> </HTML> 1.2 +27 -24 jakarta-log4j/docs/critique2.html Index: critique2.html =================================================================== RCS file: /home/cvs/jakarta-log4j/docs/critique2.html,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- critique2.html 2001/08/02 12:04:26 1.1 +++ critique2.html 2001/08/06 14:53:06 1.2 @@ -17,32 +17,31 @@ <p>In the forthcoming, still unpublished draft of JSR47, the <code>java.util.logging</code> API will resemble log4j even more than is the case now. The way the two APIs name their components may -differ but otherwise their degree of resemblance is quite frightening. +differ but otherwise their degree of resemblance is quite striking. <p>Changes introduced in the latest draft include configuration order independence, appender inheritance, resource bundle inheritance, error handlers and lazy inference of caller information. In other words, even if the priority levels remain unchanged and equally bogus, the -vast majority of the points raised in my <a -href="critique.html">previous critique</a> of JSR47 are now obsolete. -This is clearly good news. - -<p>It is fair to say that our campaign to influence the JSR47 API has -handsomely bore fruit. I wish to thank the hundreds of concerned users -who have expressed their support for log4j. My gratitude goes to Jason -Hunter for arranging the appropriate communication channel to -Sun. Graham Hamilton, the JSR47 specification lead, was very open and -receptive during our exchanges. - -<p>As one of its authors, I still think that at its core log4j is a -better API in some small ways. These differences are explained in the -next section. +majority of the points raised in my <a href="critique.html">previous +critique</a> of JSR47 are now obsolete. +<p>Consequently, it is fair to say that our campaign to influence the +JSR47 API handsomely bore fruit. I wish to thank the hundreds of +concerned users who have expressed their support for log4j. My +gratitude goes to Jason Hunter for arranging the appropriate +communication channel to Sun. Graham Hamilton, the JSR47 specification +lead, was very open and receptive during our exchanges. + +<p>As one of its authors, I still think that at log4j core API is +better in some small ways. These differences are explained in the next +section. + <p>There remain two critical differences however. First, JSR47 requires JDK 1.4 whereas log4j is compatible with JDK 1.1 and later. Second, log4j offers much more functionality. It supports a -rich configuration language and about a thousand appenders and layouts -among other very useful features. +rich configuration language, at least a dozen appenders and layouts as +well as many other useful features. <p>Efforts to backport JSR47 to earlier JDKs are doomed to fail because the <code>java.util.logging</code> package is located under @@ -53,15 +52,20 @@ Sun can be expected to defend its trademark. <p>Even without the <code>SecurityException</code> and the trademark -issue, the backported code would need to be installed. If you are -going to install a logging API, then why not install log4j which -offers a lot more than JSR47 and is backward compatible with JDK 1.1? +issue, you would need an additional logging library to fill in the +functionality gap, the JDK compatibility gap, or both. If you are +going to install one or more logging APIs, then why not install log4j +which offers a lot more than JSR47 and is backward compatible with JDK +1.1? <p>Log4j is the de facto standard logging API in Java. It has been ported to Python, C++ and the much maligned C#. By adopting log4j, you simultaneously benefit from much richer functionality and wider JDK -compatibility. In any case, the log4j project will continue to -innovate and lead the way. +compatibility. + +<p>In any case, the log4j project will continue to innovate and lead +the way. As such, many of the features that you need or will need in +the future will be first available in log4j. <h2>Remaining differences</h2> @@ -154,8 +158,7 @@ <p>Err... not exactly a useful feature nor consistent with the rest of the JSR47 API. - - +</ol> </body> </HTML> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
