logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From psm...@apache.org
Subject cvs commit: jakarta-log4j/src/java/org/apache/log4j/chainsaw WelcomePanel.html
Date Mon, 22 Sep 2003 07:00:45 GMT
psmith      2003/09/22 00:00:45

  Modified:    src/java/org/apache/log4j/chainsaw WelcomePanel.html
  Small tweaks, plus removal of some blocks of docs that
  will be located elsewhere.  This HTML file will be kept
  small as a Quick Reference.
  Revision  Changes    Path
  1.5       +2 -29     jakarta-log4j/src/java/org/apache/log4j/chainsaw/WelcomePanel.html
  Index: WelcomePanel.html
  RCS file: /home/cvs/jakarta-log4j/src/java/org/apache/log4j/chainsaw/WelcomePanel.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- WelcomePanel.html	3 Sep 2003 07:35:02 -0000	1.4
  +++ WelcomePanel.html	22 Sep 2003 07:00:45 -0000	1.5
  @@ -79,10 +79,10 @@
   <p>Log4j has a concept of a 'Receiver', an object that receives events
   from some source, and deposits them into the Log4j framework in the local JVM.  
  -It useful to think of Log4j's engine as a 'bus' much like the PCI bus in a computer,
  +It is useful to think of Log4j's engine as a 'bus' much like the PCI bus in a computer,
   with events being the data placed on the bus.</p>
  -<p>Since Chainsaw acts just like a Log4j Appender, using a Receiver allows\
  +<p>Chainsaw integrates itself with Log4j using this Receiver concept, allowing
   you to receive events from, say, a remote location, and view them within the
   Chainsaw GUI.</p>
  @@ -92,32 +92,5 @@
   places it in the local Log4j bus.  A Receiver can be a 'sink' for event
   data, while the Appender is the 'source'.
  -<a name="UsefulConfigs"></a>
  -<h2>Useful Configuration</h2>
  -<p>We'll discuss a very useful and common configuration.  If you have
  -an application that is using Log4j to log events, you are able to 
  -configure a series of appenders, and often this is just a simple FileAppender. 
  -An alternative is to configure a SocketAppender that transmits the event
  -to a remote location. In this case, Chainsaw becomes this remote location.
  -<p>Click <a href="http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/net/SocketAppender.html">here</a>
to learn more about <a href="http://jakarta.apache.org/log4j/docs/api/org/apache/log4j/net/SocketAppender.html">SocketAppenders</a>.</p>
  -<p>Click here to learn more about Receivers (and SocketReceiver in particular).
  -<a name="FAQ"></a>
  -<!--<p><a href="#TheTop">Back to top</a></p>-->
  -<a name="FilteringColouring"></a>
  -<h2>Filtering and Colouring</h2>
  -<p>Chainsaw enables you to configure filters that suppress the display of certain
logging events, and also highlight the event with a colo(u)r of your choosing.</p>
  -<p><a href="#TheTop">Back to top</a></p>
  -<h2>Examples of Filtering and Colouring</h2>
  -This example will show you how to:
  -<li>Colo(ur) all Error level logging Red, Warn level Yellow, and Info level grey</li>
  -<li>Suppress all levels but INFO/WARN/ERROR</li>
  -<!--<p><a href="#TheTop">Back to top</a></p>-->

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

View raw message