[logback-dev] svn commit: r1787 - in logback/trunk: logback-classic/src/main/java/ch/qos/logback/classic/jmx logback-classic/src/main/java/ch/qos/logback/classic/selector logback-classic/src/main/java/ch/qos/logback/classic/util logback-core/src/main/java/ch/qos/logback/core/joran/action logback-core/src/main/java/ch/qos/logback/core/util logback-examples/src/main/java/chapter7 logback-site/src/site/pages/manual logback-site/src/site/resources/manual/images/chapter4
noreply.ceki at qos.ch
noreply.ceki at qos.ch
Fri Aug 29 15:40:43 CEST 2008
Author: ceki
Date: Fri Aug 29 15:40:43 2008
New Revision: 1787
Added:
logback/trunk/logback-site/src/site/resources/manual/images/chapter4/smtpAppender1.jpg (contents, props changed)
Modified:
logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/jmx/Configurator.java
logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/selector/ContextJNDISelector.java
logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/util/ContextInitializer.java
logback/trunk/logback-core/src/main/java/ch/qos/logback/core/joran/action/IncludeAction.java
logback/trunk/logback-core/src/main/java/ch/qos/logback/core/util/Loader.java
logback/trunk/logback-examples/src/main/java/chapter7/SimpleMDC.java
logback/trunk/logback-site/src/site/pages/manual/appenders.html
logback/trunk/logback-site/src/site/pages/manual/layouts.html
Log:
LBCLASSIC-68
The c.q.l.core.util.Loader class is used to load classes or locate resources.
Previously, the TCCL (Thread Context Class Loader) was used to locate resources,
in particular configuration files. However, the TCCL is not set in all environments.
Instead of using the TCL use now use the class loader that loaded the Loader class
itself to load resources. Now, under many circumstances TCCL==self classloader
so most users will not see a difference. The situation where TCCL != self cl
can occur under relatively complicated scenarios. Thus, this commit simplifies the code
without hopefully affecting existing deployments.
Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/jmx/Configurator.java
==============================================================================
--- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/jmx/Configurator.java (original)
+++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/jmx/Configurator.java Fri Aug 29 15:40:43 2008
@@ -49,7 +49,7 @@
addInfo("Shutting down context: " + lc.getName());
lc.shutdownAndReset();
try {
- new ContextInitializer(lc).autoConfig(lc.getClass().getClassLoader());
+ new ContextInitializer(lc).autoConfig();
addInfo("Context: " + lc.getName() + " reloaded.");
} catch(JoranException je) {
addError("Reloading of context: " + lc.getName() + " failed.", je);
Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/selector/ContextJNDISelector.java
==============================================================================
--- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/selector/ContextJNDISelector.java (original)
+++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/selector/ContextJNDISelector.java Fri Aug 29 15:40:43 2008
@@ -115,7 +115,7 @@
private void configureLoggerContextByResource(LoggerContext context,
String configFilePath) {
- URL url = Loader.getResourceByTCL(configFilePath);
+ URL url = Loader.getResourceBySelfClassLoader(configFilePath);
if (url != null) {
try {
JoranConfigurator configurator = new JoranConfigurator();
Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/util/ContextInitializer.java
==============================================================================
--- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/util/ContextInitializer.java (original)
+++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/util/ContextInitializer.java Fri Aug 29 15:40:43 2008
@@ -43,7 +43,7 @@
configurator.doConfigure(url);
}
- private URL findConfigFileURLFromSystemProperties(ClassLoader classLoader) {
+ private URL findConfigFileURLFromSystemProperties() {
String logbackConfigFile = System.getProperty(CONFIG_FILE_PROPERTY, null);
if (logbackConfigFile != null) {
URL result = null;
@@ -53,7 +53,7 @@
} catch (MalformedURLException e) {
// so, resource is not a URL:
// attempt to get the resource from the class path
- result = Loader.getResource(logbackConfigFile, classLoader);
+ result = Loader.getResourceBySelfClassLoader(logbackConfigFile);
if (result != null) {
return result;
}
@@ -72,16 +72,16 @@
return null;
}
- public void autoConfig(ClassLoader classLoader) throws JoranException {
+ public void autoConfig() throws JoranException {
StatusListenerConfigHelper.installIfAsked(loggerContext);
- URL url = findConfigFileURLFromSystemProperties(classLoader);
+ URL url = findConfigFileURLFromSystemProperties();
if (url == null) {
- url = Loader.getResource(TEST_AUTOCONFIG_FILE, classLoader);
+ url = Loader.getResourceBySelfClassLoader(TEST_AUTOCONFIG_FILE);
statusOnResourceSearch(TEST_AUTOCONFIG_FILE, url);
}
if (url == null) {
- url = Loader.getResource(AUTOCONFIG_FILE, classLoader);
+ url = Loader.getResourceBySelfClassLoader(AUTOCONFIG_FILE);
statusOnResourceSearch(AUTOCONFIG_FILE, url);
}
if (url != null) {
@@ -91,11 +91,6 @@
}
}
- public void autoConfig() throws JoranException {
- ClassLoader tccl = Loader.getTCL();
- autoConfig(tccl);
- }
-
private void statusOnResourceSearch(String resourceName, URL url) {
StatusManager sm = loggerContext.getStatusManager();
if (url == null) {
Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/joran/action/IncludeAction.java
==============================================================================
--- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/joran/action/IncludeAction.java (original)
+++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/joran/action/IncludeAction.java Fri Aug 29 15:40:43 2008
@@ -130,7 +130,7 @@
}
private InputStream getInputStreamByResource(String resourceAttribute) {
- URL url = Loader.getResourceByTCL(resourceAttribute);
+ URL url = Loader.getResourceBySelfClassLoader(resourceAttribute);
if (url == null) {
String errMsg = "Could not find resource corresponding to ["
+ resourceAttribute + "]";
Modified: logback/trunk/logback-core/src/main/java/ch/qos/logback/core/util/Loader.java
==============================================================================
--- logback/trunk/logback-core/src/main/java/ch/qos/logback/core/util/Loader.java (original)
+++ logback/trunk/logback-core/src/main/java/ch/qos/logback/core/util/Loader.java Fri Aug 29 15:40:43 2008
@@ -23,41 +23,24 @@
private static boolean ignoreTCL = false;
public static final String IGNORE_TCL_PROPERTY_NAME = "logback.ignoreTCL";
-
+
static {
- String ignoreTCLProp = OptionHelper.getSystemProperty(IGNORE_TCL_PROPERTY_NAME,
- null);
+ String ignoreTCLProp = OptionHelper.getSystemProperty(
+ IGNORE_TCL_PROPERTY_NAME, null);
if (ignoreTCLProp != null) {
ignoreTCL = OptionHelper.toBoolean(ignoreTCLProp, true);
}
}
-
/**
- * This method will search for <code>resource</code> in different places.
- * The search order is as follows:
- *
- * <ol>
- *
- * <p>
- * <li>Search for <code>resource</code> using the thread context class
- * loader under Java2. This step is performed only if the <code>
- skipTCL</code>
- * parameter is false.</li>
+ * Search for a resource using the classloader passed as parameter.
*
- * <p>
- * <li>If the above step fails, search for <code>resource</code> using the
- * class loader that loaded this class (<code>Loader</code>).</li>
- *
- * <p>
- * <li>Try one last time with
- * <code>ClassLoader.getSystemResource(resource)</code>, that is is using
- * the system class loader in JDK 1.2 and virtual machine's built-in class
- * loader in JDK 1.1.
- *
- * </ol>
+ * @param resource
+ * the resource name to look for
+ * @param classLoader
+ * the classloader used for the search
*/
public static URL getResource(String resource, ClassLoader classLoader) {
try {
@@ -67,10 +50,21 @@
}
}
- public static URL getResourceByTCL(String resource) {
- return getResource(resource, getTCL());
+ /**
+ * Attempt to find a resource by using the classloader that loaded this class,
+ * namely Loader.class.
+ *
+ * @param resource
+ * @return
+ */
+ public static URL getResourceBySelfClassLoader(String resource) {
+ return getResource(resource, Loader.class.getClassLoader());
}
-
+
+// private static URL getResourceByTCL(String resource) {
+// return getResource(resource, getTCL());
+// }
+
/**
* Get the Thread Context Loader which is a JDK 1.2 feature. If we are running
* under JDK 1.1 or anything else goes wrong the method returns
@@ -81,11 +75,13 @@
return Thread.currentThread().getContextClassLoader();
}
- @SuppressWarnings("unchecked")
- public static Class loadClass(String clazz, Context context) throws ClassNotFoundException {
+ @SuppressWarnings("unchecked")
+ public static Class loadClass(String clazz, Context context)
+ throws ClassNotFoundException {
ClassLoader cl = context.getClass().getClassLoader();
return cl.loadClass(clazz);
}
+
/**
* If running under JDK 1.2 load the specified class using the
* <code>Thread</code> <code>contextClassLoader</code> if that fails try
Modified: logback/trunk/logback-examples/src/main/java/chapter7/SimpleMDC.java
==============================================================================
--- logback/trunk/logback-examples/src/main/java/chapter7/SimpleMDC.java (original)
+++ logback/trunk/logback-examples/src/main/java/chapter7/SimpleMDC.java Fri Aug 29 15:40:43 2008
@@ -81,7 +81,7 @@
JoranConfigurator configurator = new JoranConfigurator();
configurator.setContext(lc);
lc.shutdownAndReset();
- URL url = Loader.getResourceByTCL("chapter7/simpleMDC.xml");
+ URL url = Loader.getResourceBySelfClassLoader("chapter7/simpleMDC.xml");
configurator.doConfigure(url);
} catch (JoranException je) {
StatusPrinter.print(lc);
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 Fri Aug 29 15:40:43 2008
@@ -1885,9 +1885,9 @@
</root>
</configuration></pre></div>
- <a name="SMTPAppender"/>
- <h3>SMTPAppender</h3>
-
+ <h3><a name="SMTPAppender" href="#SMTPAppender">SMTPAppender</a></h3>
+
+
<p>The <a
href="../xref/ch/qos/logback/classic/net/SMTPAppender.html"><code>SMTPAppender</code></a>
accumulates logging events in a fixed-size buffer and sends them
@@ -1901,59 +1901,65 @@
</p>
<table class="bodyTable">
- <tr class="a">
- <th>Option Name</th>
- <th>Type</th>
- <th>Description</th>
- </tr>
- <tr class="b">
- <td><b><span class="option">SMTPHost</span></b></td>
- <td><code>String</code></td>
- <td>
- The host name of the SMTP server. This parameter is mandatory.
- </td>
- </tr>
- <tr class="a">
- <td><b><span class="option">To</span></b></td>
- <td><code>String</code></td>
- <td>
- The email address of the recipient. Multiple recipients can
- be specified by using several <To> elements.
- </td>
- </tr>
- <tr class="b">
- <td><b><span class="option">From</span></b></td>
- <td><code>String</code></td>
- <td>
- The stated originator of the email messages sent by
- <code>SMTPAppender</code>.
- </td>
- </tr>
- <tr class="a">
- <td><b><span class="option">Subject</span></b></td>
- <td><code>String</code></td>
- <td>
- <p>
- The subject of the email. The String can contain a <code>Pattern</code>
- that <code>PatternLayout</code> uses. In that case, the subject
- is created just before the transmission of the email, with information
- about the last logging event that was issued.
- </p>
- <p>
- For example, setting <em>Log: %logger - %msg</em> as the
- <span class="option">Subject</span> option will send an email with
- the logger name and message string of the event that triggered the
- email transmission.
- </p>
- <p>
- By default, <code>SMTPAppender</code> will form a subject with
- logger name and the message of the last logging event.
- </p>
+ <tr class="a">
+ <th>Option Name</th>
+ <th>Type</th>
+ <th>Description</th>
+ </tr>
+ <tr>
+ <td><b><span class="option">SMTPHost</span></b></td>
+ <td><code>String</code></td>
+ <td>The host name of the SMTP server. This parameter is mandatory.</td>
+ </tr>
+
+ <tr class="alt">
+ <td><b><span class="option">SMTPPort</span></b></td>
+ <td><code>int</code></td>
+ <td>The port where the SMTP server is listening. Defaults to
+ 25.</td>
+ </tr>
+
+ <tr>
+ <td><b><span class="option">To</span></b></td>
+ <td><code>String</code></td>
+ <td>The email address of the recipient. Multiple recipients
+ can be specified by using several <To> elements.</td>
+ </tr>
+ <tr class="alt">
+ <td><b><span class="option">From</span></b></td>
+ <td><code>String</code></td>
+ <td>The stated originator of the email messages sent by
+ <code>SMTPAppender</code>.
+ </td>
+ </tr>
+ <tr>
+ <td><b><span class="option">Subject</span></b></td>
+ <td><code>String</code></td>
+ <td>
+ <p>The subject of the email. It can be any value accepted as
+ a valid conversion pattern by <a
+ href="layouts.html#ClassicPatternLayout">PatternLayout</a>. Layouts
+ will be discussed in the next chapter.
+ </p>
+
+ <p>The outgoing email message will have a subject line
+ corresponding to applying the pattern on the logging event
+ that triggered the email message.
+ </p>
+
+ <p>Assuming the <span class="option">Subject</span> option
+ is set to "Log: %logger - %msg" and the triggerring event's
+ logger is named "com.foo.Bar", and contains the message
+ "Hello world", then the outgoing email will have the subject
+ line "Log: com.foo.Bar - Hello World".
+ </p>
+
+ <p>By default, this option is set to "%logger{20} - %m".</p>
</td>
</tr>
- <tr class="b">
+ <tr class="alt">
<td><b><span class="option">BufferSize</span></b></td>
- <td><code>String</code></td>
+ <td><code>int</code></td>
<td>
The <span class="option">BufferSize</span> option takes a positive
integer representing the maximum number of logging events to collect in a
@@ -1962,7 +1968,7 @@
The default size of the cyclic buffer is 512.
</td>
</tr>
- <tr class="a">
+ <tr >
<td><b><span class="option">Evaluator</span></b></td>
<td><code>String</code></td>
<td>
@@ -1971,17 +1977,21 @@
<code>SMTPAppender</code>'s <code>Evaluator</code> can be given
by adding an attribute to the newly created element.
</p>
- <p>
- More details about the use of event evaluators with <code>SMTPAppender</code>
- follow further down this document.
+
+ <p>More details about the use of event evaluators with
+ <code>SMTPAppender</code> follow further down this document.
</p>
- <p>In the absence of this option,
- <code>SMTPAppender</code> is assigned a default event evaluator which triggers
- email transmission as a response to any event of level <em>ERROR</em> or higher.
+
+ <p>In the absence of this option, <code>SMTPAppender</code> is
+ assigned a default event evaluator which triggers email
+ transmission as a response to any event of level
+ <em>ERROR</em> or higher.
</p>
- <p><code>EventEvaluator</code> objects are subclasses of the <code>JaninoEventEvaluatorBase</code>
- which depends on Janino. See the <a href="../dependencies.html">dependencies page</a>
- for more information.
+
+ <p><code>EventEvaluator</code> objects are subclasses of the
+ <code>JaninoEventEvaluatorBase</code> which depends on
+ Janino. See the <a href="../dependencies.html">dependencies
+ page</a> for more information.
</p>
</td>
</tr>
@@ -1990,7 +2000,7 @@
<p>The SMTPAppender keeps only the last <span
class="option">BufferSize</span> logging events in its cyclic
buffer, throwing away older events when its buffer becomes full.
- The number of logging events delivered in any e-mail sent by
+ Thus, the number of logging events delivered in any e-mail sent by
<code>SMTPAppender</code> is upper-bounded by <span
class="option">BufferSize</span>. This keeps memory requirements
bounded while still delivering a reasonable amount of application
@@ -2033,6 +2043,7 @@
<To>EMAIL-DESTINATION</To>
<To>ANOTHER_EMAIL_DESTINATION</To> <!-- a second destination is optional -->
<From>SENDER-EMAIL</From>
+ <Subject>TESTING: %logger{20} - %m</Subject>
<layout class="ch.qos.logback.classic.PatternLayout">
<Pattern>%date %-5level %logger{35} - %message%n</Pattern>
</layout>
@@ -2044,26 +2055,29 @@
</root>
</configuration></pre></div>
- <p>
- Before trying out <code>chapter4.mail.Email</code> application with the above
- configuration file, you must set the <span class="option">SMTPHost</span>,
- <span class="option">To</span> and <span class="option">From</span> options
- to values appropriate for your environment. Once you have set the proper values,
- change directory to <em>logback-examples</em> and execute the following command:
+ <p>Before trying out <code>chapter4.mail.Email</code> application
+ with the above configuration file, you must set the <span
+ class="option">SMTPHost</span>, <span class="option">To</span> and
+ <span class="option">From</span> options to values appropriate for
+ your environment. Once you have set the correct values in the
+ configuration file, execute the following command:
</p>
<div class="source"><pre>java chapter4.mail.EMail 300 src/main/java/chapter4/mail/mail.xml</pre></div>
- <p>
- The chosen recipient should see an email message containing 300 logging events
- formatted by <code>PatternLayout</code>.
+ <p>The recipient you specified should receive an email message
+ containing 300 logging events formatted by
+ <code>PatternLayout</code> The figure below is the resulting email
+ message as shown by Mozialla Thunderbird.
</p>
+
+ <p><img src="images/chapter4/smtpAppender1.jpg" alt="resulting email"/></p>
- <p>
- In another configuration file <em>mail2.xml</em>, the values for the
- <span class="option">SMTPHost</span>, <span class="option">To</span>
- and <span class="option">From</span> options are determined by variable
- substitution. Here is the relevant part of <em>mail2.xml</em>.
+ <p>In the next exampleconfiguration file <em>mail2.xml</em>, the
+ values for the <span class="option">SMTPHost</span>, <span
+ class="option">To</span> and <span class="option">From</span>
+ options are determined by variable substitution. Here is the
+ relevant part of <em>mail2.xml</em>.
</p>
<div class="source"><pre>
@@ -2075,41 +2089,66 @@
</appender>
</pre></div>
- <p>
- You can supply the various values on the command line:
- </p>
+ <p>You can pass the required parameters on the command line:</p>
<div class="source"><pre>java -Dfrom=source at xyz.com -Dto=recipient at xyz.com
-DsmtpHost=some_smtp_host src/main/java/chapter4.mail.EMail 10000 chapter4/mail/mail2.xml
</pre></div>
- <p>
- Be sure to replace with the correct values appropriate for your environment.
+ <p>Be sure to replace with values as appropriate for your
+ environment.
</p>
- <p>
- Given that the default size of the cyclic buffer is 512,
- the recipient should see an email message containing 512 events conveniently
- formatted in an HTML table. Note that this run of the <code>chapter4.mail.Email</code>
- application generated 10'000 events of which only the last 512 were included in the email.
- </p>
-
- <p>
- By default, the <code>SMTPAppender</code> will initiate the transmission of an email
- message as a response to an event of level <em>ERROR</em> or higher.
- However, it is possible to override this default behavior by providing a custom
- implementation of the <code>EventEvaluator</code> interface.
- </p>
-
- <p>
- The <code>SMTPAppender</code> submits each incoming event to its evaluator
- by calling <code>evaluate()</code> method in order to check whether
- the event should trigger an email or just be placed in the cyclic buffer.
- When the evaluator gives a positive answer to its evaluation, an email is sent.
- The <code>SMTPAppender</code> contains one and only one evaluator object.
- This object may possess its own state. For illustrative purposes,
- the <code>CounterBasedEvaluator</code> class listed next, implements an
- event evaluator whereby every 1024th event triggers an email message.
+ <p>Note that in this latest example, <code>PatternLayout</code>
+ was replaced by <code>HTMLLayout</code> which formats logs as an
+ HTML table. You can change the list and order of columns as well
+ as the CSS of the table. Please refer to <a
+ href="layouts.html#ClassicHTMLLayout">HTMLLayout</a> documentation
+ for further details.
+ </p>
+
+ <p>Given that the default size of the cyclic buffer is 512, the
+ recipient should see an email message containing 512 events
+ conveniently formatted in an HTML table. Note that this run of the
+ <code>chapter4.mail.Email</code> application generated 10'000
+ events of which only the last 512 were included in the outgoing
+ email.
+ </p>
+
+ <p><img src="images/chapter4/smtpAppender2.jpg" alt="2nd email"/></p>
+
+ <p>Email clients such as Mozilla Thunderbird, Eurdora or MS
+ Outlook, offer reasonably good CSS support for HTML email.
+ However, they sometimes automatically downgrade HTML to
+ plaintext. For example, to view HTML email in Thunderbird, the
+ "View→Message Body As→Original HTML" option
+ must be set. Yahoo!Mail's support for HTML email, in particular
+ its CSS support is very good. GMail on the other hand, while it
+ honors the basic HTML table structure, it ignores the internal-CSS
+ formatting. Gmail supports inline-CSS formatitng but since
+ inline-CSS would make the resulting output too voluminous,
+ <code>HTMLLayout</code> does not use inline-CSS.
+ </p>
+
+ <h3>Triggering event</h3>
+
+ <p>By default, the <code>SMTPAppender</code> will initiate the
+ transmission of an email message as a response to an event of
+ level <em>ERROR</em> or higher. However, it is possible to
+ override this default behavior by providing a custom
+ implementation of the <code>EventEvaluator</code> interface.
+ </p>
+
+ <p>The <code>SMTPAppender</code> submits each incoming event to
+ its evaluator by calling <code>evaluate()</code> method in order
+ to check whether the event should trigger an email or just be
+ placed in the cyclic buffer. When the evaluator gives a positive
+ answer to its evaluation, an email is sent. The
+ <code>SMTPAppender</code> contains one and only one evaluator
+ object. This object may possess its own state. For illustrative
+ purposes, the <code>CounterBasedEvaluator</code> class listed
+ next, implements an event evaluator whereby every 1024th event
+ triggers an email message.
</p>
<em>Example 4.11: A <code>EventEvaluator</code> implementation
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 Fri Aug 29 15:40:43 2008
@@ -279,8 +279,9 @@
</p>
- <a name="ClassicPatternLayout"></a>
- <h3>PatternLayout</h3>
+
+ <h3><a name="ClassicPatternLayout"
+ href="#ClassicPatternLayout">PatternLayout</a></h3>
<p>
Logback classic ships with a flexible layout called <a
@@ -1412,9 +1413,11 @@
behaviours, such as option handling.
</p>
- <a name="ClassicHTMLLayout"></a>
+
- <h2>Generating logs in HTML format</h2>
+ <h2>
+ <a name="ClassicHTMLLayout" href="#ClassicHTMLLayout">Generating logs in HTML format</a>
+ </h2>
<p>Logback provides a special <a
href="../xref/ch/qos/logback/core/Layout.html"><code>Layout</code></a>,
Added: logback/trunk/logback-site/src/site/resources/manual/images/chapter4/smtpAppender1.jpg
==============================================================================
Binary file. No diff available.
More information about the logback-dev
mailing list