[logback-dev] svn commit: r1316 - logback/trunk/logback-site/src/site/resources/manual
noreply.seb at qos.ch
noreply.seb at qos.ch
Mon Feb 5 18:05:17 CET 2007
Author: seb
Date: Mon Feb 5 18:05:17 2007
New Revision: 1316
Modified:
logback/trunk/logback-site/src/site/resources/manual/appenders.html
logback/trunk/logback-site/src/site/resources/manual/architecture.html
logback/trunk/logback-site/src/site/resources/manual/filters.html
logback/trunk/logback-site/src/site/resources/manual/introduction.html
logback/trunk/logback-site/src/site/resources/manual/joran.html
logback/trunk/logback-site/src/site/resources/manual/layouts.html
Log:
Modified anchors
Modified: logback/trunk/logback-site/src/site/resources/manual/appenders.html
==============================================================================
--- logback/trunk/logback-site/src/site/resources/manual/appenders.html (original)
+++ logback/trunk/logback-site/src/site/resources/manual/appenders.html Mon Feb 5 18:05:17 2007
@@ -113,7 +113,7 @@
transmitting them over the wire.
</p>
- <a name="AppenderBase"/>
+ <a name="AppenderBase"></a>
<h2>AppenderBase</h2>
<p>
@@ -229,7 +229,7 @@
contained in the core module are can be used by any module without any customization.
</p>
- <a name="WriterAppender" />
+ <a name="WriterAppender"></a>
<h3>WriterAppender</h3>
<p>
@@ -353,7 +353,7 @@
<img src="images/chapter4/fileAppenderUML.png" alt="A UML diagram showing FileAppender"/>
- <a name="ConsoleAppender" />
+ <a name="ConsoleAppender"></a>
<h3>ConsoleAppender</h3>
<p>
@@ -420,7 +420,7 @@
<div class="source"><pre>java chapter4.ConfigurationTester src/main/java/chapter4/conf/logback-Console.xml</pre></div>
- <a name="FileAppender" />
+ <a name="FileAppender"></a>
<h3>FileAppender</h3>
<p>
@@ -553,7 +553,7 @@
<div class="source"><pre>java chapter4.ConfigurationTester src/main/java/chapter4/conf/logback-fileAppender.xml</pre></div>
- <a name="RollingFileAppender" />
+ <a name="RollingFileAppender"></a>
<h3>RollingFileAppender</h3>
<p>
@@ -665,7 +665,7 @@
Lastly, a <code>RollingPolicy</code> knows about its parent.
</p>
- <a name="FixedWindowRollingPolicy" />
+ <a name="FixedWindowRollingPolicy"></a>
<h4>FixedWindowRollingPolicy</h4>
<p>
@@ -882,7 +882,7 @@
</root>
</configuration></pre></div>
- <a name="TimeBasedRollingPolicy" />
+ <a name="TimeBasedRollingPolicy"></a>
<h4>TimeBasedRollingPolicy</h4>
<p>
<a href="../xref/ch/qos/logback/core/rolling/TimeBasedRollingPolicy.html">
@@ -1115,7 +1115,7 @@
</root>
</configuration></pre></div>
- <a name="TriggeringPolicy"/>
+ <a name="TriggeringPolicy"></a>
<h3>Triggering policies</h3>
<p><a href="../xref/ch/qos/logback/core/rolling/TriggeringPolicy.html"><code>TriggeringPolicy</code></a>
@@ -1143,7 +1143,7 @@
returning a boolean value.
</p>
- <a name="SizeBasedTriggeringPolicy" />
+ <a name="SizeBasedTriggeringPolicy"></a>
<h4>SizeBasedTriggeringPolicy</h4>
<p>
@@ -1218,14 +1218,14 @@
with a <code>Level</code> of <em>ERROR</em> or more is issued.
</p>
- <a name="Classic"/>
+ <a name="Classic"></a>
<h2>Logback Classic</h2>
<p>While logging event are declared as <code>Object</code> in logback core,
they are instances of the <code>LoggingEvent</code> class in logback classic.</p>
- <a name="SocketAppender" />
+ <a name="SocketAppender"></a>
<h3>SocketAppender</h3>
<p>
@@ -1474,7 +1474,7 @@
tunnels the events it receives from its clients to a second server.
</p>
- <a name="JMSAppenderBase" />
+ <a name="JMSAppenderBase"></a>
<h3>JMSAppenderBase</h3>
<p>
@@ -1728,7 +1728,7 @@
The JMS appenders do not implement the <code>ExceptionListener</code> interface.
</p>
- <a name="JMSTopicAppender" />
+ <a name="JMSTopicAppender"></a>
<h3>JMSTopicAppender</h3>
<p>
@@ -1871,7 +1871,7 @@
</root>
</configuration></pre></div>
- <a name="JMSQueueAppender" />
+ <a name="JMSQueueAppender"></a>
<h3>JMSQueueAppender</h3>
<p>
@@ -2227,7 +2227,7 @@
- <a name="DBAppender"/>
+ <a name="DBAppender"></a>
<h3>DBAppender</h3>
<p>
@@ -2760,7 +2760,7 @@
The gain is a <em>10</em> factor.
</p>
- <a name="SyslogAppender" />
+ <a name="SyslogAppender"></a>
<h3>SyslogAppender</h3>
<p>
@@ -2891,7 +2891,7 @@
</p>
- <a name="Access" />
+ <a name="Access"></a>
<h2>Logback Access</h2>
<p>
@@ -2917,7 +2917,7 @@
for classic's <code>SocketAppender</code>.
</p>
- <a name="AccessSMTPAppender"/>
+ <a name="AccessSMTPAppender"></a>
<h3>SMTPAppender</h3>
<p>
@@ -2959,7 +2959,7 @@
- <a name="AccessDBAppender"/>
+ <a name="AccessDBAppender"></a>
<h3>DBAppender</h3>
<p>
@@ -3118,7 +3118,7 @@
</configuration></pre></div>
- <a name="WriteYourOwnAppender" />
+ <a name="WriteYourOwnAppender"></a>
<h2>Writing your own Appender</h2>
Modified: logback/trunk/logback-site/src/site/resources/manual/architecture.html
==============================================================================
--- logback/trunk/logback-site/src/site/resources/manual/architecture.html (original)
+++ logback/trunk/logback-site/src/site/resources/manual/architecture.html Mon Feb 5 18:05:17 2007
@@ -94,7 +94,7 @@
logback-core has no notion of loggers.
</p>
- <a name="LoggerContext" />
+ <a name="LoggerContext"></a>
<h3>Logger context</h3>
<p>The first and foremost advantage of any logging API over plain
@@ -362,7 +362,7 @@
parent <code>X</code>, which has an assigned level.
</p>
- <a name="PrintintMethods" />
+ <a name="PrintintMethods"></a>
<h3>Printing methods</h3>
<p>By definition, the printing method determines the level of a
@@ -465,7 +465,7 @@
// This request is disabled, because <span class="green bold">DEBUG</span> < <span class="blue">INFO</span>.
barlogger.<span class="green bold">debug</span>("Exiting gas station search");</pre></div>
- <a name="RetrievingLoggers" />
+ <a name="RetrievingLoggers"></a>
<h3>Retrieving Loggers</h3>
<p>
Calling the <code><a href="../apidocs/org/slf4j/LoggerFactory.html#getLogger(java.lang.String)">LoggerFactory.getLogger</a></code>
@@ -516,7 +516,7 @@
located seems to be the best general strategy known so far.
</p>
- <a name="AppendersAndLayouts" />
+ <a name="AppendersAndLayouts"></a>
<h3>Appenders and Layouts</h3>
<p>
@@ -674,7 +674,7 @@
the message of the request.
</p>
- <a name="ParametrizedLogging" />
+ <a name="ParametrizedLogging"></a>
<h3>Parameterized logging</h3>
<p>
@@ -772,7 +772,7 @@
<div class="source"><pre>Object[] paramArray = {newVal, below, above};
logger.debug("Value {} was inserted between {} and {}.", paramArray);</pre></div>
- <a name="Configuration" />
+ <a name="Configuration"></a>
<h3>Configuration</h3>
<p>Inserting log requests into the application code requires a
@@ -1058,7 +1058,7 @@
the introduction. The output was generated due to this feature.
</p>
-<a name="UnderTheHood" />
+<a name="UnderTheHood"></a>
<h3>A peak under the hood</h3>
<p>
@@ -1147,7 +1147,7 @@
<a href="underTheHood.html"><img src="images/chapter2/underTheHoodSequence2_small.gif" /></a>
-<a name="Performance" />
+<a name="Performance"></a>
<h3>Performance</h3>
<p>
Modified: logback/trunk/logback-site/src/site/resources/manual/filters.html
==============================================================================
--- logback/trunk/logback-site/src/site/resources/manual/filters.html (original)
+++ logback/trunk/logback-site/src/site/resources/manual/filters.html Mon Feb 5 18:05:17 2007
@@ -78,7 +78,7 @@
<h2>Logback Classic</h2>
- <a name="Filter" />
+ <a name="Filter"></a>
<p><code>Filter</code> objects all implement the
<a href="../xref/ch/qos/logback/core/filter/Filter.html"><code>Filter</code></a>
abscract class. The <code>decide(Object event)</code> method is passed a
@@ -271,7 +271,7 @@
or <code>AbstractMatcherFilter</code> classes.
</p>
- <a name="EventEvaluator" />
+ <a name="EventEvaluator"></a>
<h3>Event Evaluators</h3>
<p>
@@ -471,7 +471,7 @@
0 [main] INFO chapter6.FilterEvents - logging statement 9</pre></div>
- <a name="TurboFilter" />
+ <a name="TurboFilter"></a>
<h3>TurboFilters</h3>
<p>
Modified: logback/trunk/logback-site/src/site/resources/manual/introduction.html
==============================================================================
--- logback/trunk/logback-site/src/site/resources/manual/introduction.html (original)
+++ logback/trunk/logback-site/src/site/resources/manual/introduction.html Mon Feb 5 18:05:17 2007
@@ -85,7 +85,7 @@
</p>
</div>
- <a name="Requirements" />
+ <a name="Requirements"></a>
<h3>Requirements</h3>
<p>Logback-classic module requires the presence
@@ -236,7 +236,7 @@
produce logging output on the configured appenders.</p>
</ol>
- <a name="BuildingLogback" />
+ <a name="BuildingLogback"></a>
<h3>Building logback</h3>
<p>
Modified: logback/trunk/logback-site/src/site/resources/manual/joran.html
==============================================================================
--- logback/trunk/logback-site/src/site/resources/manual/joran.html (original)
+++ logback/trunk/logback-site/src/site/resources/manual/joran.html Mon Feb 5 18:05:17 2007
@@ -960,7 +960,7 @@
</configuration></pre></div>
-<a name="Joran" />
+<a name="Joran"></a>
<h2>Using Joran in your own application</h2>
<p>As we've seen, logback relies on Joran, a
@@ -1111,7 +1111,7 @@
<code>StatusManager</code>.
</p>
-<a name="helloWorld" />
+<a name="helloWorld"></a>
<h3>A hello world example</h3>
<p>The <em>logback-examples/src/main/java/chapter3/helloWorld/</em> directory includes a
@@ -1156,7 +1156,7 @@
will be issued, displaying <em>Hello World</em> in the console.
</p>
-<a name="calculator" />
+<a name="calculator"></a>
<h3>Collaborating actions</h3>
<p>
The <em>logback-examples/src/main/java/joran/calculator/</em> directory includes several actions
@@ -1241,7 +1241,7 @@
of XML will guarantee that a value saved by one <code>begin()</code> will be consumed
only by the matching <code>end()</code> method.</p>
-<a name="newRule" />
+<a name="newRule"></a>
<h3>New-rule action</h3>
<p>Joran includes an action which allows the Joran interpreter to lean
new rules on the fly while interpreting the XML file containing the
@@ -1289,7 +1289,7 @@
<multiply/>
</computation></pre></div>
-<a name="implicit" />
+<a name="implicit"></a>
<h3>Implicit actions </h3>
<p>The rules defined thus far are called explicit rules because they
require an explicit pattern, hence fixing the tag name of the elements
Modified: logback/trunk/logback-site/src/site/resources/manual/layouts.html
==============================================================================
--- logback/trunk/logback-site/src/site/resources/manual/layouts.html (original)
+++ logback/trunk/logback-site/src/site/resources/manual/layouts.html Mon Feb 5 18:05:17 2007
@@ -292,7 +292,7 @@
</p>
- <a name="PatternLayout" />
+ <a name="PatternLayout"></a>
<h3>PatternLayout</h3>
<p>
@@ -1311,7 +1311,7 @@
the use of options, in her custom <code>Converter</code> objects.
</p>
- <a name="ClassicHTMLLayout"/>
+ <a name="ClassicHTMLLayout"></a>
<h3>HTMLLayout</h3>
<p><a href="../xref/ch/qos/logback/classic/html/HTMLLayout.html">
<code>HTMLLayout</code></a> outputs events in an HTML table. Each row of the table corresponds to a
@@ -1444,7 +1444,7 @@
<p>Writing a custom <code>Layout</code> for logback access is nearly identical
as to writing a <code>Layout</code> for the classic module.</p>
- <a name="AccessPatternLayout" />
+ <a name="AccessPatternLayout"></a>
<h3>PatternLayout</h3>
<p>Access' <a href="../xref/ch/qos/logback/access/PatternLayout.html">
<code>PatternLayout</code></a> work the exact same way as it's classic counterpart.
@@ -1725,7 +1725,7 @@
much like the <em>common</em> pattern but also displays two request headers, namely
referer, and user-agent.</p>
- <a name="AccessHTMLLayout" />
+ <a name="AccessHTMLLayout"></a>
<h3>HTMLLayout</h3>
<p>The access version of
More information about the logback-dev
mailing list