psmith 2004/04/07 18:47:45
Modified: src/xdocs plan.xml
Log:
Removed "1.2 plan" section... We're in 1.2 maintenance mode.
Modified and added as much as I could think off in an attempt to reflect where we're
at, but I may not be 100% accurate here, please feel free to change this.
Note: I will not update the website until everyone is happy.
Revision Changes Path
1.9 +43 -186 logging-log4j/src/xdocs/plan.xml
Index: plan.xml
===================================================================
RCS file: /home/cvs/logging-log4j/src/xdocs/plan.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- plan.xml 9 Oct 2002 22:50:07 -0000 1.8
+++ plan.xml 8 Apr 2004 01:47:44 -0000 1.9
@@ -63,8 +63,8 @@
as early is possible. It is strongly recommended to add
a new test case with each new feature or component.</p>
- <p>Existing <em>Perl</em> language based test cases are
- gradually being migrated to junit (all-Java)based test
+ <p>Existing <em>Perl</em> language based test cases have been
+ migrated to junit (all-Java)based test
cases. The new tests are placed under the
<code>tests/</code> directory. It should be thus
possible for participants in the project to understand
@@ -91,14 +91,13 @@
are configured separately.
</p>
- <p>The support for extensible configuration files will be
- based on the code in commons-digester authored by Craig
- McClanahan and Scott Sanders. They graciously granted
- permission for the modification of their code and its
- inclusion in log4j.</p>
+ <p>The new JoranConfigurator being created by Ceki will be based on
+ a new 'module' know as Joran, which can convert XML files into other
objects based
+ on rules. You can read more abouth Joran <b><u><a
href="http://www.qos.ch/logging/JoranConfigurator.html";>here</a></u></b>
+ </p>
</td>
<td>Ceki</td>
- <td>design board</td>
+ <td>Significantly progressed</td>
</tr>
<tr>
@@ -133,20 +132,35 @@
<td>?</td>
<td>vaporware</td>
</tr>
+ <tr>
+ <td>Plugins/Receivers</td>
+
+ <td>
+ <p>A Plugin framework has been designed and implemented.</p>
+ <p>All of the currently developed plugins are "Receivers", which can be
thought of as the reverse of an appender; something
+ that <b>accepts</b> LoggingEvents from some external source.
+ </p>
+ <p>This has proven particulaly useful with the log4j ports, with the
addition of the XML-based Receivers able to accept
+ LoggingEvents generated from other languages (see "Overture to other
programming languages" below)
+ </p>
+
+ </td>
+ <td>All</td>
+ <td>Significantly progressed</td>
+ </tr>
<tr>
<td>Improvements to Chainsaw</td>
<td>
- <p>Visualisation and dynamic filtering of logging event is
- bound to be a very important area of activity in the
- future. A number of important improvements to chainsaw
- have been suggested.
+ <p><a href="chainsaw.html">Chainsaw v2</a> development has now progressed
to the point where the main developers of it
+ and many other members of the logging community are using it daily. It's
still pre-alpha but only
+ because we keep thinking up things to add.
</p>
</td>
- <td>Oliver Burn</td>
- <td>under discusison</td>
+ <td>Scott Deboy and Paul Smith</td>
+ <td>Significantly progressed </td>
</tr>
<tr>
@@ -157,19 +171,24 @@
extensions to XML configuration language mentioned
above.</td>
- <td>?</td>
- <td>not started</td>
+ <td>Ceki</td>
+ <td>Completed, still testing</td>
</tr>
<tr>
<td>Overture to other programming languages</td>
- <td>It is higly desriable to allow log4j ports in other languages
- to access log4j services in a language independent way.
- </td>
+ <td><p>It is higly desriable to allow log4j ports in other languages
+ to access log4j services in a language independent way. </p>
+
+ <p>The use of a standard XML format to represent a LoggingEvent has been
established and many of the related logging projects from
+ non-Java languages have begun to support it. In fact, a number of the
log4j ports have volunteered to join Apache!</p>
+
+ <p>Scott Deboy has completed work to create a fex XML-based Receiver
+ classes that can accept logging events from an external source, and 'import'
them into the local log4j environment. </p> </td>
- <td>?</td>
- <td>not started</td>
+ <td>Ceki, Scott Deboy</td>
+ <td>Significantly Progressed (if not completed)</td>
</tr>
<tr>
@@ -189,8 +208,8 @@
scripts.
</p>
</td>
- <td>Kevin Steppe</td>
- <td>not started</td>
+ <td>Ceki</td>
+ <td>Significantly Progressed</td>
</tr>
@@ -232,169 +251,7 @@
</tr>
</table>
</section>
-
-
-
- <section name="Workplan for log4j 1.2">
- <p>
- Here is workplan for the 1.2 release.
- </p>
-
- <table border="1" cellpadding="3" cellspacing="2">
-
- <tr>
- <th>Label</th>
- <th>Comment</th>
- <th>Volunteer</th>
- <th>Status</th>
- </tr>
-
- <tr bgcolor="DDDDDD">
- <td>More test cases</td>
-
- <td>We need more automated test cases to catch bugs as early
- is possible.It is highly recommended to add a new test case
- with each new feature or component.</td>
-
- <td>All committers</td>
- <td>ongoing effort</td>
- </tr>
-
-
- <tr>
- <td>Removal of deprecated methods</td>
-
- <td>Deprecated <code>setOption</code> and <code>getOption</code>
- methods in appender and layouts should be removed.</td>
-
- <td>Ceki</td>
- <td>done</td>
- </tr>
-
- <tr bgcolor="DDDDDD">
- <td>JDBCAppender</td>
-
- <td>
- <p>We currently have two competing JDBCAppenders: one by
- Thomas Fenner and the other by Kevin Steppe.</p>
-
- <p>Kevin Steppe stood up and did it.</p>
- </td>
-
- <td>Kevin Steppe</td>
-
- <td>done</td>
- </tr>
-
- <tr>
- <td>Log4j in applets</td>
-
- <td>In order to minimize network traffic, the size of log4j-core.jar
- needs to be reduced to at most 50KB.
-
- <p>Log4jME has been released. It's less than 20KB.</p>
- </td>
-
- <td>Ceki</td>
- <td>done</td>
- </tr>
-
- <tr bgcolor="DDDDDD">
- <td>Improved documentation</td>
-
- <td>Log4j documentation needs to be enhanced with configuration
- examples and much more hand-holding.</td>
-
- <td>Ceki</td>
-
- <td>ongoing effort</td>
-
- </tr>
-
- <tr>
- <td valign="top">Mapped Diagnostic Contexts</td>
-
- <td>Mapped Diagnostic Contexts are similar to the NDC
- except that the MDC is a string to string map instead of
- a stack that the user sets when entering a special
- context. The <code>PatternLayout</code> has to be
- enhanced to support this by extending the %x pattern to
- accept an argument. Here is an example:
-
- <pre>
- ConversionPattern=3D%d %p %c %x{server} %x{host} - %m%n
- </pre>
-
- User code:
- <pre>
- {
- MDC.put("server", "totoServer");
- MDC.put("host", "someHost");
-
- logger.debug("Hello");
-
- }
-</pre>
- will print:
- <pre>2000-01-24 10:00:00,000 DEBUG totoServer someHost - Hello</pre>
-
- <p>To make MDCs truly user friendly
- <code>ThreadLocal</code> variables are required. This
- will allow the MDC to be inherited by child
- threads. <code>ThreadLocal</code> are only supported
- under JDK 1.2 and above. In JDK 1.1, the MDC will not
- work but won't harm the user application either.</p>
- </td>
- <td>Ceki</td>
- <td>done</td>
- </tr>
-
- <tr bgcolor="DDDDDD">
- <td>Enhanced variable substitution support in DOMConfigurator</td>
- <td></td>
-
- <td>Ceki</td>
- <td>done</td>
- </tr>
-
- <tr>
- <td>FallbackErrorHandler</td>
-
- <td>The FallbackErrorHandler implements the ErrorHandler
- interface such that a secondary appender may be
- specified. This secondary appender takes over if the primary
- appender fails for whatever reason.
-
- <p>The DOMConfigurator needs to be extended to support the
- FallbackErrorHandler</p>
-
- </td>
- <td>Ceki</td>
- <td>implemented, requires further testing</td>
- </tr>
-
-
- <tr>
- <td>Ensure backward compatibility of LoggingEvent
- objects</td>
-
- <td>To avoid deployment problems we must ensure that
- LoggingEvent objects are compatible between 1.2 and 1.1.3.
-
- <p>Robert Bushman has proposed a very innovative way for
- solving this problem. See <a
- href="http://www.mail-archive.com/[EMAIL PROTECTED]/msg01397.html">
- http://www.mail-archive.com/[EMAIL PROTECTED]/msg01397.html</a>
- for further details.
- </p>
- </td>
-
- <td>Ceki</td>
- <td>implemented, manually tested, requires automated test cases</td>
- </tr>
- </table>
- </section>
-
+
</body>
</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
