Author: seb Date: Tue Jan 23 12:10:05 2007 New Revision: 1265 Modified: logback/trunk/logback-site/src/site/xdocTemplates/demo.xml Log: minor fixes Modified: logback/trunk/logback-site/src/site/xdocTemplates/demo.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/demo.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/demo.xml Tue Jan 23 12:10:05 2007 @@ -112,8 +112,8 @@ <div class="source"><pre><filter class="ch.qos.logback.core.filter.EvaluatorFilter"> <evaluator name="loggingTaskEval"> <expression> - logger.getName().contains("LoggingTask") && - message.contains("Howdydy-diddly-ho") && + logger.getName().contains("LoggingTask") && + message.contains("Howdydy-diddly-ho") && (timeStamp - event.getStartTime()) >= 20000 </expression> </evaluator> @@ -238,7 +238,9 @@ <p> SLF4J allows the use of Marker objects. For example, one could use <em>TRACE</em> markers, to enrich some -specific logging statements. On the other hand, one could want that such +specific logging statements. In our demo applications, the <em>Howdydy-diddly-ho</em> +logging statements are bound to a <em>TRACE</em> marker. +On the other hand, one could want that such marked statements be dropped and not logged anywhere. <code>TurboFilter</code> objects can do that in an elegant and flexible way. Let us uncomment the <em>TurboFilter: Marker value</em> section in the <em>logback.xml</em> file as