February 2007 - logback-dev

[Bug 8] New: The insertion of a percent symbol causes the Parser to crash
by bugzilla-daemon＠pixie.qos.ch 19 Mar '08

19 Mar '08

http://bugzilla.qos.ch/show_bug.cgi?id=8 Summary: The insertion of a percent symbol causes the Parser to crash Product: logback-core Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Pattern AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.sebastien(a)qos.ch When inserting the percent char twice, so that it appears in the PatternLayout output, a number format exception is thrown. It does not prevent from using normally the PatternLayout. trace: ERROR in ch.qos.logback.core.joran.spi.Interpreter@131f71a - Exception in Action for tag <layout>8:14 java.lang.NumberFormatException: For input string: "% %" java.lang.NumberFormatException: For input string: "% %" at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48) at java.lang.Integer.parseInt(Integer.java:447) at java.lang.Integer.parseInt(Integer.java:497) at ch.qos.logback.core.pattern.FormatInfo.valueOf(FormatInfo.java:70) at ch.qos.logback.core.pattern.parser.Parser.T(Parser.java:84) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:51) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.Eopt(Parser.java:107) at ch.qos.logback.core.pattern.parser.Parser.E(Parser.java:55) at ch.qos.logback.core.pattern.parser.Parser.parse(Parser.java:31) at ch.qos.logback.core.pattern.PatternLayoutBase.start(PatternLayoutBase.java:76) at ch.qos.logback.core.joran.action.AbstractLayoutAction.end(AbstractLayoutAction.java:75) at ch.qos.logback.core.joran.spi.Interpreter.callEndAction(Interpreter.java:289) at ch.qos.logback.core.joran.spi.Interpreter.endElement(Interpreter.java:152) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:633) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1242) at javax.xml.parsers.SAXParser.parse(SAXParser.java:375) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:125) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:101) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:84) at ch.qos.logback.core.joran.JoranConfiguratorBase.doConfigure(JoranConfiguratorBase.java:77) at mainPackage.ConfigTester.main(ConfigTester.java:21) -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 5

[Bug 38] New: Display a message when used behind slf4j
by bugzilla-daemon＠pixie.qos.ch 21 Aug '07

21 Aug '07

http://bugzilla.qos.ch/show_bug.cgi?id=38 Summary: Display a message when used behind slf4j Product: logback-general Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P1 Component: build-structure AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.sebastien(a)qos.ch Logback should display a message when it is used as SLF4J's implementation. We should find a way to tell the user that it's logback that is being used, without polluting any output. -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 1

[Bug 39] New: Introduce concept of MDC as soon ass they are referenced
by bugzilla-daemon＠pixie.qos.ch 21 Aug '07

21 Aug '07

http://bugzilla.qos.ch/show_bug.cgi?id=39 Summary: Introduce concept of MDC as soon ass they are referenced Product: logback-site Version: unspecified Platform: PC OS/Version: Windows Status: NEW Severity: normal Priority: P3 Component: Documentation AssignedTo: logback-dev(a)qos.ch ReportedBy: xavier.hanin(a)gmail.com While reading the documentation I had the feeling that MDC was introduced too late. Indeed, you reference MDC the first time in chapter 2 (as far as I can say), without giving even an hint on what it is. Several other chapters reference this concept, but it's only in chapter 7 that I understood what it is. Maybe adding a short introduction to this concept (and the concept of Marker) in chapter 2 would help the reader? -- Configure bugmail: http://bugzilla.qos.ch/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

1 2

svn commit: r1375 - logback/trunk/logback-site/src/site/pages
by noreply.ceki＠qos.ch 28 Feb '07

28 Feb '07

Author: ceki Date: Wed Feb 28 22:48:56 2007 New Revision: 1375 Modified: logback/trunk/logback-site/src/site/pages/index.html Log: correct version 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 Wed Feb 28 22:48:56 2007 @@ -2,107 +2,56 @@ <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Logback Manual</title> -<link rel="stylesheet" type="text/css" media="screen" href="../css/site.css" /> +<title>Logback Home</title> +<link rel="stylesheet" type="text/css" media="screen" href="css/site.css" /> </head> <body> - <script> -prefix='../'; + <script> +prefix=''; </script> -<script src="../templates/header.js"></script> + +<script src="templates/header.js"></script> <div id="left"> - <script src="../templates/left.js"></script> + <script src="templates/left.js"></script> </div> <div id="right"> - <script src="../templates/right.js"></script> + <script src="templates/right.js"></script> </div> <div id="content"> - <h2>The logback manual</h2> + + <h2>Logback Project</h2> + <p> + Logback is intended as a successor to the popular log4j + project. It was designed by Ceki Gülcü, the founder of the + log4j project. It builds upon exerience gained in building + industrial-strength logging systems going back as far as 1999. + </p> + <p> + Logback's basic architecture is sufficiently generic so as to + apply under different circumstances. At present time, logback is + divided into three modules, logback-core, logback-classic and + logback-access. + </p> - <p>The complete logback manual documents the latest version of - logback framework. In over 140 pages and dozens of concrete - examples, it covers both basic and advanced logback features: + <p> + The logback-core module lays the groundwork for the other two + modules. The logback-classic module can be assimilated to a + significantly improved version of log4j. Moreover, + logback-classic natively implements the <a + href="http://www.slf4j.org">SLF4J API</a> so that you can + readily switch back and forth between logback and other logging + systems such as log4j or JDK14 Logging. </p> - <div> - <ul> - <li><p>the overall logback architecture</p></li> - <li><p>discussion of best logback practices and anti-patterns</p></li> - <li><p>logback configuration scripts in XML format</p></li> - <li><p>appenders</p></li> - <li><p>layouts</p></li> - <li><p>filter chains</p></li> - <li><p>logback diagnostic contexts</p></li> - <li><p>logback default initialization</p></li> - <li><p>logback in Servlet Containers</p></li> - </ul> - </div> - - - <div class="highlight"> - <p> - If you wish to print chapters in this document, we recommend - that you do so using <a - href="http://www.getfirefox.com">Firefox 2</a>, with <em>Adapt to - page size</em> enabled, or <a - href="http://www.opera.com">Opera</a>. - </p> <p> - To run the examples provided in this book, you might have - to run the provided script to setup your classpath. The scripts - can be found in the logback distributions, inside the <em>logback-examples</em> - directory. - </p> - </div> - - <p>The logback manual describes the logback API in considerable - detail, including its features and design rationale. Authored by - Ceki Gülcü and Sébastien Pennec, the main - contributors to the logback project, the logback manual is - intended for developers already familiar with the Java language - but new to logback, as much as for experienced logback users. With - the aid of introductory material and many examples, new users - should quickly come up to speed. - </p> - - <div> - <p>Without further ado, here are the contents of the manual:</p> - - <ul> - <li><p> - <a href="introduction.html"><b>Chapter 1: Introduction to logback</b></a> - </p></li> - <li><p> - <a href="architecture.html"><b>Chapter 2: Architecture</b></a> - </p></li> - <li><p> - <a href="joran.html"><b>Chapter 3: Logback configuration with Joran</b></a> - </p></li> - - <li><p> - <a href="appenders.html"><b>Chapter 4: Appenders</b></a> - </p></li> - - <li><p> - <a href="layouts.html"><b>Chapter 5: Layouts</b></a> - </p></li> - - <li><p> - <a href="filters.html"><b>Chapter 6: Filter chains</b></a> - </p></li> - - <li><p> - <a href="mdc.html"><b>Chapter 7: Diagnostic Context</b></a> - </p></li> + The Access module integrates with Servlet containers to + provide HTTP-access log functionality. Note that you can + easily build your own modules on top of the Core module. + </p> - <li><p> - <a href="contextSelector.html"><b>Chapter 8: Context Selector</b></a> - </p></li> - - </ul> - </div> -<script src="../templates/footer.js"></script> + + </div> </body> </html>

1 0

svn commit: r1374 - in logback/trunk/logback-site/src/site: pages/images pages/templates resources/css resources/images resources/templates
by noreply.ceki＠qos.ch 28 Feb '07

28 Feb '07

Author: ceki Date: Wed Feb 28 22:43:01 2007 New Revision: 1374 Added: logback/trunk/logback-site/src/site/pages/images/ - copied from r1371, /logback/trunk/logback-site/src/site/resources/images/ logback/trunk/logback-site/src/site/pages/templates/ - copied from r1371, /logback/trunk/logback-site/src/site/resources/templates/ Removed: logback/trunk/logback-site/src/site/resources/css/ logback/trunk/logback-site/src/site/resources/images/ logback/trunk/logback-site/src/site/resources/templates/ Log: moving files from resources/ to pages/

1 0

svn commit: r1373 - in logback/trunk/logback-site/src/site: pages pages/manual/images resources/manual/images
by noreply.ceki＠qos.ch 28 Feb '07

28 Feb '07

Author: ceki Date: Wed Feb 28 22:40:56 2007 New Revision: 1373 Added: logback/trunk/logback-site/src/site/pages/manual/images/ - copied from r1371, /logback/trunk/logback-site/src/site/resources/manual/images/ Removed: logback/trunk/logback-site/src/site/resources/manual/images/ Modified: logback/trunk/logback-site/src/site/pages/index.html Log: moving manual/images 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 Wed Feb 28 22:40:56 2007 @@ -2,54 +2,107 @@ <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="content-type" content="text/html; charset=iso-8859-1" /> -<title>Logback Home</title> -<link rel="stylesheet" type="text/css" media="screen" href="css/site.css" /> +<title>Logback Manual</title> +<link rel="stylesheet" type="text/css" media="screen" href="../css/site.css" /> </head> <body> - <script> -prefix=''; + <script> +prefix='../'; </script> - -<script src="templates/header.js"></script> +<script src="../templates/header.js"></script> <div id="left"> - <script src="templates/left.js"></script> + <script src="../templates/left.js"></script> </div> <div id="right"> - <script src="templates/right.js"></script> + <script src="../templates/right.js"></script> </div> <div id="content"> - - <h2>Logback Project</h2> - <p> - Logback is intended as a successor to the popular log4j - project. It was designed by Ceki Gülcü, the founder of the - log4j project. It builds upon exerience gained in building - industrial-strength logging systems going back as far as 1999. - </p> - <p> - Logback's basic architecture is sufficiently generic so as to - apply under different circumstances. At present time, logback is - divided into three modules, logback-core, logback-classic and - logback-access. - </p> + <h2>The logback manual</h2> - <p> - The logback-core module lays the groundwork for the other two - modules. The logback-classic module can be assimilated to a - significantly improved version of log4j. Moreover, - logback-classic natively implements the <a - href="http://www.slf4j.org">SLF4J API</a> so that you can - readily switch back and forth between logback and other logging - systems such as log4j or JDK14 Logging. + <p>The complete logback manual documents the latest version of + logback framework. In over 140 pages and dozens of concrete + examples, it covers both basic and advanced logback features: + </p> - The Access module integrates with Servlet containers to - provide HTTP-access log functionality. Note that you can - easily build your own modules on top of the Core module. - </p> + <div> + <ul> + <li><p>the overall logback architecture</p></li> + <li><p>discussion of best logback practices and anti-patterns</p></li> + <li><p>logback configuration scripts in XML format</p></li> + <li><p>appenders</p></li> + <li><p>layouts</p></li> + <li><p>filter chains</p></li> + <li><p>logback diagnostic contexts</p></li> + <li><p>logback default initialization</p></li> + <li><p>logback in Servlet Containers</p></li> + </ul> + </div> - - + + <div class="highlight"> + <p> + If you wish to print chapters in this document, we recommend + that you do so using <a + href="http://www.getfirefox.com">Firefox 2</a>, with <em>Adapt to + page size</em> enabled, or <a + href="http://www.opera.com">Opera</a>. + </p> + <p> + To run the examples provided in this book, you might have + to run the provided script to setup your classpath. The scripts + can be found in the logback distributions, inside the <em>logback-examples</em> + directory. + </p> + </div> + + <p>The logback manual describes the logback API in considerable + detail, including its features and design rationale. Authored by + Ceki Gülcü and Sébastien Pennec, the main + contributors to the logback project, the logback manual is + intended for developers already familiar with the Java language + but new to logback, as much as for experienced logback users. With + the aid of introductory material and many examples, new users + should quickly come up to speed. + </p> + + <div> + <p>Without further ado, here are the contents of the manual:</p> + + <ul> + <li><p> + <a href="introduction.html"><b>Chapter 1: Introduction to logback</b></a> + </p></li> + <li><p> + <a href="architecture.html"><b>Chapter 2: Architecture</b></a> + </p></li> + <li><p> + <a href="joran.html"><b>Chapter 3: Logback configuration with Joran</b></a> + </p></li> + + <li><p> + <a href="appenders.html"><b>Chapter 4: Appenders</b></a> + </p></li> + + <li><p> + <a href="layouts.html"><b>Chapter 5: Layouts</b></a> + </p></li> + + <li><p> + <a href="filters.html"><b>Chapter 6: Filter chains</b></a> + </p></li> + + <li><p> + <a href="mdc.html"><b>Chapter 7: Diagnostic Context</b></a> + </p></li> + + <li><p> + <a href="contextSelector.html"><b>Chapter 8: Context Selector</b></a> + </p></li> + + </ul> + </div> +<script src="../templates/footer.js"></script> </div> </body> </html>

1 0

svn commit: r1372 - in logback/trunk/logback-site/src/site/pages: css manual
by noreply.ceki＠qos.ch 28 Feb '07

28 Feb '07

Author: ceki Date: Wed Feb 28 22:30:52 2007 New Revision: 1372 Modified: logback/trunk/logback-site/src/site/pages/css/site.css 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/layouts.html Log: ongoing work on the documentaiton Modified: logback/trunk/logback-site/src/site/pages/css/site.css ============================================================================== --- logback/trunk/logback-site/src/site/pages/css/site.css (original) +++ logback/trunk/logback-site/src/site/pages/css/site.css Wed Feb 28 22:30:52 2007 @@ -24,6 +24,7 @@ div.source { margin-top: 1em; } + .source { border-top: 1px solid #DDDDDD; border-bottom: 1px solid #DDDDDD; @@ -35,6 +36,17 @@ white-space: pre; } +.command { + border-top: 1px solid #DDDDDD; + border-bottom: 1px solid #DDDDDD; + background:#eee; + font-family: Courier, "MS Courier New", Prestige, Everson Monocourrier, monospace; + padding-bottom: 0ex; + padding-top: 0ex; + padding-left: 1ex; + white-space: pre; +} + pre { padding: 0px; margin: 0px; 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 Wed Feb 28 22:30:52 2007 @@ -21,7 +21,7 @@ <h2>The logback manual</h2> <p>The complete logback manual documents the latest version of - logback framework. In over 100 pages and dozens of concrete + logback framework. In over 140 pages and dozens of concrete examples, it covers both basic and advanced logback features: </p> 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 Wed Feb 28 22:30:52 2007 @@ -57,20 +57,20 @@ <p> Logback is intended as a successor to the popular log4j project. - It was designed by Ceki Gülcü, the log4j founder. - It builds upon a decade long experience gained in - designing industrial-strength logging systems. The resulting - product, logback is faster with a smaller footprint than all - existing logging systems, sometimes by a wide margin. Logback - also offers unique and rather useful features such as Markers, - parameterized logging statements, conditional stack tracing and - powerful event filtering. These are only few examples of useful - features logback has to offer. For its own error reporting, - logback relies on <code>Status</code> objects, which greatly - facilitate troubleshooting. You may wish to rely on Status - objects in contexts other than logging. Logback-core bundles - Joran, a powerful and generic configuration system, which can be - put to use in your own projects to great effect. + It was designed by Ceki Gülcü, log4j's founder. It + builds upon a decade long experience gained in designing + industrial-strength logging systems. The resulting product, + logback is faster with a smaller footprint than all existing + logging systems, sometimes by a wide margin. Logback also offers + unique and rather useful features such as Markers, parameterized + logging statements, conditional stack tracing and powerful event + filtering. These are only few examples of useful features + logback has to offer. For its own error reporting, logback + relies on <code>Status</code> objects, which greatly facilitate + troubleshooting. You may wish to rely on Status objects in + contexts other than logging. Logback-core bundles Joran, a + powerful and generic configuration system, which can be put to + use in your own projects to great effect. </p> <h2>First Baby Step</h2> @@ -239,30 +239,27 @@ <a name="BuildingLogback"></a> <h3>Building logback</h3> -<p> -Like many java applications today, logback relies on <a href="http://maven.apache.org"> -Maven 2</a> as its build tool. Maven 2 is a free open source build tool that requires -one or more build files names <em>pom.xml</em> which already ship with logback -distributions. -</p> - -<p> -Building all logback components is mostly done by issuing the <em>mvn compile</em> -line in a terminal or command window. Maven 2 will automatically download the required -external libraries and use them. However, a library cannot be downloaded from -the Maven 2 repository. Libraries such as <code>JMS</code> -from sun require a separate download and to issue a command to install their -jars into your local repository. The required command will be presented -by Maven 2 in your console when trying to compile logback. -</p> - -<p> -Logback distributions contain complete source code such that you can modify parts -of logback library and build your own version of it. You may even -redistribute the modified version, as long as you adhere to the conditions -of the LGPL License. In particular you may not call the modified version <em>logback</em> -or claim that it is endorsed by the QOS.ch. -</p> + <p>Like many java applications today, logback relies on <a + href="http://maven.apache.org"> Maven 2</a> as its build tool. Maven + 2 is a free open source build tool that requires one or more build + files names <em>pom.xml</em> which already ship with logback + distributions. + </p> + + <p>Building all logback modules is mostly done by issuing the + <em>mvn package</em> line in a terminal or command window. Maven + will automatically download the required external libraries and use + them. However, certain artefacts cannot be downloaded from the + Maven2 repository. Libraries such as <code>JMS</code> from SUN Inc. + need to be downloaded and installed separately into your local + repository. + </p> + + <p>Logback distributions contain complete source code such that you + can modify parts of logback library and build your own version of + it. You may even redistribute the modified version, as long as you + adhere to the conditions of the LGPL License. + </p> 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 Wed Feb 28 22:30:52 2007 @@ -143,42 +143,49 @@ }</pre></div> <p> - Note that - <code>MySampleLayout</code> - extends <a href="../xref/ch/qos/logback/core/LayoutBase.html"> - <code>LayoutBase</code></a>. - This class manages trivial components of a <code>Layout</code> - such as started or stopped status, header, footer and - content type access or logging context awareness. It allows - the developer to concentrate on the formatting she expects - from her <code>Layout</code>. Note that the <code>LayoutBase</code> - class is generic. By extending it, we precise the type that it will - have to handle, by adding <em><LoggingEvent></em> after its declaration. - </p> - - <p>The marginally more interesting <code>doLayout(LoggingEvent event)</code> - method begins by instantiating a StringBuffer. It proceeds by adding various - fields of the event parameter. The Texan from Texas was careful to print - the formatted form of the message and not its object form. - This allows for logging requests which are passed object arrays to - build the message in its proper form. - </p> - <p> - In the above listing of the <code>Layout</code> class, - we had omitted the class static <code>LINE_SEP</code> - field which is simply assigned the value returned by - <code>System.getProperty("line.separator")</code> - method. After adding system dependent line separator - character(s), the format method returns the string buffer as - a String. - </p> - <p> - The <code>doLayout</code> method ignores any eventual exceptions contained - in the event. In a real world layout implementation, you would probably not want - to silently ignore exceptions. + Note that <code>MySampleLayout</code> extends <a + href="../xref/ch/qos/logback/core/LayoutBase.html"> + <code>LayoutBase</code></a>. This class manages state shared by + all <code>Layout</code> classes, such as whether the layout is + started or stopped, header, footer and content type data. It + allows the developer to concentrate on the formatting she + expects from her <code>Layout</code>. Note that the + <code>LayoutBase</code> class is generic. In its class + declaration, <code>MySampleLayout</code> extends a typed + <code>LayoutBase</code>, + <code>LayoutBase<LoggingEvent></code>, instead of generic + one. + </p> + + <p>The <code>doLayout(LoggingEvent event)</code> method, i.e. the + only method in <code>MySampleLayout</code>, begins by + instantiating a <code>StringBuffer</code>. It proceeds by adding + various fields of the event parameter. The Texan from Texas was + careful to print the formatted form of the message. This is + important when there are one or more parameters passed along with + the logging request. + </p> + + <p>In the above listing of the <code>Layout</code> class, the + <code>LINE_SEP</code> field is inherited from the + <code>Layout</code> interface. It refers to the value returned by + <code>System.getProperty("line.separator")</code> method, that is + system dependent line separator character(s). After adding these + system dependent character(s), the <code>doLayout()</code> method + converts <code>sbuf</code> to <code>String</code> and returns the + resulting value. + </p> + + <p>In the above example, the <code>doLayout</code> method ignores + any eventual exceptions contained in the event. In a real world + layout implementation, you would most probably want to print the + contents of exceptions as well. </p> - <p>Custom layouts are configured as any other layout, as shown below:</p> + <h3>Configuringyour custom layout</h3> + + <p>Custom layouts are configured as any other layout. Here is as + example:</p> <em>Example 5.0: Configuration of MySampleLayout (logback-examples/src/main/java/chapter5/sampleLayoutConfig.xml)</em> @@ -201,23 +208,26 @@ followed by an error message. </p> <p> - To run this example execute the command - <em>java chapter5.SampleLogging src/main/java/chapter5/sampleLayoutConfig.xml</em> - once in the <em>logback-examples</em> directory. This will produce the following - output: - </p> + To run this example issue the following command from within the + <em>logback-examples</em> directory. + </p> + + <p class="command">java chapter5.SampleLogging src/main/java/chapter5/sampleLayoutConfig.xml</p> + + <p> This will produce:</p> <div class="source"><pre>0 DEBUG [main] chapter5.SampleLogging - Everything's going well -0 ERROR [main] chapter5.SampleLogging - ... not quite</pre></div> +0 ERROR [main] chapter5.SampleLogging - maybe not quite...</pre></div> - <p>That was simple enough. - The skeptic Pyrrho of Elea, who insists that nothing is certain except - perhaps uncertainty itself, which is by no means certain either, - might ask: how about a layout with options? - The reader shall find a slightly modified version of our - custom layout in <code>MySampleLayout2.java</code>. She will discover that adding an option - to a layout is as simple as declaring a setter method for the option. + <p>That was simple enough. The skeptic Pyrrho of Elea, who + insists that nothing is certain except perhaps uncertainty itself, + which is by no means certain either, might ask: how about a layout + with options? The reader shall find a slightly modified version + of our custom layout in <code>MySampleLayout2.java</code>. She + will discover that adding an option to a layout is as simple as + declaring a setter method for the option. </p> + <p> The <a href="../xref/chapter5/MySampleLayout2.html"><code>MySampleLayout2</code> @@ -269,17 +279,26 @@ } }</pre></div> - <p>Appart from the actual use of the two attributes, in the <code>doLayout</code> method, - the two setter methods are the only addition to the original class. Yet, it is sufficient - to allow the user to configure these attributes, as shown in the configuration file below:</p> + +  + <p>The addition of the corresponding setter method is all that is + needed to enable the configuration of an option. Note that the + <code>PrintThreadName</code> attribute is a boolean and not a + <code>String</code>. It can be configured anyway by writing + <em>true</em> of <em>false</em> in the configuration + file.Configuration of logback components was covered in detail in + <a href="chapter3.html">"Chapter 3: Logback configuration with + Joran"</a>. Here is a configuration file adapted for + <code>MySampleLayout2</code>. + </p> <div class="source"><pre><configuration> <appender name="STDOUT" class="ch.qos.logback.core.ConsoleAppender"> <layout class="chapter5.MySampleLayout2"> - <b><prefix>MyPrefix</prefix> - <printThreadName>false</printThreadName></b> + <b><prefix>MyPrefix</prefix></b> + <b><printThreadName>false</printThreadName></b> </layout> </appender> @@ -290,9 +309,7 @@ </configuration></pre></div> <p> - Note that the <code>PrintThreadName</code> attribute is a boolean - and not a <code>String</code>. It can be configured anyway by writing <em>true</em> - of <em>false</em> in the configuration file. + </p>

1 0

svn commit: r1371 - logback/tags/SLF4J_1.3.0
by noreply.ceki＠qos.ch 28 Feb '07

28 Feb '07

Author: ceki Date: Wed Feb 28 22:24:30 2007 New Revision: 1371 Removed: logback/tags/SLF4J_1.3.0/ Log: tag added by mistake

1 0

svn commit: r1370 - logback/tags/SLF4J_1.3.0
by noreply.ceki＠qos.ch 28 Feb '07

28 Feb '07

Author: ceki Date: Wed Feb 28 22:21:54 2007 New Revision: 1370 Added: logback/tags/SLF4J_1.3.0/ - copied from r766, /logback/trunk/ Log: tagging release 1.3.0

1 0

svn commit: r1369 - in logback/trunk/logback-examples: lib src/main/java/chapter5
by noreply.ceki＠qos.ch 28 Feb '07

28 Feb '07

Author: ceki Date: Wed Feb 28 20:51:06 2007 New Revision: 1369 Added: logback/trunk/logback-examples/lib/slf4j-api-1.3.0.jar (contents, props changed) Removed: logback/trunk/logback-examples/lib/slf4j-api-1.2.jar Modified: logback/trunk/logback-examples/src/main/java/chapter5/SampleLogging.java Log: Minor updates Added: logback/trunk/logback-examples/lib/slf4j-api-1.3.0.jar ============================================================================== Binary file. No diff available. Modified: logback/trunk/logback-examples/src/main/java/chapter5/SampleLogging.java ============================================================================== --- logback/trunk/logback-examples/src/main/java/chapter5/SampleLogging.java (original) +++ logback/trunk/logback-examples/src/main/java/chapter5/SampleLogging.java Wed Feb 28 20:51:06 2007 @@ -25,10 +25,7 @@ } logger.debug("Everything's going well"); - logger.info("Everything's going well info"); - logger.warn("Everything's going well warn"); - - logger.error("... not quite error"); + logger.error("maybe not quite..."); } }

1 0