Author: seb Date: Tue Oct 24 19:56:27 2006 New Revision: 763 Modified: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/PatternLayout.java logback/trunk/logback-access/src/main/java/ch/qos/logback/access/html/HTMLLayout.java logback/trunk/logback-classic/examples/src/chapter5/CallerEvaluatorExample.java logback/trunk/logback-classic/examples/src/chapter5/callerEvaluatorConfig.xml logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/PatternLayout.java logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/html/HTMLLayout.java logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml Log: - added links from javadoc to online layouts page - other fixes Modified: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/PatternLayout.java ============================================================================== --- logback/trunk/logback-access/src/main/java/ch/qos/logback/access/PatternLayout.java (original) +++ logback/trunk/logback-access/src/main/java/ch/qos/logback/access/PatternLayout.java Tue Oct 24 19:56:27 2006 @@ -45,175 +45,8 @@ * usual <code>PatternLayout</code>. * </p> * <p> - * For more information about the general use of a <code>PatternLayout</code>, - * please refer to logback classic's - * <code>ch.qos.logback.classic.PatternLayout</code>. - * </p> - * <p> - * Logback access' <code>PatternLayout</code> offers the following - * possibilities: - * </p> - * <table border="1" CELLPADDING="8"> - * <th>Conversion Character or Word</th> - * <th>Effect</th> - * - * <tr> - * <td align="center"><b>a / remoteIP</b></td> - * <td> - * <p> - * Remote IP address. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>A / localIP</b></td> - * <td> - * <p> - * Local IP address. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>b / B / byteSent</b></td> - * <td> - * <p> - * Response's content length. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>h / clientHost</b></td> - * <td> - * <p> - * Remote host. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>H / protocol</b></td> - * <td> - * <p> - * Request protocol. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>i / header</b></td> - * <td> - * <p> - * Request header. This conversion word can be followed by a key whose - * corresponding data will be extracted from the header information. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>l</b></td> - * <td> - * <p>Remote user. In logback-access, this converter always returns - * the value "-". - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>m / requestMethod</b></td> - * <td> - * <p> - * Request method. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>r / requestURL</b></td> - * <td> - * <p> - * URL requested. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>s / statusCode</b></td> - * <td> - * <p> - * Status code of the request. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>t / date</b></td> - * <td> - * <p> - * Date of the event. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>u / user</b></td> - * <td> - * <p> - * Remote user. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>U / requestURI</b></td> - * <td> - * <p> - * Requested URI. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>v / server</b></td> - * <td> - * <p> - * Server name. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>localPort</b></td> - * <td> - * <p> - * Local port. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>reqAttribute</b></td> - * <td> - * <p> - * Attribute of the request. Just like the request header conversion word, - * reqAttribute can be followed by a key. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>reqCookie</b></td> - * <td> - * <p> - * Request cookie. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>responseHeader</b></td> - * <td> - * <p> - * Header of the response. Just like the request header conversion word, - * responseHeader can be followed by a key. - * </p> - * </td> - * </tr> - * <tr> - * <td align="center"><b>reqParameter</b></td> - * <td> - * <p> - * Parameter of the response. Just like the request header conversion word, - * reqParameter can be followed by a key. - * </p> - * </td> - * </tr> - * </table> + * For more informations about this layout, please refer to the online manual at + * http://logback.qos.ch/manual/layouts.html#AccessPatternLayout * * @author Ceki Gülcü * @author Sébastien Pennec Modified: logback/trunk/logback-access/src/main/java/ch/qos/logback/access/html/HTMLLayout.java ============================================================================== --- logback/trunk/logback-access/src/main/java/ch/qos/logback/access/html/HTMLLayout.java (original) +++ logback/trunk/logback-access/src/main/java/ch/qos/logback/access/html/HTMLLayout.java Tue Oct 24 19:56:27 2006 @@ -27,33 +27,10 @@ * See {@link ch.qos.logback.access.PatternLayout} for documentation on the * available patterns. * <p> - * A user-specified external CSS file can be linked to the html page. - * In case one does not want to customize the html output, an internal CSS style - * is used. + * For more informations about this layout, please refer to the online manual at + * http://logback.qos.ch/manual/layouts.html#AccessHTMLLayout * - * The HTMLLayout is often used in conjunction with SMTPAppender, to - * send a nicely formatted html email. Of course, it can be used with any - * other Appender. * - * In case on wants to use the HTMLLayout with a SMTPAppender, here is a sample - * configuration file that can be used. - * - * <pre> - * <configuration> - * <appender name="SMTP" class="ch.qos.logback.access.net.SMTPAppender"> - * <layout class="ch.qos.logback.access.html.HTMLLayout"> - * <param name="pattern" value="%remoteIP%date%requestURL%statusCode%bytesSent" /> - * </layout> - * <param name="From" value="sender.email@domain.net" /> - * <param name="SMTPHost" value="mail.domain.net" /> - * <param name="Subject" value="LastEvent: %statusCode %requestURL" /> - * <param name="To" value="destination.email@domain.net" /> - * </appender> - * - * <appender-ref ref="SMTP" /> - * </configuration> - *</pre> - * <p> * @author Ceki Gülcü * @author Sébastien Pennec */ Modified: logback/trunk/logback-classic/examples/src/chapter5/CallerEvaluatorExample.java ============================================================================== --- logback/trunk/logback-classic/examples/src/chapter5/CallerEvaluatorExample.java (original) +++ logback/trunk/logback-classic/examples/src/chapter5/CallerEvaluatorExample.java Tue Oct 24 19:56:27 2006 @@ -25,9 +25,9 @@ for (int i = 0; i < 5; i++) { if (i == 3) { - logger.debug("stacktrace logging statement" + i); + logger.debug("who calls thee?"); } else { - logger.debug("logging statement" + i); + logger.debug("I know me " + i); } } } Modified: logback/trunk/logback-classic/examples/src/chapter5/callerEvaluatorConfig.xml ============================================================================== --- logback/trunk/logback-classic/examples/src/chapter5/callerEvaluatorConfig.xml (original) +++ logback/trunk/logback-classic/examples/src/chapter5/callerEvaluatorConfig.xml Tue Oct 24 19:56:27 2006 @@ -1,7 +1,7 @@ <configuration> <evaluator name="DISPLAY_CALLER_EVAL"> - <Expression>logger.getName().contains("chapter5") && message.contains("stacktrace")</Expression> + <Expression>logger.getName().contains("chapter5") && message.contains("who calls thee")</Expression> </evaluator> <appender name="STDOUT" Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/PatternLayout.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/PatternLayout.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/PatternLayout.java Tue Oct 24 19:56:27 2006 @@ -40,402 +40,8 @@ * {#link String}. The format of the result depends on the * <em>conversion pattern</em>. * <p> - * - * <p> - * The conversion pattern is closely related to the conversion pattern of the - * printf function in C. A conversion pattern is composed of literal text and - * format control expressions called <em>conversion specifiers</em>. - * - * <p> - * <i>Note that you are free to insert any literal text within the conversion - * pattern.</i> - * </p> - * - * <p> - * Each conversion specifier starts with a percent sign (%) and is followed by - * optional <em>format modifiers</em> and a <em>conversion character</em> or - * <em>conversion word</em>. The conversion character or word specifies the - * type of data, e.g. logger, level, date, thread name. The format modifiers - * control such things as field width, padding, left and right justification. - * The following is a simple example. - * - * <p> - * Let the conversion pattern be <b>"%-5level [%thread]: %message%n"</b> and - * assume that the logback environment was set to use a PatternLayout. Then the - * statements - * - * <pre> - * Logger logger = LoggerFactory.getLogger("root"); - * root.debug("Message 1"); - * root.warn("Message 2"); - * </pre> - * - * would yield the output - * - * <pre> - * DEBUG [main]: Message 1 - * WARN [main]: Message 2 - * </pre> - * - * <p> - * Note that there is no explicit separator between text and conversion - * specifiers. The pattern parser knows when it has reached the end of a - * conversion specifier when it reads a conversion character. In the example - * above the conversion specifier <b>%-5level</b> means the level of the - * logging event should be left justified to a width of five characters. - * - * The recognized conversion characters and words are - * - * <p> - * <table border="1" CELLPADDING="8"> - * <th>Conversion Character or Word</th> - * <th>Effect</th> - * - * <tr> - * <td align=center><b>c / l / lo / logger</b></td> - * - * <td>Used to output the logger of the logging event. The logger conversion - * specifier can be optionally followed by <em>precision specifier</em>, that - * is a decimal constant in brackets. - * - * <p> - * If a precision specifier is given, then only the corresponding number of - * right most components of the logger name will be printed. By default the - * logger name is printed in full. - * - * <p> - * For example, for the logger name "a.b.c" the pattern <b>%logger{2}</b> - * will output "b.c". See more examples of name abbreviations further down this - * document. - * - * </td> - * </tr> - * - * <tr> - * <td align=center><b>C / class</b></td> - * - * <td>Used to output the fully qualified class name of the caller issuing the - * logging request. This conversion specifier can be optionally followed by - * <em>precision specifier</em>, that is a decimal constant in brackets. - * - * <p> - * If a precision specifier is given, then only the corresponding number of - * right most components of the class name will be printed. By default the class - * name is output in fully qualified form. - * - * <p> - * For example, for the class name "ch.logback.xyz.SomeClass", the pattern - * <b>%class{1}</b> will output "SomeClass". See more examples of name - * abbreviations further down this document. - * - * <p> - * <b>WARNING</b> Generating the caller class information is slow. Thus, it's - * use should be avoided unless execution speed is not an issue. - * - * </td> - * </tr> - * - * <tr> - * <td align=center><b>d / date</b></td> - * <td>Used to output the date of the logging event. The date conversion - * specifier may be followed by a set of braces containing a date and time - * pattern strings {@link java.text.SimpleDateFormat}, <em>ABSOLUTE</em>, - * <em>DATE</em> or <em>ISO8601</em>. For example, <b>%d{HH:mm:ss,SSS}</b>, - * <b>%d{dd MMM yyyy HH:mm:ss,SSS}</b> or <b>%d{DATE}</b>. If - * no date format specifier is given then ISO8601 format is assumed. </td> - * </tr> - * - * <tr> - * <td align=center><b>F / file</b></td> - * - * <td>Used to output the file name where the logging request was issued. - * - * <p> - * <b>WARNING</b> Generating caller file information is extremely slow. Its use - * should be avoided unless execution speed is not an issue. - * </td> - * </tr> - * - * <tr> - * <td align=center><b>caller</b></td> - * - * <td>Used to output location information of the caller which generated the - * logging event. - * - * <p> - * The location information depends on the JVM implementation but usually - * consists of the fully qualified name of the calling method followed by the - * callers source the file name and line number between parentheses. - * - * <p> - * The location information can be very useful. However, it's generation is - * <em>extremely</em> slow. It's use should be avoided unless execution speed - * is not an issue. - * - * </td> - * </tr> - * - * <tr> - * <td align=center><b>L / line</b></td> - * - * <td>Used to output the line number from where the logging request was - * issued. - * - * <p> - * <b>WARNING</b> Generating caller location information is extremely slow. - * It's use should be avoided unless execution speed is not an issue. - * </td> - * </tr> - * - * - * <tr> - * <td align=center><b>m / msg / message</b></td> - * <td>Used to output the application supplied message associated with the - * logging event.</td> - * </tr> - * - * <tr> - * <td align=center><b>M / method</b></td> - * - * <td>Used to output the method name where the logging request was issued. - * - * <p> - * <b>WARNING</b> Generating caller location information is extremely slow. - * It's use should be avoided unless execution speed is not an issue. - * </td> - * </tr> - * - * <tr> - * <td align=center><b>n</b></td> - * - * <td>Outputs the platform dependent line separator character or characters. - * - * <p> - * This conversion character offers practically the same performance as using - * non-portable line separator strings such as "\n", or "\r\n". Thus, it is the - * preferred way of specifying a line separator. - * - * </td> - * </tr> - * - * <tr> - * <td align=center><b>p / le / level</b></td> - * <td>Used to output the level of the logging event.</td> - * </tr> - * - * <tr> - * - * <td align=center><b>r / relative</b></td> - * - * <td>Used to output the number of milliseconds elapsed since the start of the - * application until the creation of the logging event.</td> - * </tr> - * - * - * <tr> - * <td align=center><b>t / thread</b></td> - * - * <td>Used to output the name of the thread that generated the logging event.</td> - * - * </tr> - * - * <tr> - * <td align=center><b>X / mdc</b></td> - * - * <td> - * - * <p> - * Used to output the MDC (mapped diagnostic context) associated with the thread - * that generated the logging event. The <b>X</b> conversion character can be - * followed by the key for the map placed between braces, as in - * <b>%X{clientNumber}</b> where <code>clientNumber</code> is the key. The - * value in the MDC corresponding to the key will be output. If no additional - * sub-option is specified, then the entire contents of the MDC key value pair - * set is output using a format key1=val1, key2=val2 - * </p> - * - * <p> - * See {@link MDC} class for more details. - * </p> - * - * </td> - * </tr> - * <tr> - * <td align=center><b>throwable</b></td> - * - * <td> - * <p> - * Used to output the Throwable trace that has been bound to the LoggingEvent, - * by default this will output the full trace as one would normally find by a - * call to Throwable.printStackTrace(). The throwable conversion word can be - * followed by an option in the form <b>%throwable{short}</b> which will only - * output the first line of the ThrowableInformation. - * </p> - * </td> - * </tr> - * - * <tr> - * - * <td align=center><b>%</b></td> - * - * <td>The sequence %% outputs a single percent sign. </td> - * </tr> - * - * </table> - * - * <p> - * By default the relevant information is output as is. However, with the aid of - * format modifiers it is possible to change the minimum field width, the - * maximum field width and justification. - * - * <p> - * The optional format modifier is placed between the percent sign and the - * conversion character or word. - * - * <p> - * The first optional format modifier is the <em>left justification flag</em> - * which is just the minus (-) character. Then comes the optional - * <em>minimum field width</em> modifier. This is a decimal constant that - * represents the minimum number of characters to output. If the data item - * requires fewer characters, it is padded on either the left or the right until - * the minimum width is reached. The default is to pad on the left (right - * justify) but you can specify right padding with the left justification flag. - * The padding character is space. If the data item is larger than the minimum - * field width, the field is expanded to accommodate the data. The value is - * never truncated. - * - * <p> - * This behavior can be changed using the <em>maximum field width</em> - * modifier which is designated by a period followed by a decimal constant. If - * the data item is longer than the maximum field, then the extra characters are - * removed from the <em>beginning</em> of the data item and not from the end. - * For example, it the maximum field width is eight and the data item is ten - * characters long, then the first two characters of the data item are dropped. - * This behavior deviates from the printf function in C where truncation is done - * from the end. - * - * <p> - * Below are various format modifier examples for the logger conversion - * specifier. - * - * <p> - * <TABLE BORDER=1 CELLPADDING=8> - * <th>Format modifier - * <th>Left justify - * <th>Minimum width - * <th>Maximum width - * <th>Comment - * - * <tr> - * <td align=center>%20c</td> - * <td align=center>false</td> - * <td align=center>20</td> - * <td align=center>none</td> - * - * <td>Left pad with spaces if the category name is less than 20 characters - * long. - * - * <tr> - * <td align=center>%-20c</td> - * <td align=center>true</td> - * <td align=center>20</td> - * <td align=center>none</td> - * <td>Right pad with spaces if the logger name is less than 20 characters - * long. - * - * <tr> - * <td align=center>%.30c</td> - * <td align=center>NA</td> - * <td align=center>none</td> - * <td align=center>30</td> - * - * <td>Truncate from the beginning if the logger name is longer than 30 - * characters. - * - * <tr> - * <td align=center>%20.30c</td> - * <td align=center>false</td> - * <td align=center>20</td> - * <td align=center>30</td> - * - * <td>Left pad with spaces if the logger name is shorter than 20 characters. - * However, if logger name is longer than 30 characters, then truncate from the - * beginning. - * - * <tr> - * <td align=center>%-20.30c</td> - * <td align=center>true</td> - * <td align=center>20</td> - * <td align=center>30</td> - * - * <td>Right pad with spaces if the logger name is shorter than 20 characters. - * However, if logger name is longer than 30 characters, then truncate from the - * beginning. - * - * </table> - * - * <p> - * Below are some examples of conversion patterns. - * - * <dl> - * - * <p> - * <dt><b>%relative [%thread] %-5level %logger %mdc - %message\n</b> - * <p> - * <dd>This is essentially the TTCC layout. - * - * <p> - * <dt><b>%-6relative [%15.15thread] %-5level %30.30logger %mdc - %message\n</b> - * - * <p> - * <dd>Similar to the TTCC layout except that the relative time is right padded - * if less than 6 digits, thread name is right padded if less than 15 characters - * and truncated if longer and the logger name is left padded if shorter than 30 - * characters and truncated if longer. - * - * </dl> - * <p> Here are a few more examples of the precision specifier behaviour, with emphasis on - * the way it affects class names. - * <p> - * - * <table BORDER=1 CELLPADDING=8> - * - * <tr> - * <th>Conversion Pattern</th> - * <th>Logger name</th> - * <th>Result</th> - * </tr> - * - * <tr> - * <td>%logger{10}</td> - * <td>mainPackage.sub.sample.Bar</td> - * <td>m.s.s.Bar</td> - * </tr> - * - * <tr> - * <td>%logger{15}</td> - * <td>mainPackage.sub.sample.Bar</td> - * <td>m.s.sample.Bar</td> - * </tr> - * - * <tr> - * <td>%logger{16}</td> - * <td>mainPackage.sub.sample.Bar</td> - * <td>m.sub.sample.Bar</td> - * </tr> - * - * <tr> - * <td>%logger{26}</td> - * <td>mainPackage.sub.sample.Bar</td> - * <td>mainPackage.sub.sample.Bar</td> - * </tr> - * - * </table> - * - * <p> - * The above text is largely inspired from Peter A. Darnell and Philip E. - * Margolis' highly recommended book "C -- a Software Engineering Approach", - * ISBN 0-387-97389-3. + * For more informations about this layout, please refer to the online manual at + * http://logback.qos.ch/manual/layouts.html#ClassicPatternLayout * * */ Modified: logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/html/HTMLLayout.java ============================================================================== --- logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/html/HTMLLayout.java (original) +++ logback/trunk/logback-classic/src/main/java/ch/qos/logback/classic/html/HTMLLayout.java Tue Oct 24 19:56:27 2006 @@ -26,57 +26,9 @@ * See {@link ch.qos.logback.classic.PatternLayout} for documentation on the * available patterns. * <p> - * Note that the pattern <em>%ex</em> used to display an Exception is not the only way - * to display an Exception with this layout. If you use this pattern, a table column will - * be created to display the potential Exception's stacktrace. - * <p> - * However, a better solution is available in the form of implementations of the - * {@link ch.qos.logback.classic.html.IThrowableRenderer} interface. - * These implementations can be called and assigned to HTMLLayout to manage the display - * of anything related to Exceptions. - * <p> - * By default, a {@link ch.qos.logback.classic.html.DefaultThrowableRenderer} - * is assigned to the HTMLLayout. It writes the Exception on a new table row, along - * with its stacktrace, in a easily readable manner. - * <p> - * If one wants to use the <em>&ex</em> pattern anyway, then a NOPThrowableRenderer - * can be specified in the configuration file. - * <p> - * A user-specified external CSS file can be linked to the html page. - * In case one does not want to customize the html output, an internal CSS style - * is used. + * For more informations about this layout, please refer to the online manual at + * http://logback.qos.ch/manual/layouts.html#ClassicHTMLLayout * - * The HTMLLayout is often used in conjunction with SMTPAppender, to - * send a nicely formatted html email. Of course, it can be used with any - * other Appender. - * - * In case on wants to use the HTMLLayout with a SMTPAppender, here is a sample - * configuration file that can be used. - * - * <pre> - * <configuration> - * <appender name="SMTP" class="ch.qos.logback.classic.net.SMTPAppender"> - * <layout class="ch.qos.logback.classic.html.HTMLLayout"> - * <param name="pattern" value="%relative%thread%mdc%level%class%msg" /> - * </layout> - * <throwableRenderer class="ch.qos.logback.classic.html.DefaultThrowableRenderer" /> - * <param name="From" value="sender.email@domain.net" /> - * <param name="SMTPHost" value="mail.domain.net" /> - * <param name="Subject" value="LastEvent: %class - %msg" /> - * <param name="To" value="destination.email@domain.net" /> - * </appender> - * - * <root> - * <level value="debug" /> - * <appender-ref ref="SMTP" /> - * </root> - * </configuration> - *</pre> - * <p> - * In this configuration file, the <em>throwableRenderer</em> element specifies the default - * implementation of IThrowableRenderer. It could be omitted, but is showed for educationnal - * purposes. - * <p> * @author Ceki Gülcü * @author Sébastien Pennec */ Modified: logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml ============================================================================== --- logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml (original) +++ logback/trunk/logback-site/src/site/xdocTemplates/manual/layouts.xml Tue Oct 24 19:56:27 2006 @@ -43,20 +43,13 @@ </td> </tr> </table> + + <p>Printing notice: if you want to print this document, you might want to + use Firefox, with <em>Adapt to page size</em> enabled, + or Opera for better rendering on paper.</p> <h2>What is a layout</h2> -<div class="source">this -is - a test - without pres</div> - - -<div class="source"><pre>this -is - a test - with pres</pre></div> - <p> While appenders are responsible for writing logging output to an appender dependent device, layouts are responsible for @@ -486,14 +479,14 @@ </p> <p>For example, <b>%caller{2}</b> would display the following excerpt:</p> -<div class="source"><pre>0 [main] DEBUG - logging statement Caller+0 \ -at mainPackage.sub.sample.Bar.sampleMethodName(Bar.java:22) -Caller+1 at mainPackage.sub.sample.Bar.createLoggingRequest(Bar.java:17)</pre></div> +<div class="source"><pre>0 [main] DEBUG - logging statement +Caller+0 at mainPackage.sub.sample.Bar.sampleMethodName(Bar.java:22) +Caller+1 at mainPackage.sub.sample.Bar.createLoggingRequest(Bar.java:17)</pre></div> <p>And <b>%caller{3}</b> would display this other excerpt:</p> -<div class="source"><pre>16 [main] DEBUG - logging statement Caller+0 \ -at mainPackage.sub.sample.Bar.sampleMethodName(Bar.java:22) -Caller+1 at mainPackage.sub.sample.Bar.createLoggingRequest(Bar.java:17) -Caller+2 at mainPackage.ConfigTester.main(ConfigTester.java:38)</pre></div> +<div class="source"><pre>16 [main] DEBUG - logging statement +Caller+0 at mainPackage.sub.sample.Bar.sampleMethodName(Bar.java:22) +Caller+1 at mainPackage.sub.sample.Bar.createLoggingRequest(Bar.java:17) +Caller+2 at mainPackage.ConfigTester.main(ConfigTester.java:38)</pre></div> <p> This conversion word can also use evaluators to test logging events