March 2008 - logback-dev - mailman3.qos.ch

svn commit: r1657 - logback/trunk/logback-site/src/site/pages
by noreply.ceki＠qos.ch 22 Mar '08

22 Mar '08

Author: ceki Date: Sat Mar 22 19:45:01 2008 New Revision: 1657 Modified: logback/trunk/logback-site/src/site/pages/faq.html Log: - indetentation changes only Modified: logback/trunk/logback-site/src/site/pages/faq.html ============================================================================== --- logback/trunk/logback-site/src/site/pages/faq.html (original) +++ logback/trunk/logback-site/src/site/pages/faq.html Sat Mar 22 19:45:01 2008 @@ -20,239 +20,185 @@ <div id="content"> <h2> - <a name="top">Logback Frequently Asked Questions</a> - </h2> - - - Logback Classic - - - <ol type="1"> - <li> - <a href="#setup_jetty"> - How can I use logback-classic with Jetty ? - </a> - </li> - <li> - <a href="#auto_config"> - How does the automatic configuration work? - </a> - </li> - <li> - <a href="#intercept_calls_tomcat"> - How can I intercept JCL calls in Tomcat? - </a> - </li> - <li> - <a href="#intercept_calls_jetty"> - How can I intercept JCL calls in Jetty ? - </a> - </li> - </ol> + <a name="top">Logback Frequently Asked Questions</a> + </h2> + + + Logback Classic + + + <ol type="1"> + <li> + <a href="#setup_jetty"> + How can I use logback-classic with Jetty ? + </a> + </li> + <li> + <a href="#auto_config"> + How does the automatic configuration work? + </a> + </li> + <li> + <a href="#intercept_calls_tomcat"> + How can I intercept JCL calls in Tomcat? + </a> + </li> + <li> + <a href="#intercept_calls_jetty"> + How can I intercept JCL calls in Jetty ? + </a> + </li> + </ol> - <div class="section"> - <h2>Logback Classic</h2> - <dl> - <dt> - <a name="setup_jetty"> - How can I use logback-classic with Jetty ? - </a> - </dt> - <dd> - - The Jetty application server uses SLF4J for its internal - logging. Here are the required steps to install logback - as SLF4J's underlaying implementation. - - - A few jars must be present in the - JETTY_HOME/lib - directory. - - - - Logback-classic is based on the SLF4J api. Therefore, - the - slf4j-api-VERSION.jar - jar must be present. This jar can be downloaded from the - <a href="http://www.slf4j.org/">SLF4J</a> - project. - - - Logback's own jars must also be present, namely - logback-core-VERSION.jar - and - logback-classic-VERSION.jar - . - - - - To configure logback-classic, a file called - logback.xml - should be placed in the - JETTY_HOME/resources - directory. You can find configuration samples in the - examples/src/chapter4/conf/ - directory, in the distribution of logback. - - <table border="0"> - <tr> - <td align="right"> - <a href="#top">[top]</a> - </td> - </tr> - </table> - <hr /> - </dd> - <dt> - <a name="auto_config"> - How does the automatic configuration work? - </a> - </dt> - <dd> - - If a file called - logback.xml - is found in the classpath, then it is used. - - - In case it is not found, a - logback-test.xml - file is searched, and used if available. - - - If none of these files are available, logback uses its - <code>BasicConfigurator</code> - class to create a simple default configuration that will - only log to the console. - - <table border="0"> - <tr> - <td align="right"> - <a href="#top">[top]</a> - </td> - </tr> - </table> - <hr /> - </dd> - <dt> - <a name="intercept_calls_tomcat"> - How can I intercept JCL calls in Tomcat? - </a> - </dt> - <dd> - - When a dependency of your webapp logs using Jakarta - Commons Logging (for example Struts), you can intercept - these calls and redirect them to logback. - - - This can be done by using - jcl104-over-slf4j.jar - , a module that is shipped with - <a href="http://www.slf4j.org">SLF4J</a> - . - - - If you have only one webapp, its - WEB-INF/lib - directory should already contain the logback jars, - namely - logback-core-VERSION.jar - , - logback-classic-VERSION.jar - and - slf4j-api-VERSION.jar - . A logback configuration file, named - logback.xml - should be placed in the - WEB-INF/classes/ - directory. - - - You now need to add - <code>jcl104-over-slf4j.jar</code> - to your - WEB-INF/lib - directory and remove - <code>commons-logging-1.0.4.jar</code> - . The logging that used to be directed to JCL should now - be handled by logback. - - - - In case several webapps share the logback jars, you - might place the previously mentionned jars in the - common/lib/ - directory of your Tomcat installation. The - logback.xml - file should then be placed in - common/classes - . - - <table border="0"> - <tr> - <td align="right"> - <a href="#top">[top]</a> - </td> - </tr> - </table> - <hr /> - </dd> - <dt> - <a name="intercept_calls_jetty"> - How can I intercept JCL calls in Jetty ? - </a> - </dt> - <dd> - - Using logback as the logging implementation of choice - for frameworks depending on JCL can also be done in - Jetty. - - - In case you have only one webapp, the required steps are - exactly the same as - <a href="#intercept_calls_tomcat"> - those needed in Tomcat - </a> - . - - - In case several webapps share the logback jars, you - might place the necessary jars in the - lib/ - directory of your Jetty installation. The - logback.xml - file should then be placed in the - resources/ - directory. - - - However, due to - <a - href="http://docs.codehaus.org/display/JETTY/Classloading"> - Jetty's internal Classloading mechanism - </a> - , the - logback-classic-VERSION.jar - and - slf4j-api-VERSION.jar - files should also be placed in the - WEB-INF/lib/ - directory of your webapps. - - <table border="0"> - <tr> - <td align="right"> - <a href="#top">[top]</a> - </td> + <div class="section"> + <h2>Logback Classic</h2> + <dl> + <dt> + <a name="setup_jetty"> + How can I use logback-classic with Jetty ? + </a> + </dt> + <dd> + The Jetty application server uses SLF4J for its internal + logging. Here are the required steps to install logback as + SLF4J's underlaying implementation. + + + A few jars must be present in the JETTY_HOME/lib + directory. + + + Logback-classic is based on the SLF4J api. Therefore, the + slf4j-api-VERSION.jar jar must be present. This jar + can be downloaded from the <a + href="http://www.slf4j.org/">SLF4J</a> project. + + Logback's own jars must also be present, namely + logback-core-VERSION.jar and + logback-classic-VERSION.jar . + + + To configure logback-classic, a file called + logback.xml should be placed in the + JETTY_HOME/resources directory. You can find + configuration samples in the + examples/src/chapter4/conf/ directory, in the + distribution of logback. + + + <table border="0"> + <tr> + <td align="right"> + <a href="#top">[top]</a> + </td> + </tr> + </table> + <hr /> + </dd> + <dt> + <a name="auto_config"> + How does the automatic configuration work? + </a> + </dt> + <dd> + If a file called logback.xml is found in the + classpath, then it is used. + + In case it is not found, a logback-test.xml file + is searched, and used if available. + + If none of these files are available, logback uses its + <code>BasicConfigurator</code> class to create a simple + default configuration that will only log to the console. + + <table border="0"> + <tr> + <td align="right"> + <a href="#top">[top]</a> + </td> </tr> - </table> - </dd> - </dl> - </div> - </div> + </table> + <hr /> + </dd> + <dt> + <a name="intercept_calls_tomcat"> + How can I intercept JCL calls in Tomcat? + </a> + </dt> + <dd> + When a dependency of your webapp logs using Jakarta Commons + Logging (for example Struts), you can intercept these calls + and redirect them to logback. + + This can be done by using jcl104-over-slf4j.jar , + a module that is shipped with <a + href="http://www.slf4j.org">SLF4J</a> . + + If you have only one webapp, its WEB-INF/lib + directory should already contain the logback jars, namely + logback-core-VERSION.jar , + logback-classic-VERSION.jar and + slf4j-api-VERSION.jar . A logback configuration file, + named logback.xml should be placed in the + WEB-INF/classes/ directory. + + You now need to add <code>jcl104-over-slf4j.jar</code> to + your WEB-INF/lib directory and remove + <code>commons-logging-1.0.4.jar</code> . The logging that used + to be directed to JCL should now be handled by logback. + + + In case several webapps share the logback jars, you might + place the previously mentionned jars in the + common/lib/ directory of your Tomcat + installation. The logback.xml file should then be + placed in common/classes . + + <table border="0"> + <tr> + <td align="right"> + <a href="#top">[top]</a> + </td> + </tr> + </table> + <hr /> + </dd> + <dt> + <a name="intercept_calls_jetty"> + How can I intercept JCL calls in Jetty ? + </a> + </dt> + <dd> + Using logback as the logging implementation of choice for + frameworks depending on JCL can also be done in Jetty. + + In case you have only one webapp, the required steps are + exactly the same as <a href="#intercept_calls_tomcat">those + needed in Tomcat</a>. + + In case several webapps share the logback jars, you might + place the necessary jars in the lib/ directory of + your Jetty installation. The logback.xml file should + then be placed in the resources/ directory. + + However, due to <a + href="http://docs.codehaus.org/display/JETTY/Classloading"> + Jetty's internal Classloading mechanism</a>, the + logback-classic-VERSION.jar and + slf4j-api-VERSION.jar files should also be placed in + the WEB-INF/lib/ directory of your webapps. + + <table border="0"> + <tr> + <td align="right"> + <a href="#top">[top]</a> + </td> + </tr> + </table> + </dd> + </dl> + </div> +</div>

1 0

[Bug 100] New: Serialization of objectArray in LoggingEvent does not always work
by bugzilla-daemon＠pixie.qos.ch 22 Mar '08

22 Mar '08

http://bugzilla.qos.ch/show_bug.cgi?id=100 Summary: Serialization of objectArray in LoggingEvent does not always work Product: logback-classic Version: unspecified Platform: PC URL: http://www.qos.ch/pipermail/logback-dev/2007- September/002169.html OS/Version: Other Status: NEW Severity: major Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: noreply.ceki(a)qos.ch I think this is happening: * Logback is sending a serialized LoggingEvent over the socket * the LoggingEvent has a reference to the foo.bar.Car instance * the Eclipse plugin receives the bytes over the wire and tries to deserialize the LoggingEvent, this fails because the foo.bar.Car class is not on the classpath. Resolution: I think the SocketAppender should only send the formattedMessage over the wire and not the argumentArray. In other words: argumentArray should be declared transient. Let's see what the LogBack developers think about that ... -- 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 19

[Bug 129] New: An <include> in an included file leads to out of memory
by bugzilla-daemon＠pixie.qos.ch 20 Mar '08

20 Mar '08

http://bugzilla.qos.ch/show_bug.cgi?id=129 Summary: An <include> in an included file leads to out of memory Product: logback-core Version: unspecified Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 Component: Joran AssignedTo: logback-dev(a)qos.ch ReportedBy: mfranz(a)intershop.de Situation: 3 configuration files A.xml, B.xml and C.xml A includes B and B includes C This leads Joran to run into out of memory. The reason is in class ch.qos.logback.core.joran.action.IncludeAction The begin() method fills the instance variable recoder with events and adds them to the global list. But since there is only one instance of IncludeAction it adds the already added events from the first include a second time at the second include event. This leads to an almost endless loop. A not that severe effect is that if a single file contains multiple includes it executes the first include as often as the total number of includes is. To solve this for me clearing the event list at the end of the begin method worked well: public void begin(InterpretationContext ec, String name, Attributes attributes) throws ActionException { ... ec.getJoranInterpreter().addEvents(recorder.saxEventList); // This is my fix recorder.saxEventList.clear(); } -- 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

[Bug 139] New: LoggingEvent.formattedMessage is only initialized in c'tor.
by bugzilla-daemon＠pixie.qos.ch 20 Mar '08

20 Mar '08

http://bugzilla.qos.ch/show_bug.cgi?id=139 Summary: LoggingEvent.formattedMessage is only initialized in c'tor. Product: logback-classic Version: unspecified Platform: All OS/Version: All Status: NEW Severity: major Priority: P1 Component: Other AssignedTo: logback-dev(a)qos.ch ReportedBy: joern(a)huxhorn.de LoggingEvent.formattedMessage is only initialized if message and arguments are supplied during construction. If the default c'tor is used and message and arguments are provided using setMessage and setArgumentArray then formattedMessage will stay null. Instead, formattedMessage should be declared transient and the actual formatting should take place lazily during getFormattedMessage call. This would fix this problem, would increase general logging performance (formatting only if actually needed) and would decrease the size of serialized log events significantly while it would not change anything from the callers point of view. This is a follow-up of bug #100. -- 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 0

[Bug 138] New: support looking up property files from classpath resources
by bugzilla-daemon＠pixie.qos.ch 20 Mar '08

20 Mar '08

http://bugzilla.qos.ch/show_bug.cgi?id=138 Summary: support looking up property files from classpath resources Product: logback-core Version: unspecified Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P1 Component: Joran AssignedTo: logback-dev(a)qos.ch ReportedBy: bruno.navert(a)morganstanley.com Joran's support for property files (through PropertyAction) is useful, but it only reads filesystem files. It would be useful to be able to read classpath resources, that way the logback.xml file as well as its properties files would be located in the same place (in the class path). Furthermore, it would be useful for both resource and file lookups to perform system property resolution in the included file names. For instance: <substitutionProperty resource="config/logback/logback-${CONFIG_MODE}.properties"/> where CONFIG_MODE is a system property. In our environment this is set to something like DEV or QA or PROD, which would allow use of substitution properties that change based on the environment. -- 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 0

svn commit: r1656 - logbackPDE/trunk/plugins/ConsolePlugin
by noreply.ceki＠qos.ch 19 Mar '08

19 Mar '08

Author: ceki Date: Wed Mar 19 22:26:03 2008 New Revision: 1656 Modified: logbackPDE/trunk/plugins/ConsolePlugin/pom.xml Log: - bumped version number Modified: logbackPDE/trunk/plugins/ConsolePlugin/pom.xml ============================================================================== --- logbackPDE/trunk/plugins/ConsolePlugin/pom.xml (original) +++ logbackPDE/trunk/plugins/ConsolePlugin/pom.xml Wed Mar 19 22:26:03 2008 @@ -8,7 +8,7 @@ <artifactId>ConsolePlugin</artifactId> <packaging>zip</packaging> <name>Console Plugin for Eclipse</name> - <version>1.0.1-SNAPSHOT</version> + <version>1.0.2</version> <url>http://logback.qos.ch</url> <organization>

1 0

svn commit: r1655 - in logback-demo/trunk: . src/main/resources
by noreply.ceki＠qos.ch 19 Mar '08

19 Mar '08

Author: ceki Date: Wed Mar 19 22:11:22 2008 New Revision: 1655 Modified: logback-demo/trunk/pom.xml logback-demo/trunk/src/main/resources/logback.xml Log: - bumped logback dependency to logback 0.9.9-SNAPSHOT - grouping example in logback.xml Modified: logback-demo/trunk/pom.xml ============================================================================== --- logback-demo/trunk/pom.xml (original) +++ logback-demo/trunk/pom.xml Wed Mar 19 22:11:22 2008 @@ -9,20 +9,20 @@ <version>1.0</version> <properties> - <lb.version>0.9.8</lb.version> + <lb.version>0.9.9-SNAPSHOT</lb.version> </properties> <dependencies> <dependency> - <groupId>struts</groupId> - <artifactId>struts</artifactId> - <version>1.2.9</version> - <scope>compile</scope> - </dependency> + <groupId>struts</groupId> + <artifactId>struts</artifactId> + <version>1.2.9</version> + <scope>compile</scope> + </dependency> <dependency> - <groupId>javax.servlet</groupId> + <groupId>javax.servlet</groupId> <artifactId>servlet-api</artifactId> <version>2.4</version> <scope>provided</scope> Modified: logback-demo/trunk/src/main/resources/logback.xml ============================================================================== --- logback-demo/trunk/src/main/resources/logback.xml (original) +++ logback-demo/trunk/src/main/resources/logback.xml Wed Mar 19 22:11:22 2008 @@ -10,7 +10,7 @@ class="ch.qos.logback.core.ConsoleAppender"> <layout class="ch.qos.logback.classic.PatternLayout"> <pattern> - %d{HH:mm:ss.SSS} [%thread] %-5level %logger{32} - %msg%n + $%d{HH:mm:ss.SSS} [%thread]$ %-5level %logger{32} - %msg%n </pattern> </layout> </appender> @@ -27,7 +27,7 @@ <layout class="ch.qos.logback.classic.PatternLayout"> <Pattern> - %d{HH:mm:ss,SSS} [%thread] %-5level %logger{32} - %msg%n + %-26(%d{HH:mm:ss,SSS} [%thread]) %-5level %logger{32} - %msg%n </Pattern> </layout> </appender>

1 0

svn commit: r1654 - logback/trunk/logback-site/src/site/pages/manual
by noreply.ceki＠qos.ch 19 Mar '08

19 Mar '08

Author: ceki Date: Wed Mar 19 22:07:35 2008 New Revision: 1654 Modified: logback/trunk/logback-site/src/site/pages/manual/appenders.html Log: - ongoing work on the appenders chapter 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 Wed Mar 19 22:07:35 2008 @@ -857,7 +857,7 @@ <a href="../xref/ch/qos/logback/core/rolling/TimeBasedRollingPolicy.html"> <code>TimeBasedRollingPolicy</code></a> is probably the most popular rolling polciy. It allows defines a rollover policy based - on time, say by day or month. + on time, say by day or by month. <code>TimeBasedRollingPolicy</code>'s has only one mandatory @@ -868,10 +868,10 @@ name of the rolled (archived) log files. Its value FileNamePattern should consist of the name of the file, plus a suitably placed %d conversion specifier. - The %d conversion specifier may contain a date and time + The %d conversion specifier may contain a date-and-time pattern as specified by the <code>java.text.SimpleDateFormat</code> - class. If the date and time pattern is omitted, then the default - pattern of yyyy-MM-dd is assumed. The following examples + class. If the date-and-time pattern is omitted, then the default + pattern yyyy-MM-dd is assumed. The following examples should clarify the point. @@ -1005,30 +1005,19 @@ </table> The FileNamePattern serves a dual - purposes. First, by studying the pattern, logback computes the - requested rollover periodicity. Second, it computes each file's - name. It is entirely possible for two different patterns to specify - the same periodicity. The (date) patterns yyyy-MM and + purpose. First, by studying the pattern, logback computes the + requested rollover periodicity. Second, it computes each archived + file's name. Note that it is possible for two different patterns to + specify the same periodicity. The patterns yyyy-MM and yyyy@MM both specify monthly rollover, although the resulting archive files will carry different names. - - Thus, <code>TimeBasedRollingPolicy</code> caries a responsiblity - for rollover as well as for the triggering of said rollover. Put - differently, <code>TimeBasedTriggeringPolicy</code> implements both - <code>RollingPolicy</code> and <code>TriggeringPolicy</code> - interfaces. A <code>RollingFileAppender</code> owning a child - <code>TimeBasedRollingPolicy</code> can be started and used - correctly even if its does not contain a reference to a - <code>TriggeringPolicy</code>. - - - As with <code>FixedWindowRollingPolicy</code>, - <code>TimeBasedRollingPolicy</code> decouples the location of the - active log file and the archived log files. The File option defines the log file for the - current period whereas archived files are those files which - have been rolled over in previous periods. + + Thus, <code>TimeBasedRollingPolicy</code> assumes the + responsiblity for rollover as well as for the triggering of said + rollover. Indeed, <code>TimeBasedTriggeringPolicy</code> implements + both <code>RollingPolicy</code> and <code>TriggeringPolicy</code> + interfaces. By setting the File option you can @@ -1042,6 +1031,7 @@ class="option">FileNamePattern. + For various reasons, rollovers are not clock-driven but depend on the arrival of logging events. For example, on 8th of March 2002, assuming the FileNamePattern is set to @@ -1056,9 +1046,9 @@ output in the correct file delimiting that period. -  - Here is a sample configuration of a <code>RollingFileAppender</code> which - uses a <code>TimeBasedRollingPolicy</code> + Here is a sample configuration for + <code>RollingFileAppender</code> in conjuction with a + <code>TimeBasedRollingPolicy</code>. Example 4.5: Sample configuration of a <code>RollingFileAppender</code> using a @@ -1084,63 +1074,59 @@ <a name="TriggeringPolicy"></a> <h3>Triggering policies</h3> - <a href="../xref/ch/qos/logback/core/rolling/TriggeringPolicy.html"><code>TriggeringPolicy</code></a> - implementations are responsible for instructing - the <code>RollingFileAppender</code> to rollover. + <a + href="../xref/ch/qos/logback/core/rolling/TriggeringPolicy.html"><code>TriggeringPolicy</code></a> + implementations are responsible for instructing the + <code>RollingFileAppender</code> to rollover. - The <code>TriggeringPolicy</code> interface is pretty simple. + The <code>TriggeringPolicy</code> interface contains only one + method. <div class="source"><pre>package ch.qos.logback.core.rolling; import java.io.File; import ch.qos.logback.core.spi.LifeCycle; -public interface TriggeringPolicy extends LifeCycle { +public interface TriggeringPolicy<E> extends LifeCycle { - public boolean isTriggeringEvent(final File activeFile, final Object event); + public boolean isTriggeringEvent(final File activeFile, final <E> event); }</pre></div> - The - <code>isTriggeringEvent()</code> - method takes the active file, and the currently processed - logging event. It's implementation decides, based on these - parameters, whether the rollover must occur or not, by - returning a boolean value. + The <code>isTriggeringEvent()</code> method takes as parameters + the active file, and the logging event currently being + processed. The concrete implementation determines whether the + rollover should occur or not, based on the said parameters. <a name="SizeBasedTriggeringPolicy"></a> <h4>SizeBasedTriggeringPolicy</h4> - - <a href="../xref/ch/qos/logback/core/rolling/SizeBasedTriggeringPolicy.html"> - <code>SizeBasedTriggeringPolicy</code></a> - looks at size of the file being currently written to. If it - grows larger than the specified size, the - <code>FileAppender</code> using the - <code>SizeBasedTriggeringPolicy</code> - will proceed to the rollover of the current file and log to - a new one. - - - - This <code>TriggeringPolicy</code> - only accepts one parameter, that is the - MaxFileSize - option. This option's default value is 10 MB. - - - - The MaxFileSize - option can be specified in a simple and easy way, by - specifying the unit that should be used. One can enter any - numeric value, with three possible units, namely KB, - MB and GB. Consequently, values like - 5MB, 500KB or 2GB are all valid. - - - Here is a sample configuration with a <code>RollingFileAppender</code> - using a <code>SizeBasedTriggeringPolicy</code>. + <a + href="../xref/ch/qos/logback/core/rolling/SizeBasedTriggeringPolicy.html"> + <code>SizeBasedTriggeringPolicy</code></a> looks at size of the + currently active file. If it grows larger than the specified size, + the <code>FileAppender</code> using the + <code>SizeBasedTriggeringPolicy</code> will proceed to the + rollover of the existing active file and create a new one. + + + This <code>TriggeringPolicy</code> accepts only one parameter, + namely MaxFileSize, with a default + value of 10 MB. + + + The MaxFileSize option can be + specified in bytes, kilobytes, megabytes or gigabytes by suffixing + a numeric value with KB, MB and respectively + GB. For example, 5000000, 5000KB, + 5MB and 2GB are all valid values, with the first + three being also equivalent. + + + Here is a sample configuration with a + <code>RollingFileAppender</code> in conjuction with + <code>SizeBasedTriggeringPolicy</code>. Example 4.6: Sample configuration of a <code>RollingFileAppender</code> using a @@ -1168,28 +1154,17 @@ </root> </configuration></pre></div> - - <code>TriggeringPolicy</code> implementations do not only serve with - <code>RollingFileAppender</code> objects. They can also be used to tell - <code>SMTPAppender</code>, which will be covered soon, when to send an email - containing the last logging events. - - - - In that case, the <code>isTriggeringEvent()</code> method takes null - as its first parameter (of type <code>File</code>) and takes the logging event - as its second parameter. It is based on that last element that the decision is - made to send the email or not. By default, a <code>TriggeringPolicy</code> is - included with <code>SMTPAppender</code> that triggers the mail each time an event - with a <code>Level</code> of ERROR or more is issued. - - + +  <a name="Classic"></a> <h2>Logback Classic</h2> - - - While logging event are declared as <code>Object</code> in logback core, - they are instances of the <code>LoggingEvent</code> class in logback classic. + + + While logging events are generic in logback-core, within + logback-classic they are always instances of + <code>LoggingEvent</code>. + + <a name="SocketAppender"></a> <h3>SocketAppender</h3>

1 0

svn commit: r1653 - in logback/trunk: logback-access/src/test/java/ch/qos/logback/access/jetty logback-core/src/main/java/ch/qos/logback/core/helpers logback-core/src/main/java/ch/qos/logback/core/rolling logback-core/src/test/java/ch/qos/logback/core/rolling
by noreply.ceki＠qos.ch 19 Mar '08

19 Mar '08

Author: ceki Date: Wed Mar 19 22:06:42 2008 New Revision: 1653 Modified: logback/trunk/logback-access/src/test/java/ch/qos/logback/access/jetty/JettyBasicTest.java logback/trunk/logback-core/src/main/java/ch/qos/logback/core/helpers/CyclicBuffer.java logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/RollingFileAppender.java logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/SizeBasedTriggeringPolicy.java logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TimeBasedRollingPolicy.java logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TriggeringPolicy.java logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TriggeringPolicyBase.java logback/trunk/logback-core/src/test/java/ch/qos/logback/core/rolling/SizeBasedRollingTest.java Log: - classed in c.q.l.core.rolling package made generic - additional assertion in JettyBasicTest Modified: logback/trunk/logback-access/src/test/java/ch/qos/logback/access/jetty/JettyBasicTest.java ============================================================================== --- logback/trunk/logback-access/src/test/java/ch/qos/logback/access/jetty/JettyBasicTest.java (original) +++ logback/trunk/logback-access/src/test/java/ch/qos/logback/access/jetty/JettyBasicTest.java Wed Mar 19 22:06:42 2008 @@ -61,6 +61,7 @@ assertEquals("hello world", result); ListAppender appender = (ListAppender) requestLogImpl.getAppender("list"); + assertTrue(appender.list.size()>0); AccessEvent event = (AccessEvent) appender.list.get(0); assertEquals("127.0.0.1", event.getRemoteHost()); assertEquals("localhost", event.getServerName()); Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/helpers/CyclicBuffer.java ============================================================================== --- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/helpers/CyclicBuffer.java (original) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/helpers/CyclicBuffer.java Wed Mar 19 22:06:42 2008 @@ -46,6 +46,7 @@ init(maxSize); } + @SuppressWarnings("unchecked") private void init(int maxSize) { this.maxSize = maxSize; ea = (E[]) new Object[maxSize]; Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/RollingFileAppender.java ============================================================================== --- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/RollingFileAppender.java (original) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/RollingFileAppender.java Wed Mar 19 22:06:42 2008 @@ -29,7 +29,7 @@ * */ public class RollingFileAppender<E> extends FileAppender<E> { File activeFileCache; - TriggeringPolicy triggeringPolicy; + TriggeringPolicy<E> triggeringPolicy; RollingPolicy rollingPolicy; /** @@ -136,12 +136,12 @@ public void setRollingPolicy(RollingPolicy policy) { rollingPolicy = policy; if(rollingPolicy instanceof TriggeringPolicy) { - triggeringPolicy = (TriggeringPolicy) policy; + triggeringPolicy = (TriggeringPolicy<E>) policy; } } - public void setTriggeringPolicy(TriggeringPolicy policy) { + public void setTriggeringPolicy(TriggeringPolicy<E> policy) { triggeringPolicy = policy; if(policy instanceof RollingPolicy) { rollingPolicy = (RollingPolicy) policy; Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/SizeBasedTriggeringPolicy.java ============================================================================== --- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/SizeBasedTriggeringPolicy.java (original) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/SizeBasedTriggeringPolicy.java Wed Mar 19 22:06:42 2008 @@ -26,7 +26,7 @@ * @author Ceki Gülcü * */ -public class SizeBasedTriggeringPolicy extends TriggeringPolicyBase { +public class SizeBasedTriggeringPolicy<E> extends TriggeringPolicyBase<E> { public static final String SEE_SIZE_FORMAT = "http://logback.qos.ch/codes.html#sbtp_size_format"; /** @@ -44,7 +44,7 @@ setMaxFileSize(maxFileSize); } - public boolean isTriggeringEvent(final File activeFile, final Object event) { + public boolean isTriggeringEvent(final File activeFile, final E event) { //System.out.println("Size"+file.length()); return (activeFile.length() >= maxFileSize.getSize()); } Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TimeBasedRollingPolicy.java ============================================================================== --- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TimeBasedRollingPolicy.java (original) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TimeBasedRollingPolicy.java Wed Mar 19 22:06:42 2008 @@ -29,7 +29,7 @@ * * @author Ceki Gülcü */ -public class TimeBasedRollingPolicy extends RollingPolicyBase implements TriggeringPolicy { +public class TimeBasedRollingPolicy<E> extends RollingPolicyBase implements TriggeringPolicy<E> { static final String FNP_NOT_SET = "The FileNamePattern option must be set before using TimeBasedRollingPolicy. "; static final String SEE_FNP_NOT_SET = @@ -185,7 +185,7 @@ } } - public boolean isTriggeringEvent(File activeFile, final Object event) { + public boolean isTriggeringEvent(File activeFile, final E event) { long time= getCurrentTime(); if (time >= nextCheck) { Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TriggeringPolicy.java ============================================================================== --- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TriggeringPolicy.java (original) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TriggeringPolicy.java Wed Mar 19 22:06:42 2008 @@ -23,7 +23,7 @@ * @author Ceki Gülcü * */ -public interface TriggeringPolicy extends LifeCycle { +public interface TriggeringPolicy<E> extends LifeCycle { /** * Should roll-over be triggered at this time? @@ -32,5 +32,5 @@ * @param event A reference to the currently event. * @return true if a roll-over should occur. */ - public boolean isTriggeringEvent(final File activeFile, final Object event); + public boolean isTriggeringEvent(final File activeFile, final E event); } Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TriggeringPolicyBase.java ============================================================================== --- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TriggeringPolicyBase.java (original) +++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/rolling/TriggeringPolicyBase.java Wed Mar 19 22:06:42 2008 @@ -20,7 +20,7 @@ * @author Ceki Gülcü * */ -abstract public class TriggeringPolicyBase extends ContextAwareBase implements TriggeringPolicy { +abstract public class TriggeringPolicyBase<E> extends ContextAwareBase implements TriggeringPolicy<E> { private boolean start; Modified: logback/trunk/logback-core/src/test/java/ch/qos/logback/core/rolling/SizeBasedRollingTest.java ============================================================================== --- logback/trunk/logback-core/src/test/java/ch/qos/logback/core/rolling/SizeBasedRollingTest.java (original) +++ logback/trunk/logback-core/src/test/java/ch/qos/logback/core/rolling/SizeBasedRollingTest.java Wed Mar 19 22:06:42 2008 @@ -108,7 +108,7 @@ FixedWindowRollingPolicy swrp = new FixedWindowRollingPolicy(); swrp.setContext(context); - SizeBasedTriggeringPolicy sbtp = new SizeBasedTriggeringPolicy(); + SizeBasedTriggeringPolicy<Object> sbtp = new SizeBasedTriggeringPolicy<Object>(); sbtp.setContext(context); sbtp.setMaxFileSize("100"); @@ -180,7 +180,7 @@ FixedWindowRollingPolicy fwrp = new FixedWindowRollingPolicy(); fwrp.setContext(context); - SizeBasedTriggeringPolicy sbtp = new SizeBasedTriggeringPolicy(); + SizeBasedTriggeringPolicy<Object> sbtp = new SizeBasedTriggeringPolicy<Object>(); sbtp.setContext(context); sbtp.setMaxFileSize("100");

1 0

svn commit: r1652 - in logback/trunk/logback-site/src/site/pages: . manual
by noreply.ceki＠qos.ch 19 Mar '08

19 Mar '08

Author: ceki Date: Wed Mar 19 21:48:31 2008 New Revision: 1652 Modified: logback/trunk/logback-site/src/site/pages/manual/layouts.html logback/trunk/logback-site/src/site/pages/news.html Log: - improved docs 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 Mar 19 21:48:31 2008 @@ -835,17 +835,15 @@ </td> </tr> - <tr class="b"> - - <td align="center"> - % - </td> - - <td>The sequence %% outputs a single percent sign.</td> - </tr> </table> + Given that in the context of conversion patterns the percent + sign carries special meaning, in order to include it as a literal, + it needs to be escaped with a backslash, e.g. "%d %p \% + %m%n". + + <h2>Format modifiers</h2> 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 Wed Mar 19 21:48:31 2008 @@ -81,14 +81,25 @@ serialized as strings. - Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=109">bug 109</a> reported by Joern Huxhorn. There should no longer be any NullPointerExceptions thrown by deserialized <code>AccessEvent</code> instances. + + Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=8">bug + 8</a> reported by Sebastien Pennec. The documentation has been + updated to reflect the fact that that in the context of conversion + patterns the percent sign carries special meaning, in order to + include the percent sign as a literal, it must be escaped with a + backslash. + Fixed <a href="http://bugzilla.qos.ch/show_bug.cgi?id=52">bug + 52</a> reported by Kenichi Masuko. The bug has been fixed on March + 8th, 2007. Starting with this release, Joran will support the + injection of any enum tpye, not just <code>FilterReply</code>. + <hr width="80%" align="center" />

1 0