ceki 01/07/30 13:32:09
Modified: docs HISTORY TROUBLESHOOT.html contactUs.html
critique.html download.html index.html manual.html
plan.html
src/xdocs contactUs.xml
Log:
Documentation changes.
Revision Changes Path
1.55 +15 -0 jakarta-log4j/docs/HISTORY
Index: HISTORY
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/HISTORY,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -r1.54 -r1.55
--- HISTORY 2001/06/19 18:45:22 1.54
+++ HISTORY 2001/07/30 20:32:09 1.55
@@ -5,6 +5,21 @@
client code.
[***] Changes requiring important modifications to existing client code.
+ ??, 2001
+
+ - Release of version 1.2alpha_0
+
+ - Added event reporting capability to the Hierachy class.
+
+ - Corrected a performance bug in the NDC class as observed by Dan Milstein. [*]
+
+ - Removed deprecated methods setOptions and getOptionStrings defined
+ in the org.apache.log4j.spi.OptionHandler interface. This interface
+ is implemented by most log4j appenders and layouts. In particular,
+ all appenders and layouts shipped with log4j contain these
+ deprecated methods. They have become totally redundant after we
+ moved to JavaBeans style configuration in log4j 1.1.
+
June 19, 2001
- Release of version 1.1.3
1.11 +15 -0 jakarta-log4j/docs/TROUBLESHOOT.html
Index: TROUBLESHOOT.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/TROUBLESHOOT.html,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -r1.10 -r1.11
--- TROUBLESHOOT.html 2001/06/27 21:34:30 1.10
+++ TROUBLESHOOT.html 2001/07/30 20:32:09 1.11
@@ -31,6 +31,8 @@
<li><p><a href=#syslogd>I cannot connect to syslogd under linux.</a>
+<li><p><a href=#nosuchpropperty>log4j:WARN No such property [xyz] in
some.appender.or.layout</a>
+
</ul>
<hr>
@@ -231,7 +233,20 @@
</pre>
<li><code>/etc/rc/init.d/syslog restart</code>
+
</ol>
+
+<p><a name=#nosuchpropperty><h3>log4j:WARN No such property [xyz] in
some.appender.or.layout</h3>
+
+<p>If during log4j configuration you get a warning about an inexistent
+property, then you have probably misspelled a property or entered a
+truly unrecognized property for the component you are trying to
+configure in the configuration file.
+
+<p>Log4j version 1.0 did not complain about unrecognized properties
+whereas log4j version 1.1 and later do complain.
+
+
</body>
1.10 +41 -15 jakarta-log4j/docs/contactUs.html
Index: contactUs.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/contactUs.html,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- contactUs.html 2001/05/20 15:03:06 1.9
+++ contactUs.html 2001/07/30 20:32:09 1.10
@@ -116,17 +116,20 @@
<table
border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
- <a name="Reporting tools"><strong>Reporting tools</strong></a>
+ <a name="Bug reporting"><strong>Bug reporting</strong></a>
</font>
</td></tr>
<tr><td><br/></td></tr>
<tr><td>
<blockquote>
<p>Bugs should be reported by using the
-<a href="http://nagoya.apache.org/bugzilla">Apache Bug Database</a>.<br />
-Before reporting a problem, please <a
href="http://nagoya.apache.org/bugzilla/query.cgi">check the database</a>
-and the <a href="HISTORY">project history file</a> to see if the problem is already
known.</p>
- <p>Support requests should be sent
to the log4j-user list (see below).</p>
+<a href="http://nagoya.apache.org/bugzilla">Apache Bug Database</a>.</p>
+ <p>Before reporting a problem,
please <a href="http://nagoya.apache.org/bugzilla/query.cgi">check the
+database</a> and the <a href="HISTORY">project history file</a> to see
+if the problem is not already known. After this verification step, you
+are highly encouraged to send email to the <em>log4j-user</em>
+mailing list (see below) describing the bug. Only after these
+precautionary steps should you file a bug report.</p>
</blockquote>
</p>
</td></tr>
@@ -147,17 +150,40 @@
The traffic on this list is extremely low and you are encouraged to
subscribe to this list if you are using log4j.</p>
<p>Discussion on log4j and logging
in general are held on the
-<em>log4j-user</em> mailing list. This list is <a
href="http://marc.theaimsgroup.com/?l=log4j-user&r=1&w=2">archived</a>.
-To post a message to all its members, send e-mail to <A
HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>.
-To subscribe to the log4j-users list send an e-mail to <A
HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>.</p>
- <p>Development related discussions
are held on the <em>log4j-dev</em> mailing
-list. This list is <a
href="http://marc.theaimsgroup.com/?l=log4j-dev&r=1&w=2">archived</a>. To post
a message to all its members,
-send e-mail to <A
HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>. To
subscribe to the log4j-dev list send an e-mail to <A
HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>.</p>
+<em>log4j-user</em> mailing list. To subscribe to
+this list send an e-mail to <A
HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>.</p>
+ <p>Development related discussions
are held on the <em>log4j-dev</em>
+mailing list. To subscribe to this list send an e-mail to <A
HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>.</p>
<p>All developers are encouraged to
subscribe to the
-<em>log4j-cvs</em> list which will notify you of CVS commits to the
-repository. This list is <a
href="http://marc.theaimsgroup.com/?l=log4j-cvs&r=1&w=2">archived</a>.
-To post a message to all its members, send e-mail to <A
HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>. To
-subscribe to the log4j-cvs list send an e-mail to <A
HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>.</p>
+<em>log4j-cvs</em> list which will notify the subscribers of CVS any
+commits to the repository. To subscribe to this list send an e-mail
+to <A
HREF="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</A>.
+Committers <em>must</em> subscribe to this with their Apache mail
+address.</p>
+ <p><b>To prevent spam, we expect
you to be subscribed to a list before
+posting to it. Otherwise, your mail needs to be approved by an
+administrator which delays your posting and creates needless work for us.</b></p>
+ <p>Most Jakarta mailing lists, in
particular the log4j mailing lists,
+are archived. Some of the known archives are listed below:</p>
+ <ul>
+
+<li>
+<a href="http://www.mail-archive.com/">http://www.mail-archive.com</a>
+</li>
+
+<li>Full mbox archives of all Jakarta lists are available at <a
href="http://jakarta.apache.org/mail/">http://jakarta.apache.org/mail/</a>
+</li>
+
+<li>
+<a href="http://marc.theaimsgroup.com">http://marc.theaimsgroup.com</a>
+</li>
+
+</ul>
+ <p>Please do your best to ensure
that you are not sending HTML or
+"Stylelized" email to the list. If you are using Outlook or Outlook
+Express or Eudora, chances are that you are sending HTML email by
+default. There is usually a setting that will allow you to send "Plain
+Text" email. </p>
</blockquote>
</p>
</td></tr>
1.19 +42 -22 jakarta-log4j/docs/critique.html
Index: critique.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/critique.html,v
retrieving revision 1.18
retrieving revision 1.19
diff -u -r1.18 -r1.19
--- critique.html 2001/07/05 16:54:33 1.18
+++ critique.html 2001/07/30 20:32:09 1.19
@@ -391,7 +391,7 @@
<li><p><a href="pub-support/PaulMichaelReilly.html">Paul Michael Reilly</a> <!-- -->
<li><p><a href="pub-support/MarcusAhnve.html">Marcus Ahnve</a> <!-- -->
<li><p><a href="pub-support/DavidDuddleston.html">David Duddleston</a> <!-- -->
-<li><p><a href="pub-support/BrianPaulsen.html">Brian Paulsen</a>
+<li><p><a href="pub-support/BrianPaulsen.html">Brian Paulsen</a> <!-- -->
<li><p><a href="pub-support/AlexFernandez.html">Alex Fern�ndez</a> <!-- -->
<li><p><a href="pub-support/DanielStephan.html">Daniel Stephan</a> <!-- -->
<li><p><a href="pub-support/AlexanderEvsukov.html">Alexander Evsukov</a> <!-- -->
@@ -485,21 +485,43 @@
<li><p><a href="pub-support/KenJarrad.html">Ken Jarrad</a>
<li><p><a href="pub-support/ErikBergersjo.html">ErikBergersjö</a>
<li><p><a href="pub-support/CamilleTroillard.html">Camille Troillard</a> <!-- -->
-<li><p><a href="pub-support/MarcelHeemskerk.html">Marcel Heemskerk</a>
-<li><p><a href="pub-support/BHA.html">BHA</a>
+<li><p><a href="pub-support/MarcelHeemskerk.html">Marcel Heemskerk</a> <!-- -->
+<li><p><a href="pub-support/DanRollo.html">Dan Rollo</a> <!-- -->
<li><p><a href="pub-support/JeffreyMadynski.html">Jeffrey Madynski</a> <!-- -->
-<li><p><a href="pub-support/EigilHysvaer.html">Eigil Hysvaer</a>
+<li><p><a href="pub-support/EigilHysvaer.html">Eigil Hysvaer</a> <!-- -->
<li><p><a href="pub-support/Msew.html">Msew</a> <!-- -->
-<li><p><a href="pub-support/MiguelLaiz.html">Miguel Laiz</a>
+<li><p><a href="pub-support/MiguelLaiz.html">Miguel Laiz</a> <!-- -->
<li><p><a href="pub-support/ColinSampaleanu.html">Colin Sampaleanu</a> <!-- -->
+<li><p><a href="pub-support/RobGiardina.html">Rob Giardina</a> <!-- -->
+<li><p><a href="pub-support/VeerappanSaravanan.html">Veerappan Saravanan</a> <!--
-->
+<li><p><a href="pub-support/NathanBrown.html">Nathan Brown</a> <!-- -->
+<li><p><a href="pub-support/LarryKim.html">Larry Kim</a> <!-- -->
+<li><p><a href="pub-support/SimonEvans.html">Simon Evans</a> <!-- -->
+<li><p><a href="pub-support/CharlesStanton.html">Charles W. Stanton</a> <!-- -->
+<li><p><a href="pub-support/WillSargent.html">Will Sargent</a> <!-- -->
+<li><p><a href="pub-support/AndrewLovell.html">Andrew Lovell</a> <!-- -->
+<li><p><a href="pub-support/RickRoss.html">Rick Ross</a> <!-- -->
+<li><p><a href="pub-support/ChristianGustafson.html">Christian Gustafson</a> <!--
-->
+<li><p><a href="pub-support/DougOlender.html">Doug Olender</a> <!-- -->
+<li><p><a href="pub-support/ColinGibson.html">Colin Gibson</a> <!-- -->
+<li><p><a href="pub-support/BearBibeault.html">Bear Bibeault</a> <!-- -->
+<li><p><a href="pub-support/RobertChartier.html">Robert Chartier</a> <!-- -->
+<li><p><a href="pub-support/JeroenHabets.html">Jeroen Habets</a> <!-- -->
+<li><p><a href="pub-support/MarkSchenk.html">Mark Schenk</a> <!-- -->
+<li><p><a href="pub-support/JohanS�rlin.html">Johan S�rlin</a> <!-- -->
+<li><p><a href="pub-support/MichaelWaddell.html">Michael Waddell</a> <!-- -->
+<li><p><a href="pub-support/neth6.html">neth6</a> <!-- -->
+<li><p><a href="pub-support/antuan.html">Antuan</a>
+<li><p><a href="pub-support/PaulSorenson.html">Paul Sorenson</a> <!-- -->
+<li><p><a href="pub-support/OliverKamps.html">Oliver Kamps</a> <!-- -->
+<li><p><a href="pub-support/JohnAdams.html">John Adams</a> <!-- -->
+<li><p><a href="pub-support/CarsonGross.html">Carson Gross</a> <!-- -->
+<li><p><a href="pub-support/AndreVanDelft.html">Andre Van Delft</a> <!-- -->
+<li><p><a href="pub-support/JasonHenriksen.html">Jason Henriksen</a>
+<li><p><a href="pub-support/AlexanderStaubo.html">Alexander Staubo</a> <!-- -->
+<li><p><a href="pub-support/StephanieBlair.html">Stephanie Blair</a> <!-- -->
<!--
-
-
-<li><p><a href="pub-support/.html"></a>
-<li><p><a href="pub-support/.html"></a>
-<li><p><a href="pub-support/.html"></a>
-<li><p><a href="pub-support/.html"></a>
-->
@@ -526,16 +548,14 @@
<p>Unfortunately, given the uproar that this API is causing, it is
becoming increasingly clear that the resulting API is unlikely to meet
a wide set of requirements. The apparent failure of JSR47 API is also
-casting a shadow on the nature of the Java Community Process. <a
-href="http://www.zdnet.com/eweek/stories/general/0,11011,2666270,00.html">Michael
-C. Daconta</a> has some interesting comments on the JCP. All said and
-done, Java remains a wonderful 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>Given the volume and the quality of support we are receiving from
-the community, I would not be surprised to see the JSR47 API retracted
-or replaced wholesale by log4j.
+casting a shadow on the nature of the Java Community Process. Michael
+C. Daconta has some interesting <a
+href="http://www.zdnet.com/eweek/stories/general/0,11011,2666270,00.html">
+comments</a> on the JCP. All said and done, Java remains a wonderful
+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>
</body> </HTML>
1.32 +3 -9 jakarta-log4j/docs/download.html
Index: download.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/download.html,v
retrieving revision 1.31
retrieving revision 1.32
diff -u -r1.31 -r1.32
--- download.html 2001/07/04 21:14:27 1.31
+++ download.html 2001/07/30 20:32:09 1.32
@@ -122,11 +122,7 @@
<tr><td><br/></td></tr>
<tr><td>
<blockquote>
- <hr />
- <h3>Join our <a
href="critique.html">effort</a> to influence the JSR47 API.
-</h3>
- <hr />
- <p>Download version 1.1.3 including
<i>full source code</i>, class files
+ <p>Download version 1.1.3 including <i>full
source code</i>, class files
and documentation in
<a href="../jakarta-log4j-1.1.3.tar.gz"><b>TAR.GZ</b></a> format or in
<a href="../jakarta-log4j-1.1.3.zip"><b>ZIP</b></a> format. You may
@@ -173,10 +169,8 @@
<dt><a href="http://jakarta.apache.org/taglibs/doc/log-doc/intro.html">
<b>Log Tag</b></a>
</dt>
- <dd>A custom log tag from the <a
href="http://jakarta.apache.org/taglibs/index.html">Jakarta Taglibs</a> project.</dd>
-
- <dt><a href="http://www.adjacency.org/logtags.jsp"><b>The Log Tag
Library</b></a></dt>
- <dd>Yet another tag library designed to give JSP tag-level access to log4j.</dd>
+ <dd>A custom log tag library from the <a
href="http://jakarta.apache.org/taglibs/index.html">Jakarta
+ Taglibs</a> project.</dd>
<dt><a href="http://www.japhy.de/configLog4j"><b>configLog4j</b></a></dt>
<dd>A visual log4j configuration file editor by Tobias Dezulian.</dd>
1.13 +1 -5 jakarta-log4j/docs/index.html
Index: index.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/index.html,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- index.html 2001/07/03 09:24:27 1.12
+++ index.html 2001/07/30 20:32:09 1.13
@@ -122,11 +122,7 @@
<tr><td><br/></td></tr>
<tr><td>
<blockquote>
- <hr />
- <h3>Join our <a
href="critique.html">effort</a> to influence the JSR47 API.
-</h3>
- <hr />
- <p>Inserting log statements into
your code is a low-tech method for
+ <p>Inserting log statements into your code is a
low-tech method for
debugging it. It may also be the only way because debuggers are not
always available or applicable. This is often the case for
distributed applications.</p>
1.24 +21 -5 jakarta-log4j/docs/manual.html
Index: manual.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/manual.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -r1.23 -r1.24
--- manual.html 2001/07/26 22:17:10 1.23
+++ manual.html 2001/07/30 20:32:09 1.24
@@ -799,8 +799,10 @@
static inializer of the <code>Category</code> class will attempt to
automatically configure log4j. The Java language guarantees that the
static initializer of a class is called once and only once during the
-loading of a class into memory. (Although different classloaders may
-load distinct copies of the same class.)
+loading of a class into memory. It is important to remember that
+different classloaders may load distinct copies of the same
+class. These copies of the same class are considered as totally
+unrelated by the JVM.
<p>The default initialization is very useful in environments where the
exact entry point to the application depends on the runtime
@@ -871,6 +873,10 @@
will be used to parse the URL.
</ol>
+<h2>Example Configurations</h2>
+
+
+
<h2>Default Initialization under Tomcat</h2>
<p>The default log4j initialization is particularly useful in
@@ -945,8 +951,18 @@
tells log4j to use the file <code>c:\foobar.xml</code> as the default
configuration file. The configuration file is fully specified by the
URL <code>file:/c:/foobar.lcf</code>. Thus, the same configuration
-file will be used for all web-applications -- in other words, disaster
-waiting to happen.
+file will be used for all web-applications.
+
+
+<p>Different web-applications will load the log4j classes through
+their respective classloaderss. Thus, each image of the log4j
+environment will act independetly and without any mutual
+synchronization. For example, <code>FileAppenders</code> defined
+exactly the same way in multiple web-application configurations will
+all attempt to write the same file. The results are likely to be less
+than satisfactory. You must make sure that log4j configurations of
+different web-applications do not use the same underlying system
+resource.
<p><b>Initialization servlet</b>
@@ -954,7 +970,7 @@
<p>It is also possible to use a special servlet for log4j
initialization. Here is an example,
-<table bgcolor="CCCCCC"><tr><td>
+<p><table bgcolor="CCCCCC"><tr><td>
<pre>
package com.foo;
1.3 +12 -12 jakarta-log4j/docs/plan.html
Index: plan.html
===================================================================
RCS file: /home/cvs/jakarta-log4j/docs/plan.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- plan.html 2001/06/21 05:19:44 1.2
+++ plan.html 2001/07/30 20:32:09 1.3
@@ -36,21 +36,14 @@
</TR>
-<TR>
-<TD>JMX support
+
+<TR >
+<TD>Removal of deprecated methods
-<TD>A common request is to change log4j settings without shutting down
-a running application. The JMX API is designed to handle such
-management tasks.
-
-<p>For example, a <code>HierarchyAgent</code> could list all existing
-categories in a hierarchy, create new categories, change the priority
-or attach a new appender to a category. Log4j core needs to be
-enhanced to report events such as the creation of a new categories,
-priority changes, appender attachments/removals etc.
+<TD>Deprecated <code>setOption</code> and <code>getOption</code>
+method should be removed.
<TD>TBD
-</TR>
<TR bgcolor="DDDDDD">
<TD>JDBCAppender
@@ -110,6 +103,13 @@
application either.
<TD>C. Gülcü
+
+
+<TR bgcolor="DDDDDD">
+<TD>Enhanced variable substitution support in DOMConfigurator
+<TD>
+<TD>TBD
+
</TABLE>
1.9 +6 -1 jakarta-log4j/src/xdocs/contactUs.xml
Index: contactUs.xml
===================================================================
RCS file: /home/cvs/jakarta-log4j/src/xdocs/contactUs.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- contactUs.xml 2001/07/13 07:49:39 1.8
+++ contactUs.xml 2001/07/30 20:32:09 1.9
@@ -70,11 +70,16 @@
<a href="http://marc.theaimsgroup.com">http://marc.theaimsgroup.com</a>
</li>
+</ul>
+<p>Please do your best to ensure that you are not sending HTML or
+"Stylelized" email to the list. If you are using Outlook or Outlook
+Express or Eudora, chances are that you are sending HTML email by
+default. There is usually a setting that will allow you to send "Plain
+Text" email. </p>
-</ul>
</section>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]