- logback-dev - mailman3.qos.ch

svn commit: r1523 - logback/trunk/logback-site/src/site/pages
by noreply.ceki＠qos.ch 03 May '07

03 May '07

Author: ceki Date: Thu May 3 20:45:31 2007 New Revision: 1523 Modified: logback/trunk/logback-site/src/site/pages/news.html Log: updated news 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 Thu May 3 20:45:31 2007 @@ -27,7 +27,18 @@ announce</a> mailing list.</p> <hr width="80%" align="center" /> - + + <h3>May 2007 - Release of version 0.9.6</h3> + + <p>Fixed <code>NoClassDefFoundError</code> problem when running + under JDK 1.4 <a + href="http://www.qos.ch/pipermail/logback-user/2007-April/000206.html">as + reported</a> by Brian Suksomwong. + </p> + + <hr width="80%" align="center" /> + + <h3>April 2nd, 2007 - Release of version 0.9.5</h3> <p>Fixed methods <code>isInfoEnabled</code>,

1 0

svn commit: r1522 - in logback/trunk/logback-classic/src: main/java/ch/qos/logback/classic test/java/ch/qos/logback/classic test/java/ch/qos/logback/classic/control
by noreply.ceki＠qos.ch 03 May '07

03 May '07

Author: ceki Date: Thu May 3 20:45:07 2007 New Revision: 1522 Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Level.java logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/HLogger.java logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/control/ControlLogger.java Log: Added trace methods to syncing with SLF4J version 1.4.0 Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Level.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Level.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Level.java Thu May 3 20:45:07 2007 @@ -11,10 +11,10 @@ package ch.qos.logback.classic; /** - * Defines the set of levels recognized by the LOGBback, that is {@link #OFF}, - * {@link #ERROR}, {@link #WARN}, {@link #INFO} and {@link #DEBUG}, - * {@link #ALL}. <p/> The <code>Level</code> class is final and cannot be - * sub-classed. + * Defines the set of levels recognized by logback-classic, that is {@link #OFF}, + * {@link #ERROR}, {@link #WARN}, {@link #INFO}, {@link #DEBUG}, + * {@link #TRACE} and {@link #ALL}. <p/> The <code>Level</code> class is + * final and cannot be sub-classed. * </p> */ public final class Level implements java.io.Serializable { @@ -26,6 +26,7 @@ public static final int WARN_INT = 30000; public static final int INFO_INT = 20000; public static final int DEBUG_INT = 10000; + public static final int TRACE_INT = 5000; public static final int ALL_INT = Integer.MIN_VALUE; public static final Integer OFF_INTEGER = new Integer(OFF_INT); @@ -33,6 +34,7 @@ public static final Integer WARN_INTEGER = new Integer(WARN_INT); public static final Integer INFO_INTEGER = new Integer(INFO_INT); public static final Integer DEBUG_INTEGER = new Integer(DEBUG_INT); + public static final Integer TRACE_INTEGER = new Integer(DEBUG_INT); public static final Integer ALL_INTEGER = new Integer(ALL_INT); /** @@ -41,29 +43,35 @@ public static final Level OFF = new Level(OFF_INT, "OFF"); /** - * The <code>ERROR</code> levelInt designates error events which may or not + * The <code>ERROR</code> level designates error events which may or not * be fatal to the application. */ public static final Level ERROR = new Level(ERROR_INT, "ERROR"); /** - * The <code>WARN</code> levelInt designates potentially harmful situations. + * The <code>WARN</code> level designates potentially harmful situations. */ public static final Level WARN = new Level(WARN_INT, "WARN"); /** - * The <code>INFO</code> levelInt designates informational messages + * The <code>INFO</code> level designates informational messages * highlighting overall progress of the application. */ public static final Level INFO = new Level(INFO_INT, "INFO"); /** - * The <code>DEBUG</code> levelInt designates informational events of lower + * The <code>DEBUG</code> level designates informational events of lower * importance. */ public static final Level DEBUG = new Level(DEBUG_INT, "DEBUG"); /** + * The <code>TRACE</code> level designates informational events of very low + * importance. + */ + public static final Level TRACE = new Level(TRACE_INT, "TRACE"); + + /** * The <code>ALL</code> is used to turn on all logging. */ public static final Level ALL = new Level(ALL_INT, "ALL"); @@ -95,12 +103,15 @@ /** * Convert a Level to an Integer object. + * * @return This level's Integer mapping. */ public final Integer toInteger() { switch (levelInt) { case ALL_INT: return ALL_INTEGER; + case TRACE_INT: + return TRACE_INTEGER; case DEBUG_INT: return DEBUG_INTEGER; case INFO_INT: @@ -149,6 +160,8 @@ switch (val) { case ALL_INT: return ALL; + case TRACE_INT: + return TRACE; case DEBUG_INT: return DEBUG; case INFO_INT: @@ -176,6 +189,9 @@ if (sArg.equalsIgnoreCase("ALL")) { return Level.ALL; } + if (sArg.equalsIgnoreCase("TRACE")) { + return Level.TRACE; + } if (sArg.equalsIgnoreCase("DEBUG")) { return Level.DEBUG; } Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/Logger.java Thu May 3 20:45:07 2007 @@ -370,6 +370,32 @@ return childLogger; } + public void trace(String msg) { + filterAndLog(FQCN, null, Level.TRACE, msg, null, null); + } + + public final void trace(String format, Object arg) { + filterAndLog(FQCN, null, Level.TRACE, format, arg, null); + } + + public void trace(String format, Object arg1, Object arg2) { + filterAndLog(FQCN, null, Level.TRACE, format, arg1, arg2, null); + } + + public void trace(String format, Object[] argArray) { + filterAndLog(FQCN, null, Level.TRACE, format, argArray, null); + } + + public void trace(String msg, Throwable t) { + if (isDebugEnabled()) { + filterAndLog(FQCN, null, Level.TRACE, msg, null, t); + } + } + + public final void trace(Marker marker, String msg) { + filterAndLog(FQCN, marker, Level.TRACE, msg, null, null); + } + public void debug(String msg) { filterAndLog(FQCN, null, Level.DEBUG, msg, null, null); } @@ -471,6 +497,23 @@ filterAndLog(FQCN, marker, level, msg, param1, param2, t); } + public void trace(Marker marker, String format, Object arg) { + filterAndLog(FQCN, marker, Level.TRACE, format, arg, null); + } + + public void trace(Marker marker, String format, Object arg1, Object arg2) { + filterAndLog(FQCN, marker, Level.TRACE, format, arg1, arg2, null); + } + + public void trace(Marker marker, String format, Object[] argArray) { + filterAndLog(FQCN, marker, Level.TRACE, format, argArray, null); + } + + public void trace(Marker marker, String msg, Throwable t) { + filterAndLog(FQCN, marker, Level.TRACE, msg, null, t); + } + + public void debug(Marker marker, String format, Object arg) { filterAndLog(FQCN, marker, Level.DEBUG, format, arg, null); } @@ -567,10 +610,28 @@ filterAndLog(FQCN, marker, Level.INFO, msg, null, t); } + public final boolean isTraceEnabled() { + return isTraceEnabled(null); + } + + public final boolean isDebugEnabled() { return isDebugEnabled(null); } + public boolean isTraceEnabled(Marker marker) { + final FilterReply decision = callTurboFilters(marker, Level.TRACE); + if (decision == FilterReply.NEUTRAL) { + return effectiveLevelInt <= Level.TRACE_INT; + } else if (decision == FilterReply.DENY) { + return false; + } else if (decision == FilterReply.ACCEPT) { + return true; + } else { + throw new IllegalStateException("Unknown FilterReply value: " + decision); + } + } + public boolean isDebugEnabled(Marker marker) { final FilterReply decision = callTurboFilters(marker, Level.DEBUG); if (decision == FilterReply.NEUTRAL) { @@ -582,7 +643,6 @@ } else { throw new IllegalStateException("Unknown FilterReply value: " + decision); } - } public final boolean isErrorEnabled() { Modified: logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/HLogger.java ============================================================================== --- logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/HLogger.java (original) +++ logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/HLogger.java Thu May 3 20:45:07 2007 @@ -253,6 +253,29 @@ childHLogger.effectiveLevel = this.effectiveLevel; return childHLogger; } + + public final void trace(String msg) { + if (effectiveLevel.levelInt <= Level.TRACE_INT) { + throw new UnsupportedOperationException("not yet implemented"); + } + } + + public void trace(String msg, Throwable t) { + // To change body of implemented methods use File | Settings | File + // Templates. + } + + public void trace(Object parameterizedMsg, Object param1) { + // To change body of implemented methods use File | Settings | File + // Templates. + } + + public void trace(String parameterizedMsg, Object param1, Object param2) { + // To change body of implemented methods use File | Settings | File + // Templates. + } + + public final void debug(String msg) { if (effectiveLevel.levelInt <= Level.DEBUG_INT) { @@ -315,9 +338,12 @@ // Templates. } + public boolean isTraceEnabled() { + return false; + } + public boolean isDebugEnabled() { - return false; // To change body of implemented methods use File | Settings | - // File Templates. + return false; } public boolean isErrorEnabled() { @@ -355,6 +381,12 @@ // Templates. } + public void trace(String format, Object arg) { + } + + public void trace(String format, Object[] argArray) { + } + public void debug(String format, Object arg) { } Modified: logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/control/ControlLogger.java ============================================================================== --- logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/control/ControlLogger.java (original) +++ logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/control/ControlLogger.java Thu May 3 20:45:07 2007 @@ -61,6 +61,24 @@ return name.hashCode(); } + public final void trace(String o) { + if(getEffectiveLevel().levelInt <= Level.TRACE_INT ) { + throw new UnsupportedOperationException("not yet implemented"); + } + } + + public void trace(String msg, Throwable t) { + //To change body of implemented methods use File | Settings | File Templates. + } + + public void trace(String parameterizedMsg, Object param1) { + //To change body of implemented methods use File | Settings | File Templates. + } + + public void trace(String parameterizedMsg, Object param1, Object param2) { + //To change body of implemented methods use File | Settings | File Templates. + } + public final void debug(String o) { if(getEffectiveLevel().levelInt <= Level.DEBUG_INT ) { throw new UnsupportedOperationException("not yet implemented"); @@ -111,6 +129,10 @@ //To change body of implemented methods use File | Settings | File Templates. } + public boolean isTraceEnabled() { + return false; + } + public boolean isDebugEnabled() { return false; //To change body of implemented methods use File | Settings | File Templates. } @@ -143,6 +165,8 @@ //To change body of implemented methods use File | Settings | File Templates. } + public void trace(String format, Object[] argArray) { + } public void debug(String format, Object[] argArray) { } public void info(String format, Object[] argArray) {

1 0

svn commit: r1521 - logback/trunk
by noreply.ceki＠qos.ch 03 May '07

03 May '07

Author: ceki Date: Thu May 3 20:44:05 2007 New Revision: 1521 Modified: logback/trunk/pom.xml Log: correct reference to SLF4J version Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Thu May 3 20:44:05 2007 @@ -37,7 +37,7 @@ <properties>  - <slf4j.version>1.4-SNAPSHOT</slf4j.version> + <slf4j.version>1.4.0-SNAPSHOT</slf4j.version> <consolePlugin.version>1.0.1</consolePlugin.version> <retrotranslator.verify>false</retrotranslator.verify> </properties>

1 0

[continuum] BUILD FAILURE: Logback Classic Module
by John Noreplai 03 May '07

03 May '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Failed Previous State: Failed Started at: Thu, 3 May 2007 20:40:15 +0200 Finished at: Thu, 3 May 2007 20:40:19 +0200 Total time: 3s Build Trigger: Schedule Exit code: 1 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes ceki Fixed JMX related problem observed when running under JDK 1.4. For more details please see: http://marc.info/?l=logback-user&m=117766102225897&w=2 /logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/helpers/PlatformInfo.java /logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/joran/JoranConfigurator.java **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Classic Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] ------------------------------------------------------------------------ [ERROR] BUILD ERROR [INFO] ------------------------------------------------------------------------ [INFO] Failed to resolve artifact. Missing: ---------- 1) org.slf4j:slf4j-api:jar:1.4-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.slf4j -DartifactId=slf4j-api \ -Dversion=1.4-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) ch.qos.logback:logback-classic:jar:0.9.6-SNAPSHOT 2) org.slf4j:slf4j-api:jar:1.4-SNAPSHOT ---------- 1 required artifact is missing. for artifact: ch.qos.logback:logback-classic:jar:0.9.6-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 2 seconds [INFO] Finished at: Thu May 03 20:40:18 CEST 2007 [INFO] Final Memory: 12M/143M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

svn commit: r1520 - in logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic: helpers joran
by noreply.ceki＠qos.ch 03 May '07

03 May '07

Author: ceki Date: Thu May 3 20:33:27 2007 New Revision: 1520 Added: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/helpers/PlatformInfo.java Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/joran/JoranConfigurator.java Log: Fixed JMX related problem observed when running under JDK 1.4. For more details please see: http://marc.info/?l=logback-user&m=117766102225897&w=2 Added: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/helpers/PlatformInfo.java ============================================================================== --- (empty file) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/helpers/PlatformInfo.java Thu May 3 20:33:27 2007 @@ -0,0 +1,25 @@ +package ch.qos.logback.classic.helpers; + +/** + * This class provides information about the runtime platform. + * + * @author Ceki Gulcu + * */ +public class PlatformInfo { + + private static final int UNINITIALIZED = -1; + + private static int hasJMXObjectName = UNINITIALIZED; + + public static boolean hasJMXObjectName() { + if (hasJMXObjectName == UNINITIALIZED) { + try { + Class.forName("javax.management.ObjectName"); + hasJMXObjectName = 1; + } catch (Throwable e) { + hasJMXObjectName = 0; + } + } + return (hasJMXObjectName == 1); + } +} Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/joran/JoranConfigurator.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/joran/JoranConfigurator.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/joran/JoranConfigurator.java Thu May 3 20:33:27 2007 @@ -10,6 +10,7 @@ package ch.qos.logback.classic.joran; +import ch.qos.logback.classic.helpers.PlatformInfo; import ch.qos.logback.classic.joran.action.ConfigurationAction; import ch.qos.logback.classic.joran.action.ConsolePluginAction; import ch.qos.logback.classic.joran.action.EvaluatorAction; @@ -59,7 +60,12 @@ .addRule(new Pattern("configuration/appender/layout"), new LayoutAction()); - rs.addRule(new Pattern("configuration/jmxConfigurator"), new JMXConfiguratorAction()); + // add jmxConfigurator only if we have JMX available. + // If running under JDK 1.4 (retrotranslateed logback) then we + // might not have JMX. + if(PlatformInfo.hasJMXObjectName()) { + rs.addRule(new Pattern("configuration/jmxConfigurator"), new JMXConfiguratorAction()); + } rs.addRule(new Pattern("configuration/include"), new IncludeFileAction()); rs.addRule(new Pattern("configuration/consolePlugin"), new ConsolePluginAction());

1 0

[continuum] BUILD FAILURE: Logback Classic Module
by John Noreplai 03 May '07

03 May '07

Online report : http://localhost:8090/continuum/servlet/continuum/target/ProjectBuild.vm/vi… Build statistics: State: Failed Previous State: Failed Started at: Thu, 3 May 2007 17:00:19 +0200 Finished at: Thu, 3 May 2007 17:00:40 +0200 Total time: 21s Build Trigger: Schedule Exit code: 1 Building machine hostname: pixie Operating system : Linux(unknown) Java version : 1.5.0_08(Sun Microsystems Inc.) Changes ceki added one more test /logback/trunk/logback-classic/src/test/java/ch/qos/logback/classic/pattern/PackageTest.java **************************************************************************** Output: **************************************************************************** [INFO] Scanning for projects... [INFO] ---------------------------------------------------------------------------- [INFO] Building Logback Classic Module [INFO] task-segment: [clean, install] [INFO] ---------------------------------------------------------------------------- [INFO] [clean:clean] [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/classes [INFO] Deleting directory /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/test-classes [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] Compiling 89 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/classes [INFO] [retrotranslator:translate {execution: default}] [INFO] Transforming 90 file(s) from /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/classes to /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/logback-classic-0.9.6-SNAPSHOT-jdk14.jar. [INFO] Transformation of 90 file(s) completed successfully. [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 89 source files to /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/test-classes [INFO] [surefire:test] [INFO] Surefire report directory: /opt/continuum-1.0.3/apps/continuum/working-directory/46/target/surefire-reports ------------------------------------------------------- T E S T S ------------------------------------------------------- Running ch.qos.logback.classic.LoggerContextTest Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.043 sec Running ch.qos.logback.classic.pattern.ClassNameAbbreviatorTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running ch.qos.logback.classic.TurboFilteringInLoggerTest Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.075 sec Running ch.qos.logback.classic.pattern.MDCConverterTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Running ch.qos.logback.classic.PatternLayoutTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec Running ch.qos.logback.classic.MessageFormattingTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec Running ch.qos.logback.classic.pattern.ConverterTest Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.155 sec Running ch.qos.logback.classic.selector.ContextJNDISelectorTest MockInitialContextFactory static called Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec Running ch.qos.logback.classic.control.TestAction Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running ch.qos.logback.classic.DynamicLoggerContextTest Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.831 sec Running ch.qos.logback.classic.util.InitializationTest TEST 17:00:36.459 [main] DEBUG c.q.l.c.util.InitializationTest - Hello-didily-odily TEST 17:00:36.460 [main] DEBUG c.q.l.c.util.InitializationTest - Hello-didily-odily Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running ch.qos.logback.classic.db.DBAppenderTest [Server@2d5253d5]: [Thread[main,5,main]]: checkRunning(false) entered [Server@2d5253d5]: [Thread[main,5,main]]: checkRunning(false) exited [Server@2d5253d5]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@2d5253d5]: [Thread[main,5,main]]: checkRunning(false) entered [Server@2d5253d5]: [Thread[main,5,main]]: checkRunning(false) exited [Server@2d5253d5]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@6f25844f]: [Thread[main,5,main]]: checkRunning(false) entered [Server@6f25844f]: [Thread[main,5,main]]: checkRunning(false) exited [Server@6f25844f]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@6f25844f]: [Thread[main,5,main]]: checkRunning(false) entered [Server@6f25844f]: [Thread[main,5,main]]: checkRunning(false) exited [Server@6f25844f]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@bd10a5c]: [Thread[main,5,main]]: checkRunning(false) entered [Server@bd10a5c]: [Thread[main,5,main]]: checkRunning(false) exited [Server@bd10a5c]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@bd10a5c]: [Thread[main,5,main]]: checkRunning(false) entered [Server@bd10a5c]: [Thread[main,5,main]]: checkRunning(false) exited [Server@bd10a5c]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) [Server@47171b26]: [Thread[main,5,main]]: checkRunning(false) entered [Server@47171b26]: [Thread[main,5,main]]: checkRunning(false) exited [Server@47171b26]: [Thread[main,5,main]]: setDatabaseName(0,test) [Server@47171b26]: [Thread[main,5,main]]: checkRunning(false) entered [Server@47171b26]: [Thread[main,5,main]]: checkRunning(false) exited [Server@47171b26]: [Thread[main,5,main]]: setDatabasePath(0,mem:test;sql.enforce_strict_size=true) Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.836 sec Running ch.qos.logback.classic.joran.IncludeFileActionTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.048 sec Running ch.qos.logback.classic.html.HTMLLayoutTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.52 sec Running ch.qos.logback.classic.control.RandomUtilTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 sec Running ch.qos.logback.classic.turbo.MarkerFilterTest LOGBACK: No context given for ch.qos.logback.classic.turbo.MarkerFilter@62facf0b Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec Running ch.qos.logback.classic.net.SocketAppenderTest Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.622 sec Running ch.qos.logback.classic.control.ScenarioMakerTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.045 sec Running ch.qos.logback.classic.net.LoggingEventSerializationTest Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.014 sec Running ch.qos.logback.classic.control.CLCTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running ch.qos.logback.classic.selector.ContextDetachingSCLTest About to detach context named toto No context named toto was found. About to detach context named titi TEST 17:00:38.609 [main] WARN root - Shutting down context titi Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec Running ch.qos.logback.classic.MDCTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec Running ch.qos.logback.classic.BasicLoggerTest |-WARN in ch.qos.logback.core.read.ListAppender[null] - Attempted to append to non started appender [null]. Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 sec Running ch.qos.logback.classic.net.SMTPAppenderTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.23 sec Running ch.qos.logback.classic.boolex.JaninoEventEvaluatorTest Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.411 sec Running ch.qos.logback.classic.joran.EvaluatorJoranTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.024 sec Running ch.qos.logback.classic.spi.ContextListenerTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.007 sec Running ch.qos.logback.classic.pattern.MarkerConverterTest Tests run: 4, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec <<< FAILURE! Running ch.qos.logback.classic.net.JMSQueueAppenderTest Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.018 sec Running ch.qos.logback.classic.net.JMSTopicAppenderTest Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.561 sec Running ch.qos.logback.classic.net.SyslogAppenderTest Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.245 sec Running ch.qos.logback.classic.joran.BasicJoranTest |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.read.ListAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [LIST] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [LIST] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [LIST] to Logger[root] |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.read.ListAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [LIST] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [LIST] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - ch.qos.logback.classic.joran level set to INFO |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [LIST] to Logger[root] |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - Ignoring debug attribute. |-WARN in ch.qos.logback.classic.joran.action.EvaluatorAction - Assuming default evaluator class [ch.qos.logback.classic.boolex.JaninoEventEvaluator] |-INFO in ch.qos.logback.classic.joran.action.EvaluatorAction - Adding evaluator named [helloEval] to the object stack |-INFO in ch.qos.logback.core.joran.action.MatcherAction - matcher named as [m] |-INFO in ch.qos.logback.core.joran.action.MatcherAction - Popping appender named [m] from the object stack |-INFO in ch.qos.logback.classic.joran.action.EvaluatorAction - Starting evaluator named [helloEval] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.classic.StringListAppender] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STR_LIST] |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Popping appender named [STR_LIST] from the object stack |-INFO in ch.qos.logback.classic.joran.action.LevelAction - root level set to DEBUG |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STR_LIST] to Logger[root] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec Results : Tests run: 153, Failures: 3, Errors: 0, Skipped: 0 [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] There are test failures. [INFO] ------------------------------------------------------------------------ [INFO] For more information, run Maven with the -e switch [INFO] ------------------------------------------------------------------------ [INFO] Total time: 19 seconds [INFO] Finished at: Thu May 03 17:00:40 CEST 2007 [INFO] Final Memory: 19M/170M [INFO] ------------------------------------------------------------------------ ****************************************************************************

1 0

svn commit: r1519 - logback/trunk
by noreply.ceki＠qos.ch 03 May '07

03 May '07

Author: ceki Date: Thu May 3 17:00:35 2007 New Revision: 1519 Modified: logback/trunk/pom.xml Log: depend on SLF4J 1.4.0-SNAPSHOT (not yet released) Modified: logback/trunk/pom.xml ============================================================================== --- logback/trunk/pom.xml (original) +++ logback/trunk/pom.xml Thu May 3 17:00:35 2007 @@ -37,7 +37,7 @@ <properties>  - <slf4j.version>1.3.0</slf4j.version> + <slf4j.version>1.4-SNAPSHOT</slf4j.version> <consolePlugin.version>1.0.1</consolePlugin.version> <retrotranslator.verify>false</retrotranslator.verify> </properties>

1 0

svn commit: r1518 - logback/trunk/logback-site/src/site/pages/manual
by noreply.ceki＠qos.ch 03 May '07

03 May '07

Author: ceki Date: Thu May 3 16:55:39 2007 New Revision: 1518 Modified: logback/trunk/logback-site/src/site/pages/manual/layouts.html Log: ongoing work 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 Thu May 3 16:55:39 2007 @@ -1467,7 +1467,7 @@ <pattern>%relative%thread%mdc%level%class%msg</pattern> </layout> <From>sender.email(a)domain.net</From> - <SMTPHost>mail.domain.net"</SMTPHost> + <SMTPHost>mail.domain.net</SMTPHost> <Subject>LastEvent: %class - %msg </Subject> <To>destination.email(a)domain.net</To> </appender> @@ -1833,7 +1833,7 @@ </ul> <p>Here is a sample output produced by <code>HTMLLayout</code> in logback-access:</p> - <img src="images/chapter5/htmlLayoutAccess.gif" alt="Access HTML Layout Sample Image"/> + <img src="images/htmlLayoutAccess.gif" alt="Access HTML Layout Sample Image"/> <p>What is better than a real world example? Our own log4j properties to logback <a

1 0

svn commit: r1517 - logback/trunk/logback-site/src/site/resources/manual/images
by noreply.ceki＠qos.ch 03 May '07

03 May '07

Author: ceki Date: Thu May 3 16:54:40 2007 New Revision: 1517 Added: logback/trunk/logback-site/src/site/resources/manual/images/htmlLayout0.gif (contents, props changed) logback/trunk/logback-site/src/site/resources/manual/images/htmlLayout1.jpg (contents, props changed) Log: Added: logback/trunk/logback-site/src/site/resources/manual/images/htmlLayout0.gif ============================================================================== Binary file. No diff available. Added: logback/trunk/logback-site/src/site/resources/manual/images/htmlLayout1.jpg ============================================================================== Binary file. No diff available.

1 0

svn commit: r1516 - in logback/trunk/logback-site/src/site: pages pages/manual pages/templates resources/manual/images resources/manual/images/chapter5
by noreply.ceki＠qos.ch 03 May '07

03 May '07

Author: ceki Date: Thu May 3 16:45:15 2007 New Revision: 1516 Added: logback/trunk/logback-site/src/site/pages/templates/setup.js logback/trunk/logback-site/src/site/resources/manual/images/htmlLayoutAccess.gif - copied unchanged from r1501, /logback/trunk/logback-site/src/site/resources/manual/images/chapter5/htmlLayoutAccess.gif Removed: logback/trunk/logback-site/src/site/resources/manual/images/chapter5/htmlLayout1.gif logback/trunk/logback-site/src/site/resources/manual/images/chapter5/htmlLayoutAccess.gif Modified: logback/trunk/logback-site/src/site/pages/bridge.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/introduction.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/templates/creative.js logback/trunk/logback-site/src/site/pages/templates/right.js Log: improved docs Modified: logback/trunk/logback-site/src/site/pages/bridge.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/bridge.html (original) +++ logback/trunk/logback-site/src/site/pages/bridge.html Thu May 3 16:45:15 2007 @@ -80,7 +80,7 @@ </p> <p>We are happy to report that several applications are - using log4j-bridge in production with success. + successfully using log4j-bridge in production. </p> @@ -91,10 +91,10 @@ bridge. For example, direct references to log4j appenders, filters or PropertyConfigurator are not supported by log4j-bridge. While the number of cases where log4j-bridge is insufficient is - not negligible, in a large number of cases where log4j is - configured through a configuration file, be it + not completely negligible, in a vast majority of cases where log4j + is configured through a configuration file, be it <em>log4j.properties</em> or <em>log4j.xml</em>, log4j-bridge is - sufficient to migrate your application to logback. + enough in order to migrate youran application to logback. </p> <h3>What about the overhead?</h3> @@ -102,15 +102,13 @@ <p>There overhead of using log4j-bridge instead of log4j directly is relatively small. Given that log4j-bridge immediately delegates all work to logback, the CPU overhead should be negligible, in the - order of a few <em>nanoseconds</em>, i.e. neglible. There memory - overhead amount to an entry in a hasmap per logger, which should - be usually acceptable even for very large applications consisting - of several thousand loggers. Moreover, given that logback is both + order of a few <em>nanoseconds</em>. There is a memory overhead + corresponding to an entry in a hasmap per logger, which should be + usually acceptable even for very large applications consisting of + several thousand loggers. Moreover, given that logback is both much faster and more memory-efficient, the gains made by using logback should compensate for the overhead of using log4j-bridge instead of log4j directly.</p> - - <script src="templates/footer.js"></script> 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 Thu May 3 16:45:15 2007 @@ -39,16 +39,7 @@ <script src="../templates/creative.js"></script> - - <div class="highlight"> - <p> - In order to run the examples in this chapter, you need - to make sure that certain jar files are present on the - classpath. - Please refer to the <a href="../setup.html">setup page</a> - for further details. - </p> - </div> + <script src="../templates/setup.js"></script> <h2>What is an Appender?</h2> 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 Thu May 3 16:45:15 2007 @@ -767,15 +767,7 @@ log statements without the need to modify them manually. </p> - <div class="highlight"> - <p> - In order to run the examples in this introduction, you need - to make sure that certain jar files are present on the - classpath. - Please refer to the <a href="../setup.html">setup page</a> - for further details. - </p> - </div> + <script src="../templates/setup.js"></script> <p>The logback environment is fully configurable programmatically. However, it is far more flexible to configure logback using 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 Thu May 3 16:45:15 2007 @@ -35,13 +35,14 @@ <p>—KARL FRIEDRICH GAUSS, Letter to Bolyai, 1808.</p> - <p>Style, like sheer silk, too often hides eczema.</p> + <p><em>Style, like sheer silk, too often hides eczema.</em></p> <p>—ALBERT CAMUS, <em>The Fall</em></p> </div> <script src="../templates/creative.js"></script> + <script src="../templates/setup.js"></script> <h3>Introduction</h3> @@ -51,13 +52,15 @@ might reveal itself a tricky issue. </p> + + <p>Logback provides a simple yet powerful way of dealing with multiple contexts, without corruption of data, nor collusion between context instances. </p> <p>One thing we know is that JNDI environments are - independant. Thus setting environment variables in each + independent. Thus setting environment variables in each application will allow a given component to know which application it is dealing with at the moment. This is basically the mechanism that uses logback to provide easy access to the right 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 Thu May 3 16:45:15 2007 @@ -43,17 +43,9 @@ assembled or chained together to compose an arbitrarily complex filtering policy. </p> - - <div class="highlight"> - <p> - In order to run the examples in this chapter, you need - to make sure that certain jar files are present on the - classpath. - Please refer to the <a href="../setup.html">setup page</a> - for further details. - </p> - </div> - + + <script src="../templates/setup.js"></script> + <p> There are two main types of filters, namely <code>Filter</code> and <code>TurboFilter</code>. 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 Thu May 3 16:45:15 2007 @@ -59,15 +59,7 @@ <h2>First Baby Step</h2> - <div class="highlight"> - <p> - In order to run the examples in this introduction, you need - to make sure that certain jar files are present on the - classpath. - Please refer to the <a href="../setup.html">setup page</a> - for further details. - </p> - </div> + <script src="../templates/setup.js"></script> <a name="Requirements"></a> <h3>Requirements</h3> 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 Thu May 3 16:45:15 2007 @@ -2,7 +2,7 @@ <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Chapter3: Logback configuration</title> +<title>Chapter3: Logback configuration & 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" /> @@ -20,52 +20,42 @@ </div> <div id="content"> - <h1>Chapter 3: Logback configuration with Joran</h1> + <h1>Chapter 3: Logback configuration & Joran</h1> <div class="quote"> - <p>In symbols one observes an advantage in discovery which is - greatest when they express the exact nature of a thing briefly - and, as it were, picture it; then indeed the labor of thought is - wonderfully diminished. + <p><em>In symbols one observes an advantage in discovery which + is greatest when they express the exact nature of a thing + briefly and, as it were, picture it; then indeed the labor of + thought is wonderfully diminished.</em> </p> <p>—GOTTFRIED WILHELM LEIBNIZ</p> </div> - <script src="../templates/creative.js"></script> - - <div class="highlight"> - <p> - In order to run the examples in this chapter, you need - to make sure that certain jar files are present on the - classpath. - Please refer to the <a href="../setup.html">setup page</a> - for further details. - </p> - </div> + <script src="../templates/creative.js"></script> + <script src="../templates/setup.js"></script> <p>Joran stands for a cold north-west wind which, every now and - then, blows forcefully on Lake Leman, a.k.a lake Geneva. Located + then, blows forcefully on Lake Leman, a.k.a. lake Geneva. Located right in the middle of Europe, the Leman lake happens to be the continent's largest sweet water reserve. </p> <p>In the first part, we start by presenting ways for configuring logback, with many example configuration scripts. In the <a - href="#Joran"> second part</a>, we present Joran as a generic - configuration framework, and how you can use it to configure your - own applications. + href="#Joran">second part</a>, we present Joran, a generic + configuration framework, that you can put to use in order to + configure your own applications. </p> <h2>Configuration in logback</h2> - <p>Logback can be configured both programmatically or with - configuration script (in XML formal). Here are the steps that - logback follows to try to configure itself: + <p>Logback can be configured either programmatically or with + configuration a script (expressed in XML format). Here are the + initialization steps that logback follows to try to configure + itself: </p> - - <ol> <li> <p>Logback tries to find a file called <em>logback-test.xml</em> @@ -79,14 +69,13 @@ <li><p>In case neither file is found, logback configures itself automatically using the <a href="../xref/ch/qos/logback/classic/BasicConfigurator.html"><code>BasicConfigurator</code></a> - which will direct logging output on the console. </a></p> + which will cause output to be directed on the console. </a></p> </li> </ol> -  - - <p>The last step is meant to provide basic logging functionnality - in case no configuration file is provided. + <p>The third and last step is meant to provide a default (but very + basic) logging functionnality in case no configuration file could + be found. </p> @@ -101,10 +90,10 @@ <h3>Automatically configuring logback</h3> - <p>The simplest way to configure logback is by letting logback use - its <code>BasicConfigurator.configureDefaultContext()</code> - method. Let us give a taste of how this is done with the help of - an imaginary application called <code>MyApp1</code>. + <p>The simplest way to configure logback is by letting logback + fallback to its default configuration. Let us give a taste of how + this is done in an imaginary application called + <code>MyApp1</code>. </p> <em>Example 3.1: Simple example of <code>BasicConfigurator</code> usage @@ -126,59 +115,61 @@ } }</pre></div> -<p> -There is no invokation of the <code>BasicConfigurator</code> here, since logback -automatically calls it when no configuration files are found. It creates a rather -simple logback setup. This call is hardwired to add a <code>ConsoleAppender</code> to -the root logger. The output is formatting using a <code>PatternLayout</code> set to the -pattern <em>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n</em>. Note that -by default the root logger is assigned to the <code>DEBUG</code> level. -</p> - -<p> -The output of the command <em>java chapter3.MyApp1</em> should be similar to: -</p> + <p>Assuming the default configuration files + <em>logback-test.xml</em> and <em>logback.xml</em> could not be + found, logback will default to a minimal configuration hardwired + to add a <code>ConsoleAppender</code> to the root logger. The + output is formatted using a <code>PatternLayout</code> set to the + pattern <em>%d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - + %msg%n</em>. Moreover, by default the root logger is assigned to + the <code>DEBUG</code> level. + </p> + + <p>The output of the command <em>java chapter3.MyApp1</em> should + be similar to: + </p> <div class="source"><pre>16:06:09.031 [main] INFO chapter3.MyApp1 - Entering application. 16:06:09.046 [main] DEBUG chapter3.Foo - Did it again! 16:06:09.046 [main] INFO chapter3.MyApp1 - Exiting application.</pre></div> -<p> -If you are unable to run this command, then make sure that you have set -your classpath correctly. The scripts provided in the -<em>logback-examples/</em> directory will help you setting it up. -</p> - -<p> -As a side note, let us mention that in logback child loggers link only -to their existing ancestors. In particular, the logger named <em>chapter3.Foo</em> -is linked directly with the root logger, thereby circumventing the unused -<em>chapter3</em> logger. This noticeably improves the performance -of hierarchy walks and also slightly reduces logback's memory footprint -</p> + <p>If you are unable to run this command, then make sure that you + have set your classpath correctly. The scripts provided in the + <em>logback-examples/</em> directory should help you get started. + </p> + + <script src="../templates/setup.js"></script> + + <p>The <code>MyApp1</code> application links to logback through + calls <code>org.slf4j.LoggerFactory</code> and + <code>org.slf4j.Logger</code> classes, retrieve the loggers it + wishes to use, and chugs on. For example, the only dependence of + the <code>Foo</code> class on logback are through + <code>org.slf4j.LoggerFactory</code> and + <code>org.slf4j.Logger</code> imports. Except code that configures + logback (if such code exists) user code does not need to depend on + logback. Given that SLF4J permits the use of any implementation + under its abstraction layer, it is rather easy to migrate large + bodies of code from an implementation to another. Logback also + ships with a module called <em>log4j-bridge</em> which intercepts + log4j calls and redirects them to the corresponding logback + components. With the help of <em>log4j-bridge</em> , you can + migrate an entire application using log4j to logback just by + replacing jars. More information about the <em>log4j-bridge</em> + module can be found on a <a href="../bridge.html">separate + page</a>. + </p> + + <h3>The same with <code>JoranConfigurator</code></h3> + + <p>The previous example outputs logging information always in the + same fixed manner. How boring! It takes few easy steps to modify + <code>MyApp1</code> so that the log output can be controlled at + runtime. Here is a slightly modified version called + <code>MyApp2</code>. + </p> -<p> -The <code>MyApp1</code> class uses logback by calling the org.slf4j.LoggerFactory and -org.slf4j.Logger classes, retrieve the loggers it wishes to use, and log away. -For example, the only dependence of the <code>Foo</code> class on logback is the -org.slf4j.LoggerFactory and org.slf4j.Logger import. -Except code that configures logback (if such code exists) user code does not need to -depend on logback. Given that SLF4J permits the use of any implementation under its -abstraction layer, it is rather easy to migrate large bodies of code from an implementation -to another. Logback also ships with a module called <em>log4j-bridge</em> that intercepts -log4j calls and redirects them to the corresponding logback components. Thank to that module, -one can migrate an entire application using log4j to logback just by replacing jars. More -information about the <em>log4j-bridge</em> module in its -<a href="../bridge.html">specific documentation page</a>. -</p> - -<h3>The same using <code>JoranConfigurator</code></h3> - -<p> -The previous example outputs logging information always in the same fixed manner. -Fortunately, it is easy to modify <code>MyApp1</code> so that the log output can -be controlled at runtime. Here is a slightly modified version called <code>MyApp2</code>. -</p> + <em>Example 3.2: Simple example of <code>BasicConfigurator</code> usage <a href="../xref/chapter3/MyApp2.html">(logback-examples/src/main/java/chapter3/MyApp2.java)</a></em> <div class="source"><pre>package chapter3; @@ -189,6 +180,7 @@ import ch.qos.logback.classic.LoggerContext; import ch.qos.logback.classic.joran.JoranConfigurator; import ch.qos.logback.core.joran.spi.JoranException; +import ch.qos.logback.core.util.StatusPrinter; public class MyApp2 { final static Logger logger = LoggerFactory.getLogger(MyApp2.class); @@ -197,12 +189,12 @@ LoggerContext lc = (LoggerContext) LoggerFactory.getILoggerFactory(); try { - <b>JoranConfigurator configurator = new JoranConfigurator(); +<b> JoranConfigurator configurator = new JoranConfigurator(); configurator.setContext(lc); lc.shutdownAndReset(); configurator.doConfigure(args[0]);</b> } catch (JoranException je) { - je.printStackTrace(); + StatusPrinter.print(lc); } logger.info("Entering application."); 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 Thu May 3 16:45:15 2007 @@ -31,16 +31,8 @@ </div> <script src="../templates/creative.js"></script> - - <div class="highlight"> - - <p>In order to run the examples in this chapter, you need to make - sure that certain jar files are present on the classpath. Please - refer to the <a href="../setup.html">setup page</a> for further - details. - </p> - </div> - + <script src="../templates/setup.js"></script> + <h2>What is a layout?</h2> <p>While appenders are responsible for writing logging output to @@ -287,7 +279,7 @@ </p> - <a name="PatternLayout"></a> + <a name="ClassicPatternLayout"></a> <h3>PatternLayout</h3> <p> @@ -1351,40 +1343,86 @@ <p>Here is a sample output produced by <code>HTMLLayout</code> using its default CSS stylesheet:</p> - <img src="images/chapter5/htmlLayout1.gif" alt="HTML Layout Sample Image"/> + <img src="images/htmlLayout0.gif" alt="HTML Layout Sample Image"/> <p>The content of table columns are specified with the help of a conversion pattern. See <a - href="#PatternLayout"><code>PatternLayout</code></a> for - documentation on conversion patterns. Thus, the user has full - control over the contents and format of the table. You can display - any one of the converters <code>PatternLayout</code> knows about. + href="#ClassicPatternLayout"><code>PatternLayout</code></a> for + documentation on conversion patterns. As such, you have full + control over the contents and format of the table. You can select + and display any combination of converters + <code>PatternLayout</code> knows about. </p> - <p>One notable point about the use of <code>PatternLayout</code> - with <code>HTMLLayout</code> is that conversion specifiers should - not be separated by a space or in general any literals. Each - specifier found in the pattern will result in a separate column, - in particular each literal in the pattern. + <p>One notable exception about the use of + <code>PatternLayout</code> with <code>HTMLLayout</code> is that + conversion specifiers should not be separated by space characters + or more generally by literal text. Each specifier found in the + pattern willa result in a separate column, in particular for each + literal text in the pattern, wasting valuable real estate on your + screen. </p> - <p>The pattern <em>%ex</em> used to display exceptions is not the - only way to display them. If you use the <em>%em</em> conversion - word, a table column will be created to display exception stack - traces. In most cases the column will be empty, wasting valuable - real-estate on your screen. + <p>Here is simple but functional configuration file illustrating + the use of <code>HTMLLayout</code>. + </p> + +<div class="source"><configuration debug="true"> + <appender name="FILE" class="ch.qos.logback.core.FileAppender"> + <layout class="ch.qos.logback.classic.html.HTMLLayout"> + <b><pattern>%relative%thread%mdc%level%logger%msg</pattern></b> + </layout> + <File>/test.html</File> + </appender> + + <root> + <level value="debug" /> + <appender-ref ref="FILE" /> + </root> +</configuration> +</div> + + <p>Launching the <code>TrivialMain</code> application listed below + will create the file <em>test.html</em> on your local drive.</p> + +<div class="source">import org.slf4j.Logger; +import org.slf4j.LoggerFactory; + +public class TrivialMain { + public static void main(String[] args) throws InterruptedException { + Logger logger = LoggerFactory.getLogger(TrivialMain.class); + for(int i = 0; i < 6; i ++) { + if(i % 5 == 0) { + logger.info("an info message "+i); + } else { + logger.debug("hello world number" +i); + } + } + logger.error("Finish off with fireworks", new Exception("Just testing")); + } +}</div> + + <p>The contents of <em>test.html</em> should be similar to: </p> + <img src="images/htmlLayout1.jpg" alt="HTML Layout Sample Image"/> - <p> - Moreover, printing a stack trace on a separate column does yield - very readable results. A better solution is available in the - form of implementations of the <code>IThrowableRenderer</code> - interface. Such an implementation can assigned to - <code>HTMLLayout</code> to manage the display data related to - exceptions. By default, a - <a href="../xref/ch/qos/logback/classic/html/DefaultThrowableRenderer.html"> + <h3>Stack traces</h3> + + <p> If you use the <em>%em</em> conversion word, to display stack + traces, a table column will be created to display exception stack + traces. In most cases the column will be empty, wasting screen + real-estate. Moreover, printing a stack trace on a separate column + does yield very readable results. Fortunately, the <em>%ex</em> + conversion word is not the only way to display stack traces. + </p> + + <p>A better solution is available through implementations of + <code>IThrowableRenderer</code> interface. Such an implementation + can assigned to <code>HTMLLayout</code> to manage the display data + related to exceptions. By default, a + <a href="../xref/ch/qos/logback/classic/html/DefaultThrowableRenderer.html"> <code>DefaultThrowableRenderer</code></a> is assigned to each - <code>HTMLLayout</code> isntance. It writes exceptions on a + <code>HTMLLayout</code> instance. It writes exceptions on a <em>new table row</em>, along with its stacktrace, in an easily readable manner, as shown on the figure above. </p> @@ -1394,25 +1432,30 @@ <a href="../xref/ch/qos/logback/core/html/NOPThrowableRenderer.html"> <code>NOPThrowableRenderer</code></a> in the configuration file in order to disable displaying a separate row for the stack - trace. + trace. We don't have the faintest idea why you would want to do + that, but if you did, you could. </p> - <p>A user-specified external CSS file can be set as the - style-sheet of the HTML output. For this purpose, a - <code>cssBuilder</code> xml element can be nested within a - <code><layout></code> element, as shown below. + <h3>CSS</h3> + + <p>The presentation of the HTML created by <code>HTMLLayout</code> + is controlled through a Cascading Style Sheet (CSS). In the + absence of specific instructions, <code>HTMLLayout</code> will + default to its internal CSS. However, your can instruct + <code>HTMLLayout</code> you use an external CSS file. For this + purpose, a <code>cssBuilder</code> element can be nested within a + <code><layout></code> element, as shown below. </p> <div class="source"><pre><layout> ... <cssBuilder class="ch.qos.logback.core.html.UrlCssBuilder"> - <param name="url" value="path_to_StyleFile.css" /> + <url>path_to_StyleFile.css</url> </cssBuilder> ... </layout></pre></div> - <p>By default, an internal CSS style is used.</p> - + <p>The <code>HTMLLayout</code> is often used in conjunction with <code>SMTPAppender</code>, in order to send an email pleasantly formatted in HTML. Here is a typical configuration: @@ -1421,12 +1464,12 @@ <div class="source"><pre><configuration> <appender name="SMTP" class="ch.qos.logback.classic.net.SMTPAppender"> <layout class="ch.qos.logback.classic.html.HTMLLayout"> - <param name="pattern" value="%relative%thread%mdc%level%class%msg" /> + <pattern>%relative%thread%mdc%level%class%msg</pattern> </layout> - <param name="From" value="sender.email(a)domain.net" /> - <param name="SMTPHost" value="mail.domain.net" /> - <param name="Subject" value="LastEvent: %class - %msg" /> - <param name="To" value="destination.email(a)domain.net" /> + <From>sender.email(a)domain.net</From> + <SMTPHost>mail.domain.net"</SMTPHost> + <Subject>LastEvent: %class - %msg </Subject> + <To>destination.email(a)domain.net</To> </appender> <root> @@ -1772,10 +1815,12 @@ <a name="AccessHTMLLayout"></a> <h3>HTMLLayout</h3> - <p>The access version of - <a href="../xref/ch/qos/logback/access/html/HTMLLayout.html"> - <code>HTMLLayout</code></a> works like logback classic's - version.</p> + <p>The <a + href="../xref/ch/qos/logback/access/html/HTMLLayout.html"><code>HTMLLayout</code></a> + class found in logback-access is similar to the <a + href="#ClassicHTMLLayout"><code>HTMLLayout</code></a> class found + in logback-classic. + </p> <p>By default, it will create a table containing the following data:</p> 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 Thu May 3 16:45:15 2007 @@ -40,23 +40,16 @@ and considerably increases their management overhead. </p> - <div class="highlight"> - <p> - In order to run the examples in this chapter, you need - to make sure that certain jar files are present on the - classpath. - Please refer to the <a href="../setup.html">setup page</a> - for further details. - </p> - </div> + <script src="../templates/setup.js"></script> + - <p> - A lighter technique consists of uniquely stamping each - log request servicing a given client. Neil Harrison described this method in the book - <em>Patterns for Logging Diagnostic Messages</em> in - Pattern Languages of Program Design 3, edited by R. Martin, D. Riehle, - and F. Buschmann (Addison-Wesley, 1997). Logback offers a variant of this technique: - Mapped Diagnostic Contexts (MDC). + <p>A lighter technique consists of uniquely stamping each log + request servicing a given client. Neil Harrison described this + method in the book <em>Patterns for Logging Diagnostic + Messages</em> in Pattern Languages of Program Design 3, edited by + R. Martin, D. Riehle, and F. Buschmann (Addison-Wesley, + 1997). Logback offers a variant of this technique: Mapped + Diagnostic Contexts (MDC). </p> <p> Modified: logback/trunk/logback-site/src/site/pages/templates/creative.js ============================================================================== --- logback/trunk/logback-site/src/site/pages/templates/creative.js (original) +++ logback/trunk/logback-site/src/site/pages/templates/creative.js Thu May 3 16:45:15 2007 @@ -5,7 +5,7 @@ document.write(' <p class="author">'); document.write(' Authors: Ceki Gülcü, Sébastien Pennec'); document.write(' <br/>'); -document.write(' Copyright © 2000-2006, QOS.ch</p>'); +document.write(' Copyright © 2000-2007, QOS.ch</p>'); document.write(' </td>'); document.write(' <td>'); document.write(' <a rel="license"'); Modified: logback/trunk/logback-site/src/site/pages/templates/right.js ============================================================================== --- logback/trunk/logback-site/src/site/pages/templates/right.js (original) +++ logback/trunk/logback-site/src/site/pages/templates/right.js Thu May 3 16:45:15 2007 @@ -3,8 +3,9 @@ document.write('<p class="menu_header">New and noteworthy</p>') -document.write('<p class="menu"><a href="http://xhab.blogspot.com/2007/03/new-logging-experience.html">A new logging experience!</a>') +document.write('<p class="menu"><a href="http://www.javadonkey.com/blog/log4j-isdebugenabled-logback/">isDebugEnabled()</a>') +document.write('<p class="menu"><a href="http://xhab.blogspot.com/2007/03/new-logging-experience.html">A new logging experience!</a>') document.write('<p class="menu"><a href="http://javablog.smilehouse.com/blog/default/Java/2007/02/02/Writing-rotated…">Writing rotated and compressed access logs</a>') Added: logback/trunk/logback-site/src/site/pages/templates/setup.js ============================================================================== --- (empty file) +++ logback/trunk/logback-site/src/site/pages/templates/setup.js Thu May 3 16:45:15 2007 @@ -0,0 +1,10 @@ + +document.write(' <div class="highlight">'); +document.write(' <p>'); +document.write(' In order to run the examples in this chapter, you need'); +document.write(' to make sure that certain jar files are present on the'); +document.write(' classpath.'); +document.write(' Please refer to the <a href="../setup.html">setup page</a>'); +document.write(' for further details.'); +document.write(' </p>'); +document.write(' </div>'); \ No newline at end of file

1 0