Author: ceki Date: Tue Nov 11 16:13:01 2008 New Revision: 1960 Modified: logback/trunk/logback-site/src/site/pages/access.html logback/trunk/logback-site/src/site/pages/bugreport.html logback/trunk/logback-site/src/site/pages/consolePlugin.html logback/trunk/logback-site/src/site/pages/css/common.css logback/trunk/logback-site/src/site/pages/demo.html logback/trunk/logback-site/src/site/pages/dependencies.html logback/trunk/logback-site/src/site/pages/documentation.html logback/trunk/logback-site/src/site/pages/faq.html logback/trunk/logback-site/src/site/pages/index.html logback/trunk/logback-site/src/site/pages/joran.html logback/trunk/logback-site/src/site/pages/license.html logback/trunk/logback-site/src/site/pages/mailinglist.html logback/trunk/logback-site/src/site/pages/manual/appenders.html logback/trunk/logback-site/src/site/pages/manual/architecture.html logback/trunk/logback-site/src/site/pages/manual/contextSelector.html logback/trunk/logback-site/src/site/pages/manual/filters.html logback/trunk/logback-site/src/site/pages/manual/index.html logback/trunk/logback-site/src/site/pages/manual/introduction.html logback/trunk/logback-site/src/site/pages/manual/jmxConfig.html logback/trunk/logback-site/src/site/pages/manual/joran.html logback/trunk/logback-site/src/site/pages/manual/layouts.html logback/trunk/logback-site/src/site/pages/manual/mdc.html logback/trunk/logback-site/src/site/pages/news.html logback/trunk/logback-site/src/site/pages/repos.html logback/trunk/logback-site/src/site/pages/support.html logback/trunk/logback-site/src/site/pages/team.html Log: ensure that html documents are valid XHTML Modified: logback/trunk/logback-site/src/site/pages/access.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/access.html (original) +++ logback/trunk/logback-site/src/site/pages/access.html Tue Nov 11 16:13:01 2008 @@ -1,28 +1,32 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Logback Access</title> -<link rel="stylesheet" type="text/css" media="screen" href="css/site.css" /> -</head> -<body> - <script> -prefix=''; -</script> - -<script src="templates/header.js"></script> -<div id="left"> - <script src="templates/left.js"></script> -</div> -<div id="content"> + <head> + <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> + <title>Logback Access</title> + <link rel="stylesheet" type="text/css" href="css/common.css" /> + <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" /> + <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" /> + + </head> + <body> + <script type="text/javascript">prefix='';</script> + + <script src="templates/header.js" type="text/javascript"></script> + <div id="left"> + <script src="templates/left.js" type="text/javascript"></script> + </div> + <div id="content"> - <h2>Access log with logback, Jetty and Tomcat</h2> - <div class="author"> + <h2>Access log with logback, Jetty and Tomcat</h2> + + <div class="author"> Authors: Ceki Gülcü, Sébastien Pennec </div> - <script src="../templates/creative.js"></script> + <script src="../templates/creative.js" type="text/javascript"></script> <h1>Introduction</h1> @@ -460,7 +464,8 @@ <p>Here is a sample logback-access.xml configuration file which will output the full contents of the request and response on the console. </p> -<div class="source"><configuration> + + <p class="source"><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.access.PatternLayout"> <Pattern>%fullRequest%n%n%fullResponse</Pattern> @@ -468,14 +473,12 @@ </appender> <appender-ref ref="STDOUT" /> -</configuration> -</div> +</configuration></p> -<p>Few clicks accessing the <a href="demo.html">logback-demo</a> -application configured as outlined above, yeilds: -</p> + <p>Few clicks accessing the <a href="demo.html">logback-demo</a> + application configured as outlined above, yeilds:</p> -<div class="source"><b>GET /logback-demo/index.jsp HTTP/1.1</b> + <p class="source"><b>GET /logback-demo/index.jsp HTTP/1.1</b> Host: localhost:8080 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.11) Gecko/20070312 Firefox/1.5.0.11 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 @@ -503,13 +506,13 @@ <h2>Logback demo center</h2> -[snip, so that text is reasonably sized]</div> +[snip, so that text is reasonably sized]</p> -<p> </p> + <p> </p> -</div> -<script src="templates/footer.js"></script> + <script src="templates/footer.js" type="text/javascript"></script> +</div> </body> </html> Modified: logback/trunk/logback-site/src/site/pages/bugreport.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/bugreport.html (original) +++ logback/trunk/logback-site/src/site/pages/bugreport.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,5 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/consolePlugin.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/consolePlugin.html (original) +++ logback/trunk/logback-site/src/site/pages/consolePlugin.html Tue Nov 11 16:13:01 2008 @@ -1,22 +1,24 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Logback Console Plugin for Eclipse</title> -<link rel="stylesheet" type="text/css" media="screen" href="css/site.css" /> -<link rel="stylesheet" type="text/css" media="print" href="css/print.css" /> - -</head> -<body> - <script> -prefix=''; -</script> - -<script src="templates/header.js"></script> -<div id="left"> - <script src="templates/left.js"></script> -</div> -<div id="content"> + <head> + <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> + <title>Logback Console Plugin for Eclipse</title> + <link rel="stylesheet" type="text/css" href="css/common.css" /> + <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" /> + <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" /> + + + </head> + <body> + <script type="text/javascript">prefix='';</script> + + <script src="templates/header.js" type="text/javascript"></script> + <div id="left"> + <script src="templates/left.js" type="text/javascript"></script> + </div> + <div id="content"> <h2>Logback Console Plugin for Eclipse</h2> @@ -121,7 +123,7 @@ You should see two buttons, along with the usual three Eclipse icons: </p> - <img src="images/plugin/buttons.gif" /> + <img src="images/plugin/buttons.gif" alt="buttons.gif"/> <p> The first button on the left clears the console. The second button toggles @@ -141,7 +143,7 @@ below: </p> - <img src="images/plugin/sampleLogs.gif" /> + <img src="images/plugin/sampleLogs.gif" alt="sampleLogs.gif"/> <p> All events with the <em>WARN</em> level are displayed in orange. <em>ERROR</em> @@ -162,7 +164,7 @@ an editor revealing the selected class. </p> - <img src="images/plugin/stackTrace.gif" /> + <img src="images/plugin/stackTrace.gif" alt="stackTrace.gif"/> <h3>Configuring the logback plugin</h3> @@ -177,7 +179,7 @@ The first item in this menu opens the plugin's preference window. </p> - <img src="images/plugin/prefs.gif" /> + <img src="images/plugin/prefs.gif" alt="prefs.gif" /> <p> In this window, you can configure the pattern that will be used by the plugin @@ -203,12 +205,12 @@ </li> </ul> - <p> - An important point about this pattern is that, if it is modified, the changes - are immediately reflected on the <strong>current content</strong> of the logback view. - That means that if you would like to display an <code>MDC</code> value, or any other - information that the <code>PatternLayout</code> provides, you can change it even - <em>after</em> the logs have been requested. + <p>An important point about this pattern is that, if it is + modified, the changes are immediately reflected on the + <strong>current content</strong> of the logback view. That means + that if you would like to display an <code>MDC</code> value, or any + other information that the <code>PatternLayout</code> provides, you + can change it even <em>after</em> the logs have been requested. </p> <p> @@ -243,7 +245,7 @@ opens the filter configuration window: </p> - <img src="images/plugin/filterWindow.gif" /> + <img src="images/plugin/filterWindow.gif" alt="filterWindow.gif"/> <p> The upper part of the window lists the filters that are currently @@ -294,7 +296,7 @@ saved the filter. </p> - <img src="images/plugin/createFilter.gif" /> + <img src="images/plugin/createFilter.gif" alt="createFilter.gif" /> <p> We've just created a filter that will drop any requests whose @@ -321,7 +323,7 @@ </p> -<script src="templates/footer.js"></script> + <script src="templates/footer.js" type="text/javascript"></script> </div> </body> </html> Modified: logback/trunk/logback-site/src/site/pages/css/common.css ============================================================================== --- logback/trunk/logback-site/src/site/pages/css/common.css (original) +++ logback/trunk/logback-site/src/site/pages/css/common.css Tue Nov 11 16:13:01 2008 @@ -22,7 +22,7 @@ border-top: 1px solid #DDDDDD; border-bottom: 1px solid #DDDDDD; background:#eee; - font-family: Courier, "MS Courier New", Prestige, Everson Monocourrier, monospace; + font-family: Courier, "MS Courier New", Prestige, monospace; padding-bottom: 0.5ex; padding-top: 0.5ex; padding-left: 1ex; @@ -33,7 +33,7 @@ border-top: 1px solid #DDDDDD; border-bottom: 1px solid #DDDDDD; background:#eee; - font-family: Courier, "MS Courier New", Prestige, Everson Monocourrier, monospace; + font-family: Courier, "MS Courier New", Prestige, monospace; padding-bottom: 0ex; padding-top: 0ex; padding-left: 1ex; @@ -61,18 +61,18 @@ } h2 { - font-weight: 900; - font-size: x-large; + font-weight: 900; + font-size: x-large; } h3 { - font-weight: normal; - font-size: large; + font-weight: normal; + font-size: large; } h4 { - font-weight: large; - font-size: normal; + font-weight: bold; + font-size: medium; } .footer { @@ -209,7 +209,7 @@ } .quote { - align: right; + text-align: right; padding-left: 12em; } Modified: logback/trunk/logback-site/src/site/pages/demo.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/demo.html (original) +++ logback/trunk/logback-site/src/site/pages/demo.html Tue Nov 11 16:13:01 2008 @@ -1,36 +1,38 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Logback Demo</title> -<link rel="stylesheet" type="text/css" media="screen" href="css/site.css" /> -</head> -<body> - <script> -prefix=''; -</script> - -<script src="templates/header.js"></script> -<div id="left"> - <script src="templates/left.js"></script> -</div> -<div id="content"> + <head> + <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> + <title>Logback Demo</title> + <link rel="stylesheet" type="text/css" href="css/common.css" /> + <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" /> + <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" /> + </head> + <body> + <script type="text/javascript">prefix=''; </script> + + <script src="templates/header.js" type="text/javascript"></script> + <div id="left"> + <script src="templates/left.js" type="text/javascript"></script> + </div> + <div id="content"> + - - <h2>Logback Demo</h2> + <h2>Logback Demo</h2> - <p>Welcome to the logback demo! This document will take you through - a tour of some of logback's major features. - </p> - - <h3>Installation</h3> + <p>Welcome to the logback demo! This document will take you through + a tour of some of logback's major features. + </p> + + <h3>Installation</h3> - <p> First, please download the logback demo. You will need to install a - <a href="http://subversion.tigris.org/">Subversion</a> client and - issue the following command on a console: - </p> + <p> First, please download the logback demo. You will need to + install a <a href="http://subversion.tigris.org/">Subversion</a> + client and issue the following command on a console: + </p> - <div class="source"><pre>svn co http://svn.qos.ch/repos/logback-demo/tags/STABLE logback-demo</pre></div> + <p class="source">svn co http://svn.qos.ch/repos/logback-demo/tags/STABLE logback-demo</p> <p>This will checkout a copy of the logback demonstration web-application to a directory called <em>logback-demo</em>. The @@ -553,7 +555,7 @@ page</a> for more information about any component you'd like to test. </p> -<script src="templates/footer.js"></script> +<script src="templates/footer.js" type="text/javascript"></script> </div> </body> </html> Modified: logback/trunk/logback-site/src/site/pages/dependencies.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/dependencies.html (original) +++ logback/trunk/logback-site/src/site/pages/dependencies.html Tue Nov 11 16:13:01 2008 @@ -1,20 +1,23 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Logback Dependencies</title> -<link rel="stylesheet" type="text/css" media="screen" href="css/site.css" /> -</head> -<body> -<script> - prefix=''; -</script> - -<script src="templates/header.js"></script> -<div id="left"> - <script src="templates/left.js"></script> -</div> -<div id="content"> + <head> + <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> + <title>Logback Dependencies</title> + + <link rel="stylesheet" type="text/css" href="css/common.css" /> + <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" /> + <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" /> + + </head> + <body> + <script type="text/javascript">prefix='';</script> + + <script src="templates/header.js" type="text/javascript"></script> + <div id="left"> + <script src="templates/left.js" type="text/javascript"></script> + </div> + <div id="content"> <h1>Dependencies per module</h1> @@ -221,7 +224,7 @@ </table> -<script src="../templates/footer.js"></script> + <script src="templates/footer.js" type="text/javascript"></script> </div> </body> </html> Modified: logback/trunk/logback-site/src/site/pages/documentation.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/documentation.html (original) +++ logback/trunk/logback-site/src/site/pages/documentation.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/faq.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/faq.html (original) +++ logback/trunk/logback-site/src/site/pages/faq.html Tue Nov 11 16:13:01 2008 @@ -1,180 +1,184 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Logback FAQ</title> -<link rel="stylesheet" type="text/css" media="screen" href="css/site.css" /> -</head> -<body> - <script> -prefix=''; -</script> - -<script src="templates/header.js"></script> -<div id="left"> - <script src="templates/left.js"></script> -</div> -<div id="content"> + <head> + <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> + <title>Logback FAQ</title> + <link rel="stylesheet" type="text/css" href="css/common.css" /> + <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" /> + <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" /> + + </head> + <body> + <script type="text/javascript">prefix='';</script> + + <script src="templates/header.js" type="text/javascript"></script> + <div id="left"> + <script src="templates/left.js" type="text/javascript"></script> + </div> + <div id="content"> - <h2> - <a name="top">Frequently Asked Questions</a> - </h2> - - <h3>Logback project</h3> - - <ol type="1"> - <li><a href="#why_lgpl">Why is logback distributed under LGPL and - not the Apache Software License?</a> - </li> - </ol> - - - <h3>Logback Classic</h3> + <h2> + <a name="top">Frequently Asked Questions</a> + </h2> + + <h3>Logback project</h3> + <ol type="1"> + <li><a href="#why_lgpl">Why is logback distributed under LGPL and + not the Apache Software License?</a> + </li> + </ol> - <ol type="1"> - <li> - <a href="#logger_serialization">Are logback loggers - serializable?</a> - </li> - - <li> - <a href="#auto_config">How does the automatic configuration - work?</a> - </li> - <li> - <a href="#setup_jetty">How can Jetty be instructed to use - logback-classic as its logging implementataion? - </a> - </li> - </ol> - - <!-- =============================================================== --> - <!-- =============================================================== --> - <!-- =============================================================== --> - <!-- =============================================================== --> - - - <div class="section"> - <h2>Logback project</h2> + + <h3>Logback Classic</h3> - <dl> - <dt> - <a name="why_lgpl" href="#why_lgpl">Why is logback distributed - under LGPL and not the Apache Software License?</a> - </dt> - - <dd> - <p>The logback project is distributed under the LGPL license - in order to emphasize the fact that it is a related but - <em>different</em> project than log4j. - </p> - - <p>Given that Java v7 will be distributed under GPL, we expect - GPL and LGPL to become even more prevalent in the Java world. - </p> - - <p>In short, LGPL is a reasonable and widely-accepted - license. Let well alone. - </p> - </dd> - </dl> - </div> - - <div class="section"> - <h2>Logback-classic</h2> - <dl> - - <!-- ========================================================= --> - - <dt> - <a name="auto_config" href="#auto_config"> - How does the automatic configuration work? - </a> - </dt> - <dd> - <p>This question is answered in the <a - href="manual/joran.html#auto_configuration">relevant - section</a> of the logback manual. - </p> - - </dd> - - <hr/> + + <ol type="1"> + <li> + <a href="#logger_serialization">Are logback loggers + serializable?</a> + </li> - <!-- ========================================================= --> + <li> + <a href="#auto_config">How does the automatic configuration + work?</a> + </li> + <li> + <a href="#setup_jetty">How can Jetty be instructed to use + logback-classic as its logging implementataion? + </a> + </li> + </ol> + + <!-- =============================================================== --> + <!-- =============================================================== --> + <!-- =============================================================== --> + <!-- =============================================================== --> + + + <div class="section"> + <h2>Logback project</h2> - + <dl> + <dt> + <a name="why_lgpl" href="#why_lgpl">Why is logback distributed + under LGPL and not the Apache Software License?</a> + </dt> + + <dd> + <p>The logback project is distributed under the LGPL license + in order to emphasize the fact that it is a related but + <em>different</em> project than log4j. + </p> + + <p>Given that Java v7 will be distributed under GPL, we expect + GPL and LGPL to become even more prevalent in the Java world. + </p> + + <p>In short, LGPL is a reasonable and widely-accepted + license. Let well alone. + </p> + </dd> + </dl> + </div> + + <div class="section"> + <h2>Logback-classic</h2> + <dl> + + <!-- ========================================================= --> + + <dt> + <a name="auto_config" href="#auto_config"> + How does the automatic configuration work? + </a> + </dt> + <dd> + <p>This question is answered in the <a + href="manual/joran.html#auto_configuration">relevant + section</a> of the logback manual. + </p> - <dt> - <a name="logger_serialization" href="#logger_serialization"> + </dd> + + <hr/> + + <!-- ========================================================= --> + + <dt> + <a name="logger_serialization" href="#logger_serialization"> Are logback loggers serializable?</a> - </dt> - <dd> - <p>Yes. A logback logger <em>is</em> an SLF4J logger and SLF4J - loggers are serializable. This means that an object - referencing a logger will be alble to log after its - deserialization. - </p> - - <p>The deserialized logger instance will be generated by - <code>org.slf4j.LoggerFactory</code>. Thus, it is possible - for a logback logger to be deserialized as a log4j or j.u.l. - logger, depending on the deserialization environment.</p> - </dd> - - <hr/> - <!-- ========================================================= --> - - <dt> - <a name="setup_jetty" href="#"> - How can Jetty be instructed to use logback-classic as its - logging implementataion? - </a> - </dt> - - <dd> - <p>The Jetty application server uses SLF4J for its internal - logging. - </p> - - <p>The following jar files must be present in the - <em>JETTY_HOME/lib</em> directory. - </p> - - <p>Logback-classic is based on the SLF4J api. Therefore, the - <em>slf4j-api-VERSION.jar</em> jar must be present. This jar - can be downloaded from the <a - href="http://www.slf4j.org/">SLF4J</a> project. - </p> - <p>Logback's own jars must also be present, namely - <em>logback-core-VERSION.jar</em> and - <em>logback-classic-VERSION.jar</em> . - </p> - - <p> To configure logback-classic, a file called - <em>logback.xml</em> should be placed in the - <em>JETTY_HOME/resources</em> directory. You can find sample - configuration files in the - <em>logback-examples/src/main/java/chapter4/conf/</em> folder - shipping within the logback distribution. - </p> + </dt> + <dd> + <p>Yes. A logback logger <em>is</em> an SLF4J logger and SLF4J + loggers are serializable. This means that an object + referencing a logger will be alble to log after its + deserialization. + </p> + + <p>The deserialized logger instance will be generated by + <code>org.slf4j.LoggerFactory</code>. Thus, it is possible + for a logback logger to be deserialized as a log4j or j.u.l. + logger, depending on the deserialization environment.</p> + </dd> - </dd> - - <hr /> - + <hr/> + <!-- ========================================================= --> + + <dt> + <a name="setup_jetty" href="#"> + How can Jetty be instructed to use logback-classic as its + logging implementataion? + </a> + </dt> + + <dd> + <p>The Jetty application server uses SLF4J for its internal + logging. + </p> + + <p>The following jar files must be present in the + <em>JETTY_HOME/lib</em> directory. + </p> + + <p>Logback-classic is based on the SLF4J api. Therefore, the + <em>slf4j-api-VERSION.jar</em> jar must be present. This jar + can be downloaded from the <a + href="http://www.slf4j.org/">SLF4J</a> project. + </p> + <p>Logback's own jars must also be present, namely + <em>logback-core-VERSION.jar</em> and + <em>logback-classic-VERSION.jar</em> . + </p> + + <p> To configure logback-classic, a file called + <em>logback.xml</em> should be placed in the + <em>JETTY_HOME/resources</em> directory. You can find sample + configuration files in the + <em>logback-examples/src/main/java/chapter4/conf/</em> folder + shipping within the logback distribution. + </p> - <!-- end of definitions --> - </dl> + </dd> + + <hr /> + + + <!-- end of definitions --> + </dl> + + + </div> - </div> + <script src="templates/footer.js" type="text/javascript"></script> + </div> -<script src="templates/footer.js"></script> -</div> + </body> </html> Modified: logback/trunk/logback-site/src/site/pages/index.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/index.html (original) +++ logback/trunk/logback-site/src/site/pages/index.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/joran.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/joran.html (original) +++ logback/trunk/logback-site/src/site/pages/joran.html Tue Nov 11 16:13:01 2008 @@ -1,129 +1,135 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Using Joran</title> -<link rel="stylesheet" type="text/css" media="screen" href="css/site.css" /> -<link rel="stylesheet" type="text/css" media="print" href="css/print.css" /> - -</head> -<body> - <script type="text/javascript">prefix='./'</script> - <script type="text/javascript" src="templates/header.js"></script> -<div id="left"> - <script type="text/javascript" src="templates/left.js"></script> -</div> -<div id="content"> - - <h2>Using Joran in your own applications</h2> - - <p>As we've seen, logback relies on Joran, a mature, flexible and - powerful configuration framework. Many of the capabilities offered - by logback modules are possible with the help of Joran. - </p> - - <p>Joran is actually a generic configuration system which can be - used independently of logging. To emphaises this point, we should - mention that the logback-core module does not have a notion of - loggers. In that spirit, many of the examples related to this - tutorial, have nothing to do with loggers, appenders or layouts. - </p> - - <p class="red" style="text-decoration: line-through;">The examples - for this chapter can be found under - <em>LOGBACK_HOME/logback-examples/src/main/java/chapter3</em>. - </p> - - <p>To install joran, simply <a href="../download.html">download</a> - logback and add <em>logback-core-${version}.jar</em> to your - classpath.</p> - - <h2>Historical perspective</h2> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> - <p>One of the most powerful features of the Java language is - reflection. Reflection makes it possible to configure software - systems declaratively. For example, many important properties of an - EJB are configured with the <em>ejb.xml</em> file. While EJBs are - written in Java, many of their properties are specified within the - <em>ejb.xml</em> file. Similarly, logback settings can be specified - in a configuration file, expressed in XML format. - </p> - - <p>In log4j, logback's predecessor, <code>DOMConfigurator</code> - which shipped with log4j version 1.2.x could also parse - configuration files written in XML. The <code>DOMConfigurator</code> - was written in a way that forced to tweak it each time the structure - of the configuration file changed. The modified code had to be - recompiled and redeployed. Just as importantly, the code of the - DOMConfigurator consists of loops dealing with children elements - containing many interspersed if/else statements. One could not help - but notice that that particular code reeked of redundancy. The <a - href="http://jakarta.apache.org/commons/digester/">digester - project</a> has shown that it is possible to parse XML files using - pattern matching rules. At parse time, digester will apply the rules - that match previously stated patterns. Rule classes are usually - quite small and specialized. Consequently, they are relatively easy - to understand and to maintain. - </p> - - <p>Joran is heavily inspired by the commons-digester project but - uses a slightly different terminology. In commons-digester, a rule - can be seen as consisting of a pattern and a rule, as shown by the - <code>Digester.addRule(String pattern, Rule rule)</code> method. We - find it unnecessarily confusing to have a rule to consist of itself, - not recursively but with a different meaning. In Joran, a rule - consists of a pattern and an action. An action is invoked when a - match occurs for the corresponding pattern. This relation between - patterns and actions lies at the core of Joran. Quite remarkably, - one can deal with quite complex requirements by using simple - patterns, or more precisely with exact matches and wildcard - matches. For example, the pattern <em>a/b</em> will match a - <code><b></code> element nested within an <code><a></code> - element but not a <code><c></code> element, even if nested within - a <code><b></code> element. It is also possible to match a - particular XML element, regardless of its nesting level, by using - the <em>*</em> wildcard character. For example, the pattern - <em>*/a</em> will match an <code><a></code> element at any - nesting position within the document. Other types of patterns, for - example <em>a/*</em>, are not currently supported by Joran. - </p> - - <h2>SAX or DOM?</h2> - - <p>Due to the event-based architecture of the SAX API, a tool based - on SAX cannot easily deal with forward references, that is, - references to elements which are defined later than the current - element being processed. Elements with cyclical references are - equally problematic. More generally, the DOM API allows the user to - perform searches on all the elements and make forward jumps. - </p> - - <p>This extra flexibility initially led us to choose the DOM API as - the underlying parsing API for Joran. After some experimentation, it - quickly became clear that dealing with jumps to distant elements - while parsing the DOM tree did not make sense when the - interpretation rules were expressed in the form of patterns and - actions. <em>Joran only needs to be given the elements in the XML - document in a sequential, depth-first order.</em> - </p> - - <p>Joran was first implemented in DOM. However, the author migrated - to SAX in order to benefit location information, available only with - the SAX API. Location information allows Joran to display the exact - line and column number where an error occured, which comes in quite - handy when hunting down problems. - </p> - - - <h2>Actions</h2> - - <p>Actions extend the - <code>ch.qos.logback.core.joran.action.Action</code> class which - consists of the following abstract methods. - </p> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> + <title>Using Joran</title> + <link rel="stylesheet" type="text/css" href="css/common.css" /> + <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" /> + <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" /> + + </head> + <body> + <script type="text/javascript">prefix='./'</script> + <script type="text/javascript" src="templates/header.js"></script> + <div id="left"> + <script type="text/javascript" src="templates/left.js"></script> + </div> + <div id="content"> + + <h2>Using Joran in your own applications</h2> + + <p>As we've seen, logback relies on Joran, a mature, flexible and + powerful configuration framework. Many of the capabilities offered + by logback modules are possible with the help of Joran. + </p> + + <p>Joran is actually a generic configuration system which can be + used independently of logging. To emphaises this point, we should + mention that the logback-core module does not have a notion of + loggers. In that spirit, many of the examples related to this + tutorial, have nothing to do with loggers, appenders or layouts. + </p> + + <p class="red" style="text-decoration: line-through;">The examples + for this chapter can be found under + <em>LOGBACK_HOME/logback-examples/src/main/java/chapter3</em>. + </p> + + <p>To install joran, simply <a href="../download.html">download</a> + logback and add <em>logback-core-${version}.jar</em> to your + classpath.</p> + + <h2>Historical perspective</h2> + + <p>One of the most powerful features of the Java language is + reflection. Reflection makes it possible to configure software + systems declaratively. For example, many important properties of an + EJB are configured with the <em>ejb.xml</em> file. While EJBs are + written in Java, many of their properties are specified within the + <em>ejb.xml</em> file. Similarly, logback settings can be specified + in a configuration file, expressed in XML format. + </p> + + <p>In log4j, logback's predecessor, <code>DOMConfigurator</code> + which shipped with log4j version 1.2.x could also parse + configuration files written in XML. The + <code>DOMConfigurator</code> was written in a way that forced to + tweak it each time the structure of the configuration file + changed. The modified code had to be recompiled and + redeployed. Just as importantly, the code of the DOMConfigurator + consists of loops dealing with children elements containing many + interspersed if/else statements. One could not help but notice + that that particular code reeked of redundancy. The <a + href="http://jakarta.apache.org/commons/digester/">digester + project</a> has shown that it is possible to parse XML files using + pattern matching rules. At parse time, digester will apply the + rules that match previously stated patterns. Rule classes are + usually quite small and specialized. Consequently, they are + relatively easy to understand and to maintain. + </p> + + <p>Joran is heavily inspired by the commons-digester project but + uses a slightly different terminology. In commons-digester, a rule + can be seen as consisting of a pattern and a rule, as shown by the + <code>Digester.addRule(String pattern, Rule rule)</code> + method. We find it unnecessarily confusing to have a rule to + consist of itself, not recursively but with a different + meaning. In Joran, a rule consists of a pattern and an action. An + action is invoked when a match occurs for the corresponding + pattern. This relation between patterns and actions lies at the + core of Joran. Quite remarkably, one can deal with quite complex + requirements by using simple patterns, or more precisely with + exact matches and wildcard matches. For example, the pattern + <em>a/b</em> will match a <code><b></code> element nested + within an <code><a></code> element but not a + <code><c></code> element, even if nested within a + <code><b></code> element. It is also possible to match a + particular XML element, regardless of its nesting level, by using + the <em>*</em> wildcard character. For example, the pattern + <em>*/a</em> will match an <code><a></code> element at any + nesting position within the document. Other types of patterns, for + example <em>a/*</em>, are not currently supported by Joran. + </p> + + <h2>SAX or DOM?</h2> + + <p>Due to the event-based architecture of the SAX API, a tool based + on SAX cannot easily deal with forward references, that is, + references to elements which are defined later than the current + element being processed. Elements with cyclical references are + equally problematic. More generally, the DOM API allows the user to + perform searches on all the elements and make forward jumps. + </p> + + <p>This extra flexibility initially led us to choose the DOM API + as the underlying parsing API for Joran. After some + experimentation, it quickly became clear that dealing with jumps + to distant elements while parsing the DOM tree did not make sense + when the interpretation rules were expressed in the form of + patterns and actions. <em>Joran only needs to be given the + elements in the XML document in a sequential, depth-first + order.</em> + </p> + + <p>Joran was first implemented in DOM. However, the author migrated + to SAX in order to benefit location information, available only with + the SAX API. Location information allows Joran to display the exact + line and column number where an error occured, which comes in quite + handy when hunting down problems. + </p> + + + <h2>Actions</h2> + + <p>Actions extend the + <code>ch.qos.logback.core.joran.action.Action</code> class which + consists of the following abstract methods. + </p> -<div class="source"><pre>package ch.qos.logback.core.joran.action; + <p class="source">package ch.qos.logback.core.joran.action; import org.xml.sax.Attributes; import ch.qos.logback.core.joran.spi.ExecutionContext; @@ -144,46 +150,46 @@ * have been processed. */ public abstract void end(ExecutionContext ec, String name); -}</pre></div> +}</p> - <p>Thus, every action must implement the begin and end methods.</p> + <p>Thus, every action must implement the begin and end methods.</p> - <h2>Execution context</h2> + <h2>Execution context</h2> - <p>To allow various actions to collaborate, the invocation of begin - and end methods include an execution context as the first - parameter. The execution context includes an object stack, an object - map, an error list and a reference to the Joran interpreter invoking - the action. Please see the - <code>ch.qos.logback.core.joran.spi.ExecutionContext</code> class - for the exact list of fields contained in the execution context. - </p> - - <p>Actions can collaborate together by fetching, pushing or popping - objects from the common object stack, or by putting and fetching - keyed objects on the common object map. Actions can report any error - conditions by adding error items on the execution context's - <code>StatusManager</code>. - </p> - - <a name="helloWorld"></a> - <h3>A hello world example</h3> - - <p>The <em>logback-examples/src/main/java/chapter3/helloWorld/</em> - directory includes a trivial action and Joran interpreter setup - which just displays <em>Hello World</em> when a <hello-world> - element is encountered in an XML file. It also includes the basic - steps which are necessary to set up and invoke a Joran interpreter. - </p> - - <p>The <em>hello.xml</em> file contains only one element, without - any other nested elements. The <a - href="../xref/chapter3/helloWorld/HelloWorldAction.html"> - <code>HelloWorldAction</code></a> class is a trivial implementation: - it only prints "Hello World" in the console when it's - <code>begin()</code> method is called. - </p> + <p>To allow various actions to collaborate, the invocation of begin + and end methods include an execution context as the first + parameter. The execution context includes an object stack, an object + map, an error list and a reference to the Joran interpreter invoking + the action. Please see the + <code>ch.qos.logback.core.joran.spi.ExecutionContext</code> class + for the exact list of fields contained in the execution context. + </p> + + <p>Actions can collaborate together by fetching, pushing or popping + objects from the common object stack, or by putting and fetching + keyed objects on the common object map. Actions can report any error + conditions by adding error items on the execution context's + <code>StatusManager</code>. + </p> + + <a name="helloWorld"></a> + <h3>A hello world example</h3> + + <p>The <em>logback-examples/src/main/java/chapter3/helloWorld/</em> + directory includes a trivial action and Joran interpreter setup + which just displays <em>Hello World</em> when a <hello-world> + element is encountered in an XML file. It also includes the basic + steps which are necessary to set up and invoke a Joran interpreter. + </p> + + <p>The <em>hello.xml</em> file contains only one element, without + any other nested elements. The <a + href="../xref/chapter3/helloWorld/HelloWorldAction.html"> + <code>HelloWorldAction</code></a> class is a trivial implementation: + it only prints "Hello World" in the console when it's + <code>begin()</code> method is called. + </p> <p> <a href="../xref/chapter3/helloWorld/HelloWorld.html"><code>HelloWorld</code></a> @@ -505,7 +511,7 @@ </p> -<script src="templates/footer.js"></script> + <script src="templates/footer.js" type="text/javascript"></script> </div> </body> </html> Modified: logback/trunk/logback-site/src/site/pages/license.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/license.html (original) +++ logback/trunk/logback-site/src/site/pages/license.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/mailinglist.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/mailinglist.html (original) +++ logback/trunk/logback-site/src/site/pages/mailinglist.html Tue Nov 11 16:13:01 2008 @@ -1,57 +1,54 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> -<html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Mailing lists</title> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> + <head> + <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> + <title>Mailing lists</title> + <link rel="stylesheet" type="text/css" href="css/common.css" /> <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" /> <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" /> -</head> -<body> - <script> -prefix=''; -</script> - -<script src="templates/header.js"></script> -<div id="left"> - <script src="templates/left.js"></script> -</div> -<div id="content"> - + </head> + <body> + <script type="text/javascript">prefix='';</script> + + <script src="templates/header.js" type="text/javascript"></script> + <div id="left"> + <script src="templates/left.js" type="text/javascript"></script> + </div> + <div id="content"> - - <h2>Project Mailing Lists</h2> + <h2>Project Mailing Lists</h2> - <p> - A mailing list is an electronic discussion forum that anyone - can subscribe to. When someone sends an email message to the - mailing list, a copy of that message is broadcast to - everyone who is subscribed to that mailing list. Mailing - lists provide a simple and effective communication - mechanism. With potentially thousands of subscribers, there - is a common set of etiquette guidelines that you should - observe. Please keep on reading. + <p>A mailing list is an electronic discussion forum that anyone + can subscribe to. When someone sends an email message to the + mailing list, a copy of that message is broadcast to everyone who + is subscribed to that mailing list. Mailing lists provide a simple + and effective communication mechanism. With potentially thousands + of subscribers, there is a common set of etiquette guidelines that + you should observe. Please keep on reading. </p> - <h3>Respect the mailing list type</h3> - <p> - The "User" lists where you can send questions and comments - about configuration, setup, usage and other "user" types of - questions. The "Developer" lists where you can send - questions and comments about the actual software source code - and general "development" types of questions. + + <h3>Respect the mailing list type</h3> + + <p>The "User" lists where you can send questions and comments + about configuration, setup, usage and other "user" types of + questions. The "Developer" lists where you can send questions and + comments about the actual software source code and other issues + related to development. </p> - <p> - Some questions are appropriate for posting on both the - "user" and the "developer" lists. In this case, pick one and - only one. Do not cross post. + + <p>Some questions are appropriate for posting on both the "user" + and the "developer" lists. In this case, pick one and only one. Do + not cross post. </p> - <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>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> @@ -166,7 +163,7 @@ <p> </p> - <script src="templates/footer.js"></script> + <script src="templates/footer.js" type="text/javascript"></script> </div> </body> </html> Modified: logback/trunk/logback-site/src/site/pages/manual/appenders.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/appenders.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/appenders.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,5 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/manual/architecture.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/architecture.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/architecture.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/manual/contextSelector.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/contextSelector.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/contextSelector.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/manual/filters.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/filters.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/filters.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/manual/index.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/index.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/index.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/manual/introduction.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/introduction.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/introduction.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,5 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/manual/jmxConfig.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/jmxConfig.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/jmxConfig.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/manual/joran.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/joran.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/joran.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/manual/layouts.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/layouts.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/layouts.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/manual/mdc.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/manual/mdc.html (original) +++ logback/trunk/logback-site/src/site/pages/manual/mdc.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> Modified: logback/trunk/logback-site/src/site/pages/news.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/news.html (original) +++ logback/trunk/logback-site/src/site/pages/news.html Tue Nov 11 16:13:01 2008 @@ -1,50 +1,49 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>News</title> + <head> + <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> + <title>News</title> <link rel="stylesheet" type="text/css" href="css/common.css" /> <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" /> <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" /> - - -</head> -<body> - <script> -prefix=''; -</script> - -<script src="templates/header.js"></script> -<div id="left"> - <script src="templates/left.js"></script> -</div> -<div id="content"> + + </head> + <body> + <script type="text/javascript">prefix='';</script> + + <script src="templates/header.js" type="text/javascript"></script> + <div id="left"> + <script src="templates/left.js" type="text/javascript"></script> + </div> + <div id="content"> - <h2>Logback News</h2> + <h2>Logback News</h2> - <p>You can receive logback-related announcements by subscribing to - the <a - href="http://www.qos.ch/mailman/listinfo/logback-announce">logback - announce</a> mailing list.</p> + <p>You can receive logback-related announcements by subscribing to + the <a + href="http://www.qos.ch/mailman/listinfo/logback-announce">logback + announce</a> mailing list.</p> - <hr width="80%" align="center" /> - - <h3>28th of November 2008 - Release of version 0.9.12</h3> + <hr width="80%" align="center" /> - <p>Fixed <a href="http://jira.qos.ch/browse/LBCORE-26">bug - LBCORE-26</a> reported by Tsutomu YANO and independently by - Hontvári József and Gamaliel - Amaudruz. <code>RollingFileAppender</code> when used in conjunction - with <code>DateBasedRollingPolicy</code> will rollover existing log - files at initialization if their timestamp warrants it. - </p> + <h3>28th of November 2008 - Release of version 0.9.12</h3> + + <p>Fixed <a href="http://jira.qos.ch/browse/LBCORE-26">bug + LBCORE-26</a> reported by Tsutomu YANO and independently by + Hontvári József and Gamaliel + Amaudruz. <code>RollingFileAppender</code> when used in conjunction + with <code>DateBasedRollingPolicy</code> will rollover existing log + files at initialization if their timestamp warrants it. + </p> - <p>Fixed <a - href="http://jira.qos.ch/browse/LBCLASSIC-83">LBCLASSIC-83</a>. It - is now possible to set the level of a logger to null, even if it was - previously set to a non-null level. Previously, a - <code>NullPointerException</code> would be thrown. - </p> + <p>Fixed <a + href="http://jira.qos.ch/browse/LBCLASSIC-83">LBCLASSIC-83</a>. + It is now possible to set the level of a logger to null, even if + it was previously set to a non-null level. Previously, a + <code>NullPointerException</code> would be thrown. + </p> <p>In reponse to <a href="http://jira.qos.ch/browse/LBCLASSIC-61">LBCLASSIC-61</a>, <a @@ -254,74 +253,74 @@ <h3>26th of March 2008 - Release of version 0.9.9</h3> - <p>MDC data in now inherited by child threads. This behaviour was - already specified in the javadocs. The issue was raised by Martin - Benda in <a href="http://bugzilla.qos.ch/show_bug.cgi?id=64">bug - 64</a> and independently by Peter Huber. - </p> - - <p>Logback no longer includes retro-weaver generted jars for JDK - 1.4. There seemes to be little interest in JDK 1.4 builds. Calling - retro-weaver increases logback's build time by a few seconds each - time – seconds in which we can do more productive things. - </p> - - <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=104">bug - 104</a>, silly but but nonetheless serious copy-and-paste errors in - the c.q.l.classic.Logger class, reported by Joern Huxhorn. - </p> - - <p>Having been replaced by <code>SimpleSocketServer</code>, the - <code>SocketServer</code> class has been removed. - </p> - - <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=105">bug - 105</a>, sockets created by <code>SocketAppenderBase</code> is now - closed, reported by Joern Huxhorn. More generally, - <code>SimpleSocketServer</code> is much more careful to track open - client connections and to close them. - </p> - - <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=110">bug - 110</a> in relation with the <code>requestParameterMap</code> field - in <code>AccessEvent</code> - reported by Joern Huxhorn. - </p> - - <p>Fixed <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=66"> - SLF4J bug 66</a> in relation with caller data when using - log4j-over-slf4j - reported by Frnack Routier. - </p> - - <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=129">bug - 129</a> reported by Michael Franz. As a result, Joran now supports - nested as well as multiple file inclusions. - </p> - - <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=100">bug - 100</a> reported by Joern Huxhorn. At serialization time, object - array passed as parameter, when the LoggingEvent is are now - serialized as strings. - </p> - - <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=109">bug - 109</a> reported by Joern Huxhorn. There should no longer be any - NullPointerExceptions thrown by deserialized - <code>AccessEvent</code> instances. - </p> - - <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=8">bug - 8</a> reported by Sebastien Pennec. The documentation has been - updated to reflect the fact that that in the context of conversion - patterns the percent sign carries special meaning, in order to - include the percent sign as a literal, it must be escaped with a - backslash. - </p> - - <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=52">bug - 52</a> reported by Kenichi Masuko. The bug has been fixed on March - 8th, 2007. Starting with this release, Joran will support the - injection of any enum tpye, not just <code>FilterReply</code>. - </p> + <p>MDC data in now inherited by child threads. This behaviour was + already specified in the javadocs. The issue was raised by Martin + Benda in <a href="http://bugzilla.qos.ch/show_bug.cgi?id=64">bug + 64</a> and independently by Peter Huber. + </p> + + <p>Logback no longer includes retro-weaver generted jars for JDK + 1.4. There seemes to be little interest in JDK 1.4 builds. Calling + retro-weaver increases logback's build time by a few seconds each + time – seconds in which we can do more productive things. + </p> + + <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=104">bug + 104</a>, silly but but nonetheless serious copy-and-paste errors in + the c.q.l.classic.Logger class, reported by Joern Huxhorn. + </p> + + <p>Having been replaced by <code>SimpleSocketServer</code>, the + <code>SocketServer</code> class has been removed. + </p> + + <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=105">bug + 105</a>, sockets created by <code>SocketAppenderBase</code> is now + closed, reported by Joern Huxhorn. More generally, + <code>SimpleSocketServer</code> is much more careful to track open + client connections and to close them. + </p> + + <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=110">bug + 110</a> in relation with the <code>requestParameterMap</code> field + in <code>AccessEvent</code> - reported by Joern Huxhorn. + </p> + + <p>Fixed <a href="http://bugzilla.slf4j.org/show_bug.cgi?id=66"> + SLF4J bug 66</a> in relation with caller data when using + log4j-over-slf4j - reported by Frnack Routier. + </p> + + <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=129">bug + 129</a> reported by Michael Franz. As a result, Joran now supports + nested as well as multiple file inclusions. + </p> + + <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=100">bug + 100</a> reported by Joern Huxhorn. At serialization time, object + array passed as parameter, when the LoggingEvent is are now + serialized as strings. + </p> + + <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=109">bug + 109</a> reported by Joern Huxhorn. There should no longer be any + NullPointerExceptions thrown by deserialized + <code>AccessEvent</code> instances. + </p> + + <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=8">bug + 8</a> reported by Sebastien Pennec. The documentation has been + updated to reflect the fact that that in the context of conversion + patterns the percent sign carries special meaning, in order to + include the percent sign as a literal, it must be escaped with a + backslash. + </p> + + <p>Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=52">bug + 52</a> reported by Kenichi Masuko. The bug has been fixed on March + 8th, 2007. Starting with this release, Joran will support the + injection of any enum tpye, not just <code>FilterReply</code>. + </p> <hr width="80%" align="center" /> @@ -483,304 +482,269 @@ </p> - <h3>March 5th, 2007 - Release of version 0.9.2</h3> - - <p>The documentation is now in the <em>docs/</em> directory to allow an - easier access to the logback manual and website for offline viewing. - </p> - - <h3>March 5th, 2007 - Release of version 0.9.1</h3> - - <p>Logback-class now depends on SLF4J version 1.3.0 instead of - 1.2.</p> - - <p>Numerous improvements to the documentation.</p> - - <p><a href="http://bugzilla.qos.ch/show_bug.cgi?id=46">Bug #46</a> - reported by Mark Renyolds has been fixed. The - <code>TimeUtilTest</code> should now run fine under any time - zone.</p> - - <p><a href="http://bugzilla.qos.ch/show_bug.cgi?id=45">Bug - #45</a>, also reported by Mark Reynolds, has been fixed. There - should be no <code>ClassCastException</code> thrown anymore when - passing an <code>Object</code> to the printing methods using the - log4j-bridge module. </p> - - <hr width="80%" align="center" /> - - <h3>January 31st, 2007 - Release of version 0.9</h3> - - <p> - This version contains a new component, namely the - <code>ContextSelector</code>, that provides context separation - and management when logback is used by several web-apps running - under the same server. A <a - href="manual/contextSelector.html">new chapter</a> was added to - the logback manual to detail the use of the - <code>ContextSelector</code>, along with its associated - components. - </p> - - <p> - The <code>JMXConfigurator</code> has been improved. It now shows - the context's Status objects, which lets users check the - internal state of logback. - </p> - - <p> - The logback manual's chapter 2, about <a - href="manual/architecture.html">logback's architecture</a>, has - been updated with two sections: Under the hood and Performance. - </p> - - <hr width="80%" align="center" /> - - <h3>January 23th, 2007 - Release of version 0.8.1</h3> - - <p> - This version contains new components in the Access module, - allowing users to display the full HttpServletRequest or - HttpServletResponse of an access event. - </p> - - <p> - The documentation section has been updated. The short introduction was split - into the chapter 1 and chapter 2 of the logback manual. The chapters about - Appenders and Layouts have been updated to document new components of logback. - </p> - - <p>A demonstration webApp presenting logback's major components is - available. A document explains how to run it, and provides a - step-by-step visit of the demo. - </p> + <h3>March 5th, 2007 - Release of version 0.9.2</h3> + + <p>The documentation is now in the <em>docs/</em> directory to allow an + easier access to the logback manual and website for offline viewing. + </p> + + <h3>March 5th, 2007 - Release of version 0.9.1</h3> + + <p>Logback-class now depends on SLF4J version 1.3.0 instead of + 1.2.</p> + + <p>Numerous improvements to the documentation.</p> + + <p><a href="http://bugzilla.qos.ch/show_bug.cgi?id=46">Bug #46</a> + reported by Mark Renyolds has been fixed. The + <code>TimeUtilTest</code> should now run fine under any time + zone.</p> + + <p><a href="http://bugzilla.qos.ch/show_bug.cgi?id=45">Bug + #45</a>, also reported by Mark Reynolds, has been fixed. There + should be no <code>ClassCastException</code> thrown anymore when + passing an <code>Object</code> to the printing methods using the + log4j-bridge module. </p> + + <hr width="80%" align="center" /> + + <h3>January 31st, 2007 - Release of version 0.9</h3> + + <p>This version contains a new component, namely the + <code>ContextSelector</code>, that provides context separation and + management when logback is used by several web-apps running under + the same server. A <a href="manual/contextSelector.html">new + chapter</a> was added to the logback manual to detail the use of the + <code>ContextSelector</code>, along with its associated components. + </p> + + <p>The <code>JMXConfigurator</code> has been improved. It now shows + the context's Status objects, which lets users check the internal + state of logback. + </p> + + <p>The logback manual's chapter 2, about <a + href="manual/architecture.html">logback's architecture</a>, has been + updated with two sections: Under the hood and Performance. + </p> + + <hr width="80%" align="center" /> + + <h3>January 23th, 2007 - Release of version 0.8.1</h3> + + <p>This version contains new components in the Access module, + allowing users to display the full HttpServletRequest or + HttpServletResponse of an access event. + </p> - <p>A first translation of logback jars to JDK1.4 is present in - this release. - </p> - + <p>The documentation section has been updated. The short + introduction was split into the chapter 1 and chapter 2 of the + logback manual. The chapters about Appenders and Layouts have been + updated to document new components of logback. + </p> - <hr width="80%" align="center" /> + <p>A demonstration webApp presenting logback's major components is + available. A document explains how to run it, and provides a + step-by-step visit of the demo. + </p> + + <p>A first translation of logback jars to JDK1.4 is present in + this release. + </p> + + + <hr width="80%" align="center" /> + + <h3>January 12th, 2007 - Release of version 0.8</h3> + + <p>This version contains a whole new chapter, namely Chapter 3, + about logback configuration. Several other documentation pages + have been improved. + </p> + + <p>Logback now uses Generics in many components. + </p> + + <p>Several new components have been added to logback. A JMX + Configurator now allows users to see and modify loggers or reload + configuration among other possibilities. A <a + href="jmxConfig.html">document</a> about this configurator is + available in the <a href="documentation.html">corresponding + section</a> of the site. We'd like to thank Sebastian Davids for his + ideas and contributions to this component. + </p> + + <p>A JMSTopicAppender and JMSQueueAppender are now available, as + well as two new filters: LevelFilter and ThresholdFilter. A + refactoring was done in the filters objects to ease the + implementation of custom filters. + </p> + + <hr width="80%" align="center" /> - <h3>January 12th, 2007 - Release of version 0.8</h3> + + <h3>December 19th, 2006 - Release of version 0.7.1</h3> + + <p>Version 0.7.1 of logback has been released. + </p> + + <p>This version contains more detailled information about logback + access module, and its JMX components. A <a + href="access.html">dedicated page</a> explains how to configure and + use logback access in Tomcat and Jetty, and access some of its + components via JMX. + </p> + + <hr width="80%" align="center" /> + + <h3>December 18th, 2006 - Release of version 0.7</h3> + + <p>Version 0.7 of logback has been released.</p> + + <p>Logback now ships with a new module: <em>log4j-bridge</em>. This + new module can be used to intercept log4j calls and redirects them + to logback components. More information about this module can be + found in the corresponding <a href="bridge.html">documentation + page</a>. + </p> + + <p>The documentation has been vastly updated. Two new chapters, + namely Filters and MDC, are available in the manual section. + </p> - <p>This version contains a whole new chapter, namely Chapter 3, - about logback configuration. Several other documentation pages - have been improved. - </p> - - <p>Logback now uses Generics in many components. - </p> - - <p>Several new components have been added to logback. A JMX - Configurator now allows users to see and modify loggers or reload - configuration among other possibilities. A <a - href="jmxConfig.html">document</a> about this configurator is - available in the <a href="documentation.html">corresponding - section</a> of the site. We'd like to thank Sebastian Davids for - his ideas and contributions to this component. - </p> - - <p>A JMSTopicAppender and JMSQueueAppender are now available, as - well as two new filters: LevelFilter and ThresholdFilter. A - refactoring was done in the filters objects to ease the - implementation of custom filters. - </p> - - <hr width="80%" align="center" /> - - - <h3>December 19th, 2006 - Release of version 0.7.1</h3> - - <p>Version 0.7.1 of logback has been released. - </p> - - <p>This version contains more detailled information about logback - access module, and its JMX components. A <a - href="access.html">dedicated page</a> explains how to configure - and use logback access in Tomcat and Jetty, and access some of its - components via JMX. - </p> + <hr width="80%" align="center" /> + + <h3>November 30th, 2006 - Release of version 0.6</h3> + + <p>Version 0.6 of logback has been released. + </p> + + <p>Logback classic now supports automatic configuration, allowing + test and production environment + configuration. <code>TurboFilters</code> make their first appearance + in a logback release. They provide ultra-fast filtering + possibilities. The logging context now supports listeners which + will be contacted each time the context is reset or + started. <code>SMTPAppender</code> allows for much more flexible + configuration than before. + </p> - <hr width="80%" align="center" /> + <p>In logback access, new Appenders are available, namely + <code>SocketAppender</code> and <code>DBAppender</code>. Logback + access now supports filtering and event evaluations. A + <code>CountingFilter</code> has been added. It provides statistical + views of server access, reachable via JMX. + </p> + + <p>The documentation has also been improved. A complete new chapter + has been added about Appenders, the short introduction to logback + classic has been updated and a new module, containing many + configuration examples has been added. + </p> + + <p>Logback now uses continous integration in its development. + </p> + + <p>Tests have been improved, many new have been added. This release + also provides some bug fixes. + </p> - <h3>December 18th, 2006 - Release of version 0.7</h3> + <hr width="80%" align="center" /> + + <h3>October 26th, 2006 - Release of version 0.5</h3> + + <p>Version 0.5 of logback has been released. + </p> - <p> - Version 0.7 of logback has been released. - </p> - - <p> - Logback now ships with a new module: <em>log4j-bridge</em>. This new module - can be used to intercept log4j calls and redirects them to logback components. - More information about this module can be found in the corresponding - <a href="bridge.html">documentation page</a>. - </p> - - <p> - The documentation has been vastly updated. Two new chapters, - namely Filters and MDC, are available in the manual section. - </p> + <p>This release offers a important improvements in Joran. In + particular, Joran can now replay configuration elements. + </p> - <hr width="80%" align="center" /> + <p>As in the previous release, a major area of work is the + documentation which is being continously improved. + </p> - <h3>November 30th, 2006 - Release of version 0.6</h3> + <hr width="80%" align="center" /> + + <h3>October 9th, 2006 - Release of version 0.4</h3> + + <p>Version 0.3 of logback has been released. + </p> + + <p>This release includes an improved access module, with specific + implementations for the Jetty and Tomcat servers. Documentation was + also added to show how to integrate logback-access with Jetty. + </p> - <p>Version 0.6 of logback has been released. - </p> + <p>As for the classic module, several appenders and layouts have + been added or improved. The error reporting of logback has also + been enhanced, presenting the user with a link to an online page + explaining possible reasons for the error. + </p> - <p>Logback classic now supports automatic configuration, allowing - test and production environment - configuration. <code>TurboFilters</code> make their first - appearance in a logback release. They provide ultra-fast filtering - possibilities. The logging context now supports listeners which - will be contacted each time the context is reset or - started. <code>SMTPAppender</code> allows for much more flexible - configuration than before. - </p> - - <p> - In logback access, new Appenders are available, namely - <code>SocketAppender</code> and <code>DBAppender</code>. - Logback access now supports filtering and event evaluations. A - <code>CountingFilter</code> has been added. It provides - statistical views of server access, reachable via JMX. - </p> - - <p> - The documentation has also been improved. A complete new chapter - has been added about Appenders, the short introduction to logback - classic has been updated and a new module, containing many configuration - examples has been added. - </p> - - <p> - Logback now uses continous integration in its development. - </p> - - <p> - Tests have been improved, many new have been added. - This release also provides some bug fixes. - </p> - - <hr width="80%" align="center" /> - - <h3>October 26th, 2006 - Release of version 0.5</h3> - - <p> - Version 0.5 of logback has been released. - </p> - - <p> - This release offers a important improvements in Joran. In - particular, Joran can now replay configuration elements. - </p> - - <p> - As in the previous release, a major area of work is the - documentation which is being continously improved. - </p> - - <hr width="80%" align="center" /> - - <h3>October 9th, 2006 - Release of version 0.4</h3> - <p> - Version 0.3 of logback has been released. - </p> - - <p> - This release includes an improved access module, with specific - implementations for the Jetty and Tomcat servers. Documentation - was also added to show how to integrate logback-access with - Jetty. - </p> - - <p> - As for the classic module, several appenders and layouts have - been added or improved. The error reporting of logback has also - been enhanced, presenting the user with a link to an online page - explaining possible reasons for the error. - </p> - - <p> - A joran documentation was added, with examples in the core - module. + <p>A joran documentation was added, with examples in the core + module. </p> - <hr width="80%" align="center" /> - - <h3>September 8th, 2006 - Release of version 0.3</h3> - <p> - Version 0.3 of logback has been released. - </p> - - <p> - This release offers several new Appenders, support for Mapped - Diagnostic Context, improved tests and documentation<br /> - </p> - - <p> - In response to a bug report by Rickard Nilsson on the logback - mailing list, a bug affecting parametrized logging was fixed. - </p> - - <p> - We also released a <a - href="http://logback.qos.ch/translator/">PropertiesTranslator</a> - webapp that converts <em>log4j.properties</em> files to joran - configuration files (in XML format).<br /> + <hr width="80%" align="center" /> + + <h3>September 8th, 2006 - Release of version 0.3</h3> + <p> + Version 0.3 of logback has been released. </p> - - <hr width="80%" align="center" /> - - <h3>August 23th, 2006 - Release of version 0.2.5</h3> - - <p> - Version 0.2.5 of logback has been released. + + <p>This release offers several new Appenders, support for Mapped + Diagnostic Context, improved tests and documentation<br /> </p> - <p> - This release offers better documentation. With a number of - correction mande in the short introduction to logback-classic. - </p> - - <hr width="80%" align="center" /> - - - <h3>August 15th, 2006 - Release of version 0.2</h3> - <p> - Version 0.2 of logback has been released. - </p> - - <p> - It offers better tests, a few more functionalities, and enhanced - documentation. We also improved the site design to make it - simpler and more efficient. + <p>In response to a bug report by Rickard Nilsson on the logback + mailing list, a bug affecting parametrized logging was fixed. </p> - <hr width="80%" align="center" /> + <p>We also released a <a + href="http://logback.qos.ch/translator/">PropertiesTranslator</a> + webapp that converts <em>log4j.properties</em> files to joran + configuration files (in XML format).<br /> + </p> - <h3>July 26th, 2006 - Release of version 0.1</h3> + <hr width="80%" align="center" /> + + <h3>August 23th, 2006 - Release of version 0.2.5</h3> + + <p> Version 0.2.5 of logback has been released. </p> - <p> - Version 0.1 of logback has been released. + <p>This release offers better documentation. With a number of + correction mande in the short introduction to logback-classic. </p> + + <hr width="80%" align="center" /> + + + <h3>August 15th, 2006 - Release of version 0.2</h3> + + <p>Version 0.2 of logback has been released.</p> - <hr width="80%" align="center" /> + <p>It offers better tests, a few more functionalities, and enhanced + documentation. We also improved the site design to make it simpler + and more efficient. + </p> - <h3>February 9th, 2006 - Logback web-site goes live</h3> - <p> - The logback web-site goes live on the 9th of February. At - its present state, it is pretty primitive but updates will - follow. - </p> - - - - - + <hr width="80%" align="center" /> + + <h3>July 26th, 2006 - Release of version 0.1</h3> + + <p>Version 0.1 of logback has been released.</p> + + <hr width="80%" align="center" /> + + <h3>February 9th, 2006 - Logback web-site goes live</h3> + + <p>The logback web-site goes live on the 9th of February. At its + present state, it is pretty primitive but updates will follow. + </p> + -<script src="templates/footer.js"></script> + <script src="templates/footer.js" type="text/javascript"></script> </div> </body> </html> Modified: logback/trunk/logback-site/src/site/pages/repos.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/repos.html (original) +++ logback/trunk/logback-site/src/site/pages/repos.html Tue Nov 11 16:13:01 2008 @@ -1,81 +1,66 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> -<head> -<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Repository</title> + <head> + <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> + <title>Repository</title> <link rel="stylesheet" type="text/css" href="css/common.css" /> <link rel="stylesheet" type="text/css" href="css/screen.css" media="screen" /> <link rel="stylesheet" type="text/css" href="css/_print.css" media="print" /> -</head> -<body> - <script> -prefix=''; -</script> - -<script src="templates/header.js"></script> -<div id="left"> - <script src="templates/left.js"></script> -</div> -<div id="content"> + </head> + <body> + <script type="text/javascript">prefix='';</script> + <script src="templates/header.js" type="text/javascript"></script> + <div id="left"> + <script src="templates/left.js" type="text/javascript"></script> + </div> + <div id="content"> <div class="section"> <h2>Source Repository</h2> </div> - <p> - We keep the source code in revision control systems called - Subversion. Developers have write access to the Subversion - repository, enabling them to make changes to the source - code. Everyone has read access to the repositories, so you may - download the most up-to-date development version of the - software. Note that the latest version in the Subversion - repository many not work as expected, it may not even compile - properly. If you are looking for a stable release of the source - code, you should download an official distribution instead of - the latest version in the Subversion repositories. + <p>We store the project's source code in a revision control system + called Subversion. Developers have write access to the repository, + enabling them to make changes to the source code. Everyone else + has read-access to the repository. Thus, anyone can check out + latest development version of the software. Note that the latest + version in the repository may not work as expected. It may even + not compile. If you are looking for a stable release, then + download an official distribution. + </p> + + <p>There are several ways to access the Subversion repository:</p> + + <h2>Web Access</h2> + + <p>If you just wish to browse around or download a few individual + files, you can do so with web-based ViewVC interface: + </p> - There are several ways to access the Subversion - repositories: + <p><a + href="http://svn.qos.ch/viewvc/logback/trunk/">http://svn.qos.ch/viewvc/logback/trunk/</a> </p> - <div class="section"> - <h2>Web Access</h2> - </div> - <p> - If you just wish to browse around or download a few individual - files, you can do so with web-based ViewVC interface: - </p> + <h2>Checking out a read-only copy</h2> - <p> - <a - href="http://svn.qos.ch/viewvc/logback/trunk/">http://svn.qos.ch/viewvc/logback/trunk/</a> - </p> - - <div class="section"> - <h2>Checking out a read-only copy</h2> - </div> - <p> - To access the Subversion repositories anonymously, you will need - a Subversion client. You can check out the entire logback - project with the following command:</p> + <p>To access the Subversion repositories anonymously, you will + need a Subversion client. You can check out the logback project + source code with the following command:</p> - <div class="source">svn co http://svn.qos.ch/repos/logback/trunk/ target_directory</div> + <!-- keep together as a single line --> + <p class="source">svn co http://svn.qos.ch/repos/logback/trunk/ target_directory</p> - <div class="section"> - <p> - Note that anonymous access allows read-only access only. For - read-write access please contact the logback <a - href="mailinglist.html">developer list</a> . - </p> - </div> - - - + <p>Note that anonymous access allows read-only access. For + read-write access, please contact the logback <a + href="mailinglist.html">developer list</a> . + </p> -<script src="templates/footer.js"></script> -</div> + <script src="templates/footer.js" type="text/javascript"></script> + </div> </body> </html> Modified: logback/trunk/logback-site/src/site/pages/support.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/support.html (original) +++ logback/trunk/logback-site/src/site/pages/support.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> @@ -9,11 +11,11 @@ </head> <body> - <script>prefix='';</script> + <script type="text/javascript">prefix='';</script> - <script src="templates/header.js"></script> + <script src="templates/header.js" type="text/javascript"></script> <div id="left"> - <script src="templates/left.js"></script> + <script src="templates/left.js" type="text/javascript"></script> </div> <div id="content"> Modified: logback/trunk/logback-site/src/site/pages/team.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/team.html (original) +++ logback/trunk/logback-site/src/site/pages/team.html Tue Nov 11 16:13:01 2008 @@ -1,4 +1,6 @@ -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-transitional.dtd"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> + <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />