nicko 2005/05/02 13:57:51
Modified: xdocs/src contributing.xml downloads.xml history.xml
index.xml license.xml roadmap.xml support.xml
xdocs/src/release building.xml config-examples.xml
example-apps.xml faq.xml features.xml
framework-support.xml release-notes.xml
xdocs/src/release/manual configuration.xml contexts.xml
internals.xml introduction.xml plugins.xml
repositories.xml
Log:
Added explicit id attributes to all <section> elements. This reduces churn on
the auto ids
Revision Changes Path
1.8 +14 -14 logging-log4net/xdocs/src/contributing.xml
Index: contributing.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/contributing.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- contributing.xml 24 Apr 2005 23:51:22 -0000 1.7
+++ contributing.xml 2 May 2005 20:57:50 -0000 1.8
@@ -24,7 +24,7 @@
<meta name="keywords" content="contributing to log4net development,
contributing log4net, log4net cvs, log4net" />
<body>
- <section name="Contributing to log4net Development">
+ <section id="main" name="Contributing to log4net Development">
<sectionMenu name="Contents" />
@@ -34,13 +34,13 @@
</p>
-->
- <section name="Developer Mailing List">
+ <section id="mlist" name="Developer Mailing List">
<p>
All discussion relating to log4net
development takes place on this list. All CVS checkin
notifications are also copied to this
list.
</p>
- <section name="Mailing List Archives">
+ <section id="mlist-archive" name="Mailing List
Archives">
<p>
You can browse the mailing list
archives at the following locations:
</p>
@@ -53,7 +53,7 @@
</ul>
</section>
- <section name="Subscribe">
+ <section id="mlist-subscribe" name="Subscribe">
<p>
Subscribe to either the list or
to the digest list:
</p>
@@ -75,7 +75,7 @@
</ul>
</section>
- <section name="Unsubscribe">
+ <section id="mlist-unsubscribe"
name="Unsubscribe">
<p>
To unsubscribe send an email to
the relevant email address:
</p>
@@ -97,7 +97,7 @@
</ul>
</section>
- <section name="Posting">
+ <section id="mlist-posting" name="Posting">
<p>
Most of the guidelines for the
log4net-user list also apply to the dev list.
Please have a quick read
through the <a href="support.html">guidelines</a>, thanks.
@@ -121,16 +121,16 @@
</section>
</section>
- <section name="CVS Access">
+ <section id="cvs" name="CVS Access">
- <section name="Browsing CVS">
+ <section id="cvs-view" name="Browsing CVS">
<p>
<a
href="http://cvs.apache.org/viewcvs/logging-log4net/";>Browse log4net</a>
CVS repository using ViewCVS.
</p>
</section>
- <section name="Anonymous CVS Access">
+ <section id="cvs-anon" name="Anonymous CVS
Access">
<p>
Anyone can checkout source code
from our anonymous CVS
server. To do so, simply use
the following commands (if you are
@@ -166,7 +166,7 @@
</section>
<!-- TODO: Work out how to generate nightly snapshots of the CVS tree
- <section name="Nightly Snapshots">
+ <section id="nightly" name="Nightly Snapshots">
<p>
Nightly snapshots of the CVS
tree are available at
<a
href="http://cvs.apache.org/snapshots/log4net/";>http://cvs.apache.org/snapshots/log4net/</a>.
@@ -175,7 +175,7 @@
-->
</section>
- <section name="Issue Tracking">
+ <section id="jira" name="Issue Tracking">
<p>
Many bugs reported end up not being a
bug in the log4net code,
but are due to incorrect configuration,
problems caused by installed applications,
@@ -204,7 +204,7 @@
you are seeing has already been
reported. If it has been reported then you can vote for the issue.
</p>
- <section name="Reporting an Issue">
+ <section id="jira-reporting" name="Reporting an
Issue">
<p>
If after you have exhausted all
other resources to resolve a problem you may want to file a bug report.
Please make sure the problem is
a bug in Logging and not a bug in your application.
@@ -238,7 +238,7 @@
</section>
</section>
- <section name="Contributing Patches">
+ <section id="patch" name="Contributing Patches">
<p>
Before starting to work on a patch it
is probably a good idea to join the log4net-dev
mailing list to check that equivalent
or complementary work is not already underway.
@@ -341,7 +341,7 @@
</section>
<!-- TODO: Add guidelines for contributors
- <section name="Guidelines for Contributors">
+ <section id="guidelines" name="Guidelines for
Contributors">
<p>
To contribute code to the log4net
project follow the following
guidelines:
1.3 +5 -5 logging-log4net/xdocs/src/downloads.xml
Index: downloads.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/downloads.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- downloads.xml 21 Mar 2005 02:37:12 -0000 1.2
+++ downloads.xml 2 May 2005 20:57:50 -0000 1.3
@@ -24,9 +24,9 @@
<meta name="keywords" content="log4net downloads, log4net download,
log4net" />
<body>
- <section name="log4net Downloads">
+ <section id="main" name="log4net Downloads">
- <section name="Project Status">
+ <section id="status" name="Project Status">
<p>
log4net is an effort undergoing
incubation at the Apache Software
Foundation (ASF), sponsored by the
Apache Logging Services project.
@@ -43,7 +43,7 @@
</p>
</section>
- <section name="Stable Releases">
+ <section id="stable" name="Stable Releases">
<p>
The following stable releases are
available:
</p>
@@ -53,7 +53,7 @@
</ul>
</section>
- <section name="Developer Releases">
+ <section id="developer" name="Developer Releases">
<p>
The following development snapshots are
available:
</p>
@@ -67,7 +67,7 @@
</ul>
</section>
- <section name="Archive Releases">
+ <section id="archive" name="Archive Releases">
<p>
Previous releases of log4net are
available from the sourceforge site:
</p>
1.4 +1 -1 logging-log4net/xdocs/src/history.xml
Index: history.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/history.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- history.xml 20 Feb 2005 19:29:14 -0000 1.3
+++ history.xml 2 May 2005 20:57:50 -0000 1.4
@@ -24,7 +24,7 @@
<meta name="keywords" content="log4net project history, log4net" />
<body>
- <section name="log4net Project History">
+ <section id="main" name="log4net Project History">
<p>
The log4net project was started by <a
href="http://www.neoworks.com";>NeoWorks Limited</a>
1.4 +6 -6 logging-log4net/xdocs/src/index.xml
Index: index.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/index.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- index.xml 17 Jan 2005 20:25:51 -0000 1.3
+++ index.xml 2 May 2005 20:57:50 -0000 1.4
@@ -24,9 +24,9 @@
<meta name="keywords" content=".net, C#, VB.NET, logging, tracing,
component, framework, API, log4net" />
<body>
- <section name="About log4net">
+ <section id="main" name="About log4net">
- <section name="Introduction">
+ <section id="intro" name="Introduction">
<p>
log4net is a tool to help the
programmer output log statements to a variety
of output targets. log4net is a port of
the excellent log4j framework to the
@@ -42,7 +42,7 @@
</p>
</section>
- <section name="Project Status">
+ <section id="status" name="Project Status">
<p>
log4net is an effort undergoing
incubation at the Apache Software
Foundation (ASF), sponsored by the
Apache Logging Services project.
@@ -55,9 +55,9 @@
</p>
</section>
- <section name="Contributors">
+ <section id="contributors" name="Contributors">
- <section name="Active Committers">
+ <section id="active" name="Active Committers">
<ul>
<li>
@@ -79,7 +79,7 @@
</section>
- <section name="Community Contributors">
+ <section id="community" name="Community
Contributors">
<ul>
<li>
1.3 +3 -3 logging-log4net/xdocs/src/license.xml
Index: license.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/license.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- license.xml 17 Jan 2005 20:25:51 -0000 1.2
+++ license.xml 2 May 2005 20:57:50 -0000 1.3
@@ -24,9 +24,9 @@
<meta name="keywords" content="log4net license, log4net" />
<body>
- <section name="log4net License">
+ <section id="main" name="log4net License">
- <section name="Current License">
+ <section id="current" name="Current License">
<p>
The Apache Software License Version 2.0
applies to all releases of
log4net starting with log4net 1.2.1.
@@ -259,7 +259,7 @@
]]></source>
</section>
- <section name="Previous License">
+ <section id="archive" name="Previous License">
<p>
Previous releases of log4net were
released under the Apache Software License Version 1.1.
</p>
1.3 +1 -1 logging-log4net/xdocs/src/roadmap.xml
Index: roadmap.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/roadmap.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- roadmap.xml 17 Jan 2005 20:25:51 -0000 1.2
+++ roadmap.xml 2 May 2005 20:57:50 -0000 1.3
@@ -24,7 +24,7 @@
<meta name="keywords" content="log4net development roadmap, log4net
roadmap, log4net plan, log4net" />
<body>
- <section name="log4net Development Roadmap">
+ <section id="main" name="log4net Development Roadmap">
<p>
Not yet available.
</p>
1.7 +5 -5 logging-log4net/xdocs/src/support.xml
Index: support.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/support.xml,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- support.xml 11 Mar 2005 23:03:21 -0000 1.6
+++ support.xml 2 May 2005 20:57:50 -0000 1.7
@@ -24,7 +24,7 @@
<meta name="keywords" content="log4net support, log4net" />
<body>
- <section name="log4net Support">
+ <section id="main" name="log4net Support">
<p>
log4net user support is provided via a mailing
list. Discussion on log4net is held on the
@@ -32,7 +32,7 @@
is likely that your question has been answered
before.
</p>
- <section name="Mailing List Archives">
+ <section id="mlist-archive" name="Mailing List
Archives">
<p>
You can browse the mailing list
archives at the following locations:
</p>
@@ -45,7 +45,7 @@
</ul>
</section>
- <section name="Subscribe">
+ <section id="mlist-subscribe" name="Subscribe">
<p>
Subscribe to either the list or to the
digest list:
</p>
@@ -67,7 +67,7 @@
</ul>
</section>
- <section name="Unsubscribe">
+ <section id="mlist-unsubscribe" name="Unsubscribe">
<p>
To unsubscribe send an email to the
relevant email address:
</p>
@@ -89,7 +89,7 @@
</ul>
</section>
- <section name="Posting">
+ <section id="mlist-posting" name="Posting">
<p>
Before posting please read the
following guidelines:
</p>
1.6 +9 -9 logging-log4net/xdocs/src/release/building.xml
Index: building.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/building.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- building.xml 21 Mar 2005 19:40:09 -0000 1.5
+++ building.xml 2 May 2005 20:57:50 -0000 1.6
@@ -24,7 +24,7 @@
<meta name="keywords" content="building log4net, log4net" />
<body>
- <section name="Building log4net">
+ <section id="main" name="Building log4net">
<sectionMenu name="Contents" />
<p>
@@ -36,12 +36,12 @@
name key file. See the Strong Name section
below.
</p>
- <section name="Visual Studio .NET" id="id_1">
+ <section id="vsnet" name="Visual Studio .NET">
<p>
Visual Studio .NET 2002 and 2003 are
supported build platforms for log4net.
</p>
- <section name="Visual Studio .NET 2002"
id="id_2">
+ <section id="vsnet-2002" name="Visual Studio
.NET 2002">
<p>
The log4net distribution
includes a solution and project file
for Visual Studio .NET 2002.
Open the <span class="code">log4net.sln</span>
@@ -58,7 +58,7 @@
</ul>
</section>
- <section name="Visual Studio .NET 2003"
id="id_3">
+ <section id="vsnet-2003" name="Visual Studio
.NET 2003">
<p>
Open the Visual Studio .NET
2002 solution file as above.
Visual Studio will convert the
solution and project files
@@ -74,7 +74,7 @@
</section>
</section>
- <section name="NAnt">
+ <section id="nant" name="NAnt">
<p>
The log4net distribution is built using
the NAnt tool.
NAnt version 0.85 is required to build
log4net, it is
@@ -108,7 +108,7 @@
build.cmd compile-all</pre></div>
</section>
- <section name="Strong Name">
+ <section id="sn" name="Strong Name">
<p>
In order to build the Release builds of
log4net a Strong
Name key is required.
@@ -126,17 +126,17 @@
</p>
</section>
- <section name="SDK Reference">
+ <section id="sdk" name="SDK Reference">
<p>
NDoc is used to build the log4net SDK
documentation.
NDoc is available from <a
href="http://ndoc.sourceforge.net";>ndoc.sourceforge.net</a>.
</p>
</section>
- <section name="HTML Documentation">
+ <section id="html" name="HTML Documentation">
<p>
The log4net HTML documentation is built
using Velocity.
- The source are XML files in the <span
class="code">xdcos/src</span> directory.
+ The source are XML files in the <span
class="code">xdocs/src</span> directory.
Building the documentation requires
Java, Ant, and Velocity.
Run ant from within the <span
class="code">xdocs</span> directory.
</p>
1.10 +24 -24 logging-log4net/xdocs/src/release/config-examples.xml
Index: config-examples.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/config-examples.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- config-examples.xml 21 Mar 2005 19:40:09 -0000 1.9
+++ config-examples.xml 2 May 2005 20:57:50 -0000 1.10
@@ -24,11 +24,11 @@
<meta name="keywords" content="building log4net, log4net" />
<body>
- <section name="log4net Config Examples">
+ <section id="main" name="log4net Config Examples">
<sectionMenu name="Contents" />
- <section name="Overview">
+ <section id="overview" name="Overview">
<p>
This document presents example
configurations for the built-in appenders.
These configurations are designed to
work with the
@@ -42,7 +42,7 @@
</p>
</section>
- <section name="AdoNetAppender">
+ <section id="adonetappender" name="AdoNetAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.AdoNetAppender.html">log4net.Appender.AdoNetAppender</a>.
</p>
@@ -50,7 +50,7 @@
The configuration of the <span
class="code">AdoNetAppender</span> depends on the
provider selected for the target
database. Here are some examples.
</p>
- <section name="MS SQL Server">
+ <section id="adonetappender-mssql" name="MS SQL
Server">
<p>
The following example shows how
to configure the <span class="code">AdoNetAppender</span>
to log messages to a SQL Server
database. The events are written in batches of 100
@@ -132,7 +132,7 @@
]]></source>
</section>
- <section name="MS Access">
+ <section id="adonetappender-msa" name="MS
Access">
<p>
This example shows how to write
events to an Access Database.
</p>
@@ -184,7 +184,7 @@
]]></source>
</section>
- <section name="Oracle9i">
+ <section id="adonetappender-o9" name="Oracle9i">
<p>
This example shows how to write
events to an Oracle9i Database.
</p>
@@ -250,7 +250,7 @@
]]></source>
</section>
- <section name="Oracle8i">
+ <section id="adonetappender-o8" name="Oracle8i">
<p>
This example shows how to write
events to an Oracle8i Database.
</p>
@@ -299,7 +299,7 @@
]]></source>
</section>
- <section name="IBM DB2">
+ <section id="adonetappender-db2" name="IBM DB2">
<p>
This example shows how to write
events to an IBM DB2 8.2 Database.
The following syntax should
also work with older DB2 database servers.
@@ -386,7 +386,7 @@
</section>
- <section name="AspNetTraceAppender">
+ <section id="aspnettraceappender"
name="AspNetTraceAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.AspNetTraceAppender.html">log4net.Appender.AspNetTraceAppender</a>.
</p>
@@ -406,7 +406,7 @@
]]></source>
</section>
- <section name="BufferingForwardingAppender">
+ <section id="bufferingforwardingappender"
name="BufferingForwardingAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.BufferingForwardingAppender.html">log4net.Appender.BufferingForwardingAppender</a>.
</p>
@@ -439,7 +439,7 @@
]]></source>
</section>
- <section name="ColoredConsoleAppender">
+ <section id="coloredconsoleappender"
name="ColoredConsoleAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.ColoredConsoleAppender.html">log4net.Appender.ColoredConsoleAppender</a>.
</p>
@@ -481,7 +481,7 @@
]]></source>
</section>
- <section name="ConsoleAppender">
+ <section id="consoleappender" name="ConsoleAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.ConsoleAppender.html">log4net.Appender.ConsoleAppender</a>.
</p>
@@ -510,7 +510,7 @@
]]></source>
</section>
- <section name="EventLogAppender">
+ <section id="eventlogappender" name="EventLogAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.EventLogAppender.html">log4net.Appender.EventLogAppender</a>.
</p>
@@ -545,7 +545,7 @@
</p>
</section>
- <section name="FileAppender">
+ <section id="fileappender" name="FileAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.FileAppender.html">log4net.Appender.FileAppender</a>.
</p>
@@ -594,7 +594,7 @@
]]></source>
</section>
- <section name="ForwardingAppender">
+ <section id="forwardingappender"
name="ForwardingAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.ForwardingAppender.html">log4net.Appender.ForwardingAppender</a>.
</p>
@@ -615,7 +615,7 @@
]]></source>
</section>
- <section name="MemoryAppender">
+ <section id="memoryappender" name="MemoryAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.MemoryAppender.html">log4net.Appender.MemoryAppender</a>.
</p>
@@ -630,7 +630,7 @@
]]></source>
</section>
- <section name="NetSendAppender">
+ <section id="netsendappender" name="NetSendAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.NetSendAppender.html">log4net.Appender.NetSendAppender</a>.
</p>
@@ -657,7 +657,7 @@
]]></source>
</section>
- <section name="OutputDebugStringAppender">
+ <section id="outputdebugstringappender"
name="OutputDebugStringAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.OutputDebugStringAppender.html">log4net.Appender.OutputDebugStringAppender</a>.
</p>
@@ -674,7 +674,7 @@
]]></source>
</section>
- <section name="RemotingAppender">
+ <section id="remotingappender" name="RemotingAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.RemotingAppender.html">log4net.Appender.RemotingAppender</a>.
</p>
@@ -715,7 +715,7 @@
]]></source>
</section>
- <section name="RollingFileAppender">
+ <section id="rollingfileappender"
name="RollingFileAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.RollingFileAppender.html">log4net.Appender.RollingFileAppender</a>.
</p>
@@ -804,7 +804,7 @@
]]></source>
</section>
- <section name="SmtpAppender">
+ <section id="smtpappender" name="SmtpAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.SmtpAppender.html">log4net.Appender.SmtpAppender</a>.
</p>
@@ -873,7 +873,7 @@
]]></source>
</section>
- <section name="SmtpPickupDirAppender">
+ <section id="smtppickupdirappender"
name="SmtpPickupDirAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.SmtpPickupDirAppender.html">log4net.Appender.SmtpPickupDirAppender</a>.
</p>
@@ -915,7 +915,7 @@
]]></source>
</section>
- <section name="TraceAppender">
+ <section id="traceappender" name="TraceAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.TraceAppender.html">log4net.Appender.TraceAppender</a>.
</p>
@@ -935,7 +935,7 @@
]]></source>
</section>
- <section name="UdpAppender">
+ <section id="udpappender" name="UdpAppender">
<p>
For full details see the SDK Reference
entry: <a
href="sdk/log4net.Appender.UdpAppender.html">log4net.Appender.UdpAppender</a>.
</p>
1.4 +20 -20 logging-log4net/xdocs/src/release/example-apps.xml
Index: example-apps.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/example-apps.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- example-apps.xml 16 Apr 2005 23:31:29 -0000 1.3
+++ example-apps.xml 2 May 2005 20:57:50 -0000 1.4
@@ -24,19 +24,19 @@
<meta name="keywords" content="log4net examples, log4net" />
<body>
- <section name="log4net Examples">
+ <section id="main" name="log4net Examples">
<sectionMenu name="Contents" />
- <section name="Overview">
+ <section id="overview" name="Overview">
<p>
The following examples are only
available in the log4net release download, not
on-line. To obtain the examples <a
href="../downloads.html">download</a> one of the log4net releases.
</p>
</section>
- <section name="Building Examples">
- <section name="Building An Example">
+ <section id="building" name="Building Examples">
+ <section id="building-1" name="Building An
Example">
<p>
A single example can be build
by running <span class="code">nant</span> from
the example directory.
@@ -48,7 +48,7 @@
</p>
<p>
<span class="code">nant</span>
can be run in any directory containing a
- <span
class="code">nant.build</span> file. The typical behaviour of the build file
+ <span
class="code">nant.build</span> file. The typical behavior of the build file
is to build all projects under
the current directory.
</p>
<p>
@@ -58,7 +58,7 @@
</p>
</section>
- <section name="Building All Examples">
+ <section id="building-all" name="Building All
Examples">
<p>
To build all the examples
either run <span class="code">nant</span> in the
<span
class="code">examples</span> directory or you can specify the
@@ -66,7 +66,7 @@
</p>
</section>
- <section name="Visual Studio .NET 2002">
+ <section id="building-vsnet" name="Visual
Studio .NET 2002">
<p>
There are Visual Studio .NET
2002 project files for the .NET 1.0 framework.
The solution files for C++, C#
and VB are in the <a href="../../examples/net/1.0">examples\net\1.0</a>
@@ -75,9 +75,9 @@
</section>
</section>
- <section name="Examples">
+ <section id="examples" name="Examples">
- <section name="Tutorial - ConsoleApp">
+ <section id="consoleapp" name="Tutorial -
ConsoleApp">
<p>
ConsoleApp shows how to write a
simple console application that initializes
logging and logs various events.
@@ -117,7 +117,7 @@
</p>
</section>
- <section name="Tutorial - WebApp">
+ <section id="webapp" name="Tutorial - WebApp">
<p>
ConsoleApp shows how to write a
simple ASP.NET web application that initializes
logging and logs various events.
@@ -138,12 +138,12 @@
To run this example you need to
have an ASP.NET container application to
host the web application, for
example IIS. In IIS create a new virtual
directory pointing to the
WebApp src directory. Configure IIS to recognize
- this virtual directory as an
application. Open up a webrowser, navigate to
+ this virtual directory as an
application. Open up a web browser, navigate to
the virtual directory and to
the <span class="code">WebForm1.aspx</span> page within it.
</p>
</section>
- <section name="Remoting - RemotingClient">
+ <section id="remotingclient" name="Remoting -
RemotingClient">
<p>
The RemotingClient application
is a simple console application that configures
log4net with the
RemotingAppender. This appender will attempt to deliver the
@@ -166,7 +166,7 @@
</p>
</section>
- <section name="Remoting - RemotingServer">
+ <section id="remotingserver" name="Remoting -
RemotingServer">
<p>
The RemotingServer application
is a simple console application that listens for
logging events from a remote
RemotingAppender and then logs them through the
@@ -191,7 +191,7 @@
</p>
</section>
- <section name="Repository - SimpleModule">
+ <section id="rep-simple" name="Repository -
SimpleModule">
<p>
The SimpleModule is a class
library that is intended to be used as part of
the SimpleApp example,
@@ -227,7 +227,7 @@
</p>
</section>
- <section name="Repository - SharedModule">
+ <section id="rep-shared" name="Repository -
SharedModule">
<p>
The SharedModule is a class
library that is intended to be used as part of
the SimpleApp example,
@@ -262,7 +262,7 @@
</p>
</section>
- <section name="Repository - SimpleApp">
+ <section id="rep-app" name="Repository -
SimpleApp">
<p>
The SimpleApp example uses the
SimpleModule and SharedModule to demonstrate
the ways in which multiple
assemblies within the same process may be
@@ -297,7 +297,7 @@
</p>
</section>
- <section name="Extensibility - EventIDLogApp">
+ <section id="eventidlogapp" name="Extensibility
- EventIDLogApp">
<p>
The EventIDLogApp example
demonstrates using the log4net.Ext.EventID extension.
The extension needs to be built
separately from the
@@ -319,7 +319,7 @@
</p>
</section>
- <section name="Extensibility - TraceLogApp">
+ <section id="tracelogapp" name="Extensibility -
TraceLogApp">
<p>
The TraceLogApp example
demonstrates using the log4net.Ext.Trace extension.
The extension needs to be built
separately from the
@@ -341,7 +341,7 @@
</p>
</section>
- <section name="SampleAppenders">
+ <section id="sampleappenders"
name="SampleAppenders">
<p>
This project includes the
following example appenders.
</p>
@@ -375,7 +375,7 @@
</p>
</section>
- <section name="Performance - NotLogging">
+ <section id="perf-notlogging" name="Performance
- NotLogging">
<p>
The NotLogging example
benchmarks the performance of log4net logging statements in
user code in various scenarios
including when logging is disabled.
1.3 +43 -43 logging-log4net/xdocs/src/release/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/faq.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- faq.xml 21 Mar 2005 19:40:09 -0000 1.2
+++ faq.xml 2 May 2005 20:57:50 -0000 1.3
@@ -24,12 +24,12 @@
<meta name="keywords" content="log4net frequently asked questions,
log4net faq, log4net" />
<body>
- <section name="log4net Manual - Frequently Asked Questions">
+ <section id="main" name="log4net Manual - Frequently Asked
Questions">
<sectionMenu name="Contents" />
- <section name="Information">
+ <section id="information" name="Information">
- <section name="What is log4net?">
+ <section id="what-is-log4net" name="What is
log4net?">
<p>
log4net is a tool to help the
programmer output log statements to a variety of
output targets.
@@ -57,7 +57,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Is log4net a reliable logging
system?">
+ <section id="reliability" name="Is log4net a
reliable logging system?">
<p>
No. log4net is not reliable. It
is a best-effort and <em>fail-stop</em> logging system.
</p>
@@ -83,7 +83,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="What are the prerequisites for
log4net?">
+ <section id="prerequisites" name="What are the
prerequisites for log4net?">
<p>
log4net runs on many different
frameworks and each framework has its own requirements.
As a rule of thumb you will
need an ECMA-335 compliant CLI runtime, for example,
@@ -98,7 +98,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Is there example code for using
log4net?">
+ <section id="examples" name="Is there example
code for using log4net?">
<p>
There is a directory containing
examples in <span class="code">log4net\examples</span>.
The examples are broken down by
framework.
@@ -107,7 +107,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="What are the features of
log4net?">
+ <section id="features" name="What are the
features of log4net?">
<ul>
<li>
log4net is optimized
for speed.</li>
@@ -143,7 +143,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Is log4net thread-safe?">
+ <section id="thread-safe" name="Is log4net
thread-safe?">
<p>
Yes, log4net is thread-safe.
</p>
@@ -151,7 +151,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="What does log output look like?">
+ <section id="output" name="What does log output
look like?">
<p>
The log output can be
customized in many ways. Moreover, one can completely
override the output format by
implementing one's own <span class="code">ILayout</span>
@@ -185,7 +185,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="What are Loggers?">
+ <section id="loggers" name="What are Loggers?">
<p>
The logger concept lies at the
heart of log4net's configuration. Loggers are organized into a
hierarchy and give the
programmer <em>run-time</em> control on which logging statements
@@ -199,7 +199,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Why should I donate my
extensions to log4net back to the project?">
+ <section id="contributing" name="Why should I
donate my extensions to log4net back to the project?">
<p>
Contrary to the GNU Public
License (GPL) the Apache Software License does not
make any claims over your
extensions. By extensions, we mean totally new code
@@ -232,7 +232,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="What should I keep in mind when
contributing code?">
+ <section id="contributing-guidelines"
name="What should I keep in mind when contributing code?">
<ol>
<li>
Stick to the existing
indentation style even if you hate it.
@@ -260,7 +260,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="How fast do bugs in log4net get
fixed?">
+ <section id="bug-fixes" name="How fast do bugs
in log4net get fixed?">
<p>
As fast as they get reported ;-)
</p>
@@ -268,7 +268,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="What is the history of log4net?">
+ <section id="history" name="What is the history
of log4net?">
<p>
log4net is a port of the
popular <a href="http://logging.apache.org/log4j/";>log4j</a> logging library.
The initial port was done in
June 2001, since then we have tried to remain in the
@@ -278,7 +278,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Where can I find the latest
distribution of log4net?">
+ <section id="download" name="Where can I find
the latest distribution of log4net?">
<p>
The log4net <a
href="http://logging.apache.org/log4net/";>home page</a> is a good place to
start.
</p>
@@ -288,9 +288,9 @@
</section>
- <section name="Configuration">
+ <section id="configuration" name="Configuration">
- <section name="How can I change log behavior at
runtime?">
+ <section id="dynamic" name="How can I change
log behavior at runtime?">
<p>
Logging behavior can be set
using configuration files which are parsed at runtime.
Using configuration files the
programmer can define loggers and set their
@@ -308,7 +308,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="How do I completely disable all
logging at runtime?">
+ <section id="runtime-disable" name="How do I
completely disable all logging at runtime?">
<p>
Setting the <span
class="code">Threshold</span> on the Hierarchy to Level OFF will disable all
logging from that Hierarchy.
This can be done in the log4net configuration file
@@ -320,7 +320,7 @@
</section>
<p><a href="#top">Back to Top</a></p>
- <section name="What are the configurable
options for an appender?">
+ <section id="appender-options" name="What are
the configurable options for an appender?">
<p>
log4net uses public properties
to configure components such as
Appenders, Layouts, Loggers etc.
@@ -339,7 +339,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Is it possible to direct log
output to different appenders by level?">
+ <section id="appender-level" name="Is it
possible to direct log output to different appenders by level?">
<p>
Yes it is. Setting the <span
class="code">Threshold</span> option of any appender extending
<span
class="code">AppenderSkeleton</span>, (most log4net appenders extend
@@ -367,7 +367,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Is there a way to get log4net to
automatically reload a configuration file if it changes?">
+ <section id="config-reload" name="Is there a
way to get log4net to automatically reload a configuration file if it changes?">
<p>
Yes. The <span
class="code">XmlConfigurator</span> supports automatic
reloading through the <span
class="code">ConfigureAndWatch</span> APIs. See the API
@@ -377,7 +377,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Can I load an appender from
another assembly?">
+ <section id="appender-assembly" name="Can I
load an appender from another assembly?">
<p>
Yes. When specifying the type
in the configuration file you can give the assembly
qualified name of the type. For
example:
@@ -398,7 +398,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="How do I get the Public Key for
an assembly?">
+ <section id="assembly-public-key" name="How do
I get the Public Key for an assembly?">
<p>
The fully qualified name for an
assembly includes the version, culture and
public key. The public key is
derived from the strong name used to identify
@@ -413,9 +413,9 @@
</section>
- <section name="Implementing Logging">
+ <section id="implementing" name="Implementing Logging">
- <section name="Are there any suggested ways for
naming loggers?">
+ <section id="naming" name="Are there any
suggested ways for naming loggers?">
<p>
Yes, there are.
</p>
@@ -463,7 +463,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="How do I get the fully-qualified
name of a class in a static block?">
+ <section id="static-class-name" name="How do I
get the fully-qualified name of a class in a static block?">
<p>
You can easily retrieve the
fully-qualified name of a class in a static block
for class <span
class="code">X</span>, with the statement <span
class="code">typeof(X).Name</span>.
@@ -498,7 +498,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="What is the fastest way of (not)
logging?">
+ <section id="perf-not-logging" name="What is
the fastest way of (not) logging?">
<p>
For some logger <span
class="code">log</span>, writing,
</p>
@@ -530,7 +530,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="What is REALLY the FASTEST way
of (not) logging?">
+ <section id="perf-not-logging2" name="What is
REALLY the FASTEST way of (not) logging?">
<p>
So you don't think that the
previous FAQ is really the fastest way
of not logging? Well there is a
faster way but it does have some
@@ -585,7 +585,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Can the outputs of multiple
client request go to different log files?">
+ <section id="multiple-files" name="Can the
outputs of multiple client request go to different log files?">
<p>
Many developers are confronted
with the problem of distinguishing the log
output originating from the
same class but different client requests. They come
@@ -609,7 +609,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Logger instances seem to be
create only. Why isn't there a method to remove logger instances?">
+ <section id="remove-logger" name="Logger
instances seem to be create only. Why isn't there a method to remove logger
instances?">
<p>
It is quite nontrivial to
define the semantics of a "removed" logger which is
still referenced by the user.
@@ -618,7 +618,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="How do I get multiple process to
log to the same file?">
+ <section id="single-file" name="How do I get
multiple process to log to the same file?">
<p>
The <span
class="code">FileAppender</span> holds a write lock on the log
file while it is logging. This
prevents other processes from writing to the
@@ -635,7 +635,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="If I have many processes across
multiple hosts (possibly across multiple time zones) logging to the same file
using the method above, what happens to timestamps?">
+ <section id="distributed" name="If I have many
processes across multiple hosts (possibly across multiple time zones) logging
to the same file using the method above, what happens to timestamps?">
<p>
The timestamp is created when
the logging event is created. That is so say,
when the <span
class="code">Debug</span>, <span class="code">Info</span>,
@@ -651,7 +651,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="When should I log my first
message?">
+ <section id="first-log" name="When should I log
my first message?">
<p>
The simple answer is as soon as
possible. The long answer is more complex.
</p>
@@ -676,9 +676,9 @@
</section>
- <section name="Customization">
+ <section id="customization" name="Customization">
- <section name="Can the log output format be
customized?">
+ <section id="custom-output" name="Can the log
output format be customized?">
<p>
Yes. You can implement the
<span class="code">log4net.Layout.ILayout</span>
interface to create you own
customized log format, or you can extend the
@@ -690,7 +690,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Can I write a custom appender?">
+ <section id="custom-appender" name="Can I write
a custom appender?">
<p>
Yes. You can implement the
<span class="code">log4net.Appender.IAppender</span>
interface to create you own
customized appender. We recommend that you extend the
@@ -716,7 +716,7 @@
</section>
- <section name="Troubleshooting">
+ <section id="troubleshooting" name="Troubleshooting">
<section id="internalDebug" name="How do I
enable log4net internal debugging?">
<p>
@@ -831,7 +831,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Why can't I log to a
FileAppender from a web application?">
+ <section id="trouble-file-perm" name="Why can't
I log to a FileAppender from a web application?">
<p>
The web application runs as a
special user account on the web server
called ASPNET. This account has
restricted permissions to protect the
@@ -844,7 +844,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="Why doesn't the logging in my
service work?">
+ <section id="trouble-service" name="Why doesn't
the logging in my service work?">
<p>
A windows service runs as a
user account specified in the services
control panel. This account may
have restricted permissions, make
@@ -865,7 +865,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="I am having trouble using the
AdoNetAppender to connect to my database?">
+ <section id="trouble-db" name="I am having
trouble using the AdoNetAppender to connect to my database?">
<p>
For details on the different
ways in which ADO.NET can connect to a database see:
<a
href="http://msdn.microsoft.com/library/en-us/cpguide/html/cpconadonetconnections.asp";>Connecting
to a Data Source Using ADO.NET</a>.
@@ -880,7 +880,7 @@
<p><a href="#top">Back to Top</a></p>
- <section name="How do I report bugs?">
+ <section id="report-bugs" name="How do I report
bugs?">
<p>
See the <a
href="../../support.html">support</a> page for details.
</p>
@@ -890,9 +890,9 @@
</section>
- <section name="Miscellaneous">
+ <section id="misc" name="Miscellaneous">
- <section name="How do I make log4net appear in
the Visual Studio Add References dialog?">
+ <section id="vsnet-add-reference" name="How do
I make log4net appear in the Visual Studio Add References dialog?">
<p>
There is a good discussion of
this topic on Robert GcLaws blog:
<a
href="http://weblogs.asp.net/rmclaws/archive/2003/11/15/37743.aspx";>Building a
Better Server Control Experience, Part 2</a>.
1.5 +10 -10 logging-log4net/xdocs/src/release/features.xml
Index: features.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/features.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- features.xml 14 Feb 2005 03:15:37 -0000 1.4
+++ features.xml 2 May 2005 20:57:50 -0000 1.5
@@ -24,11 +24,11 @@
<meta name="keywords" content="log4net features, log4net" />
<body>
- <section name="log4net Features">
+ <section id="main" name="log4net Features">
<sectionMenu name="Contents" />
- <section name="Overview">
+ <section id="overview" name="Overview">
<p>
log4net is a tool to help the
programmer output log statements to a
variety of output targets. In case of
problems with an application,
@@ -50,7 +50,7 @@
</p>
</section>
- <section name="Features">
+ <section id="features" name="Features">
<ul>
<li><h3>Support for multiple
frameworks</h3></li>
<li><h3>Output to multiple logging
targets</h3></li>
@@ -64,7 +64,7 @@
</ul>
</section>
- <section name="Support for multiple frameworks">
+ <section id="frameworks" name="Support for multiple
frameworks">
<p>
log4net supports the following
frameworks:
</p>
@@ -78,7 +78,7 @@
</ul>
</section>
- <section name="Output to multiple logging targets">
+ <section id="appenders" name="Output to multiple
logging targets">
<p>
log4net ships with the following
appenders (not on all frameworks):
</p>
@@ -212,7 +212,7 @@
<p />
</section>
- <section name="Hierarchical logging architecture">
+ <section id="hierarchy" name="Hierarchical logging
architecture">
<p>
Hierarchical logging is an ideal fit
with component based development.
Each component has its own of logger.
When individually tested, the
@@ -226,7 +226,7 @@
</p>
</section>
- <section name="XML Configuration">
+ <section id="xml-config" name="XML Configuration">
<p>
log4net is configured using an XML
configuration file. The configuration
information can be embedded within
other XML configuration files
@@ -239,7 +239,7 @@
</p>
</section>
- <section name="Dynamic Configuration">
+ <section id="dynamic-config" name="Dynamic
Configuration">
<p>
log4net can monitor its configuration
file for changes and dynamically
apply changes made by the configurator.
The logging levels, appenders,
@@ -250,7 +250,7 @@
</p>
</section>
- <section name="Logging Context">
+ <section id="context" name="Logging Context">
<p>
log4net can collect logging context
data in a way that is transparent
to the developer at the point of
logging. The GlobalContext and the
@@ -262,7 +262,7 @@
</p>
</section>
- <section name="Proven architecture">
+ <section id="history" name="Proven architecture">
<p>
log4net is based on the highly
successful log4j logging library,
in development since 1996. This popular
and proven architecture has
1.6 +10 -10 logging-log4net/xdocs/src/release/framework-support.xml
Index: framework-support.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/framework-support.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- framework-support.xml 21 Mar 2005 19:40:09 -0000 1.5
+++ framework-support.xml 2 May 2005 20:57:50 -0000 1.6
@@ -24,11 +24,11 @@
<meta name="keywords" content="log4net supported frameworks, mono,
sscli, .net, log4net" />
<body>
- <section name="log4net Supported Frameworks">
+ <section id="main" name="log4net Supported Frameworks">
<sectionMenu name="Contents" />
- <section name="Summary of .NET frameworks supported by
log4net">
+ <section id="summary" name="Summary of .NET frameworks
supported by log4net">
<p>
log4net now builds on 6 frameworks:
</p>
@@ -78,7 +78,7 @@
</p>
</section>
- <section name="Appenders">
+ <section id="appenders" name="Appenders">
<p>
The appenders available to each
framework depend on the functionality of the
framework and the platform it runs on:
@@ -305,20 +305,20 @@
</div>
</section>
- <section name="Framework Specific Notes">
- <section name="Microsoft .NET Framework 1.0
(1.0.3705)">
+ <section id="notes" name="Framework Specific Notes">
+ <section id="net1.0" name="Microsoft .NET
Framework 1.0 (1.0.3705)">
<p>
none
</p>
</section>
- <section name="Microsoft .NET Framework 1.1
(1.1.4322)">
+ <section id="net1.1" name="Microsoft .NET
Framework 1.1 (1.1.4322)">
<p>
none
</p>
</section>
- <section name="Microsoft .NET Compact Framework
1.0 (1.0.5000)">
+ <section id="netcf1.0" name="Microsoft .NET
Compact Framework 1.0 (1.0.5000)">
<ul>
<li>
<h4>Assembly
attributes</h4>
@@ -439,13 +439,13 @@
</ul>
</section>
- <section name="Mono 1.0">
+ <section id="mono1.0" name="Mono 1.0">
<p>
none
</p>
</section>
- <section name="Microsoft Shared Source CLI 1.0">
+ <section id="sscli1.0" name="Microsoft Shared
Source CLI 1.0">
<ul>
<li>
<h4>FileSystemWatcher</h4>
@@ -483,7 +483,7 @@
</ul>
</section>
- <section name="CLI 1.0 Compatible">
+ <section id="cli1.0" name="CLI 1.0 Compatible">
<p>
This build of log4net is
designed to run on any ECMA CLI 1.0 compatible runtime.
The assembly does not support
any platform specific features. The build includes
1.9 +13 -13 logging-log4net/xdocs/src/release/release-notes.xml
Index: release-notes.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/release-notes.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- release-notes.xml 21 Mar 2005 00:37:27 -0000 1.8
+++ release-notes.xml 2 May 2005 20:57:50 -0000 1.9
@@ -24,13 +24,13 @@
<meta name="keywords" content="log4net release notes, log4net" />
<body>
- <section name="log4net Release Notes">
+ <section id="main" name="log4net Release Notes">
<sectionMenu name="Contents" />
- <section name="1.2.9 Beta">
+ <section id="1.2.9" name="1.2.9 Beta">
- <section name="Breaking Changes">
+ <section id="1.2.9-breaking" name="Breaking
Changes">
<ul>
<li>
<h3>Renamed
namespaces</h3>
@@ -83,7 +83,7 @@
</ul>
</section>
- <section name="New Features">
+ <section id="1.2.9-new" name="New Features">
<ul>
<li>
<h3>New CLI build</h3>
@@ -335,7 +335,7 @@
</ul>
</section>
- <section name="Other Changes">
+ <section id="1.2.9-other" name="Other Changes">
<ul>
<li>
<h3>FxCop
compliance</h3>
@@ -381,7 +381,7 @@
</section>
- <section name="1.2.0 Beta 8">
+ <section id="1.2.0b8" name="1.2.0 Beta 8">
<ul>
<li>
<h3>Changed assembly name to
<span class="code">log4net</span></h3>
@@ -485,7 +485,7 @@
</ul>
</section>
- <section name="1.2.0 Beta 7">
+ <section id="1.2.0b7" name="1.2.0 Beta 7">
<ul>
<li>
<h3>Updated to support the
Microsoft .NET Framework 1.1 Final</h3>
@@ -546,7 +546,7 @@
</ul>
</section>
- <section name="1.2.0 Beta 6">
+ <section id="1.2.0b6" name="1.2.0 Beta 6">
<ul>
<li>
<h3>Added support for multiple
frameworks</h3>
@@ -728,7 +728,7 @@
</ul>
</section>
- <section name="1.2.0 Beta 5">
+ <section id="1.2.0b5" name="1.2.0 Beta 5">
<ul>
<li>
<h3>Fixed Exception thrown when
DOM Configurator called with a null XML
@@ -744,7 +744,7 @@
</ul>
</section>
- <section name="1.2.0 Beta 4">
+ <section id="1.2.0b4" name="1.2.0 Beta 4">
<ul>
<li>
<h3>Added event specific
properties to the logging event object</h3>
@@ -814,7 +814,7 @@
</ul>
</section>
- <section name="1.2.0 Beta 3">
+ <section id="1.2.0b3" name="1.2.0 Beta 3">
<ul>
<li>
<h3>Added log4net.Ext.Trace
extension</h3>
@@ -859,7 +859,7 @@
</ul>
</section>
- <section name="1.2.0 Beta 2">
+ <section id="1.2.0b2" name="1.2.0 Beta 2">
<ul>
<li>
<h3>Added ADONetAppender</h3>
@@ -874,7 +874,7 @@
</ul>
</section>
- <section name="1.2.0 Beta 1">
+ <section id="1.2.0b1" name="1.2.0 Beta 1">
<ul>
<li>
<h3>Added 6 new examples</h3>
1.6 +16 -16
logging-log4net/xdocs/src/release/manual/configuration.xml
Index: configuration.xml
===================================================================
RCS file:
/home/cvs/logging-log4net/xdocs/src/release/manual/configuration.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- configuration.xml 21 Mar 2005 19:40:10 -0000 1.5
+++ configuration.xml 2 May 2005 20:57:50 -0000 1.6
@@ -24,11 +24,11 @@
<meta name="keywords" content="log4net configuration, log4net" />
<body>
- <section name="log4net Manual - Configuration">
+ <section id="main" name="log4net Manual - Configuration">
<sectionMenu name="Contents" />
- <section name="Configuration">
+ <section id="config" name="Configuration">
<p>
Inserting log requests into the
application code requires a fair amount of
planning and effort. Observation shows
that approximately 4 percent of code is
@@ -314,7 +314,7 @@
document.
</p>
- <section name="Configuration Attributes">
+ <section id="attributes" name="Configuration
Attributes">
<p>
The log4net configuration can
be configured using assembly-level attributes rather than
specified programmatically.
@@ -410,7 +410,7 @@
</p>
</section>
- <section name="Configuration Files">
+ <section id="files" name="Configuration Files">
<p>
Typically the log4net
configuration is specified using a file. This file can
be read in one of two ways:
@@ -420,7 +420,7 @@
<li>Reading the file contents
directly</li>
</ul>
- <section name=".config Files">
+ <section id="dot-config" name=".config
Files">
<p>
The <span
class="code">System.Configuration</span> API is only available if the
configuration data is
in the application's config file; the file named
@@ -477,7 +477,7 @@
</p>
</section>
- <section name="Reading Files Directly">
+ <section id="reading" name="Reading
Files Directly">
<p>
The XmlConfigurator can
directly read any XML file and use it to configure log4net.
This includes the
application's .config file; the file named <i>MyApp.exe.config</i>
@@ -553,7 +553,7 @@
</section>
- <section name="Configuration Syntax">
+ <section id="syntax" name="Configuration
Syntax">
<p>
log4net includes a
configuration reader that parses an XML DOM, the
<span
class="code">log4net.Config.XmlConfigurator</span>. This section defines the
@@ -663,7 +663,7 @@
</table>
</div>
- <section name="Appenders">
+ <section id="appenders"
name="Appenders">
<p>
Appenders may only be
defined as child elements of the <span class="code"><log4net></span>
element. Each appender
must be uniquely named. The implementing type for the appender must be
specified.
@@ -756,7 +756,7 @@
document.
</p>
- <section name="Filters">
+ <section id="filters"
name="Filters">
<p>
Filters
elements may only be defined as children of <span
class="code"><appender></span> elements.
</p>
@@ -850,7 +850,7 @@
<filter type="log4net.Filter.DenyAllFilter" />]]></source>
</section>
- <section name="Layouts">
+ <section id="layouts"
name="Layouts">
<p>
Layout elements
may only be defined as children of <span class="code"><appender></span>
elements.
</p>
@@ -908,7 +908,7 @@
</section>
</section>
- <section name="Root Logger">
+ <section id="root" name="Root Logger">
<p>
Only one root logger
element may only be defined and it must be a child of <span
class="code"><log4net></span> element.
The root logger is the
root of the logger hierarchy. All logger ultimately inherit from this logger.
@@ -961,7 +961,7 @@
</div>
</section>
- <section name="Loggers">
+ <section id="loggers" name="Loggers">
<p>
Logger elements may
only be defined as children of the <span class="code"><log4net></span>
element.
</p>
@@ -1039,7 +1039,7 @@
</div>
</section>
- <section name="Renderers">
+ <section id="renderers"
name="Renderers">
<p>
Renderer elements may
only be defined as children of the <span class="code"><log4net></span>
element.
</p>
@@ -1086,7 +1086,7 @@
</p>
</section>
- <section name="Parameters">
+ <section id="param" name="Parameters">
<p>
Parameter elements may
be children of many elements. See the specific elements above for details.
</p>
@@ -1163,7 +1163,7 @@
<param name="Threshold" value="WARN"/>
<param>]]></source>
- <section name="Extension
Parameters">
+ <section id="extension"
name="Extension Parameters">
<p>
Configuration
parameters map directly to writable properties on an object.
The properties
available depend on the actual type of the object being
@@ -1176,7 +1176,7 @@
</p>
</section>
- <section name="Compact
Parameter Syntax">
+ <section id="new-param"
name="Compact Parameter Syntax">
<p>
All parameters
may alternately be specified using the parameter name as the element name
rather than
using the <i>param</i> element and <i>name</i> attribute.
1.4 +8 -8 logging-log4net/xdocs/src/release/manual/contexts.xml
Index: contexts.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/manual/contexts.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- contexts.xml 17 Jan 2005 20:25:51 -0000 1.3
+++ contexts.xml 2 May 2005 20:57:50 -0000 1.4
@@ -24,7 +24,7 @@
<meta name="keywords" content="building log4net, log4net" />
<body>
- <section name="log4net Manual - Contexts">
+ <section id="main" name="log4net Manual - Contexts">
<sectionMenu name="Contents" />
<p>
@@ -44,7 +44,7 @@
Log4net supports different types of contextual
logging and contexts with different scopes.
</p>
- <section name="Scopes">
+ <section id="scopes" name="Scopes">
<p>
Contextual data can be set in different
scopes. These contexts have progressively narrower visibility.
In the logging event itself the values
from all of the contexts are combined together such that
@@ -95,7 +95,7 @@
</div>
</section>
- <section name="Context Properties">
+ <section id="properties" name="Context Properties">
<p>
The log4net contexts store properties,
i.e. name value pairs. The name is a string
the value is any object. A property can
be set as follows:
@@ -113,11 +113,11 @@
The <span
class="code">PatternLayout</span> supports rendering the value of a named
property using the <span
class="code">%property{name}</span> syntax. The value is
converted to a string by passing it to
the <span class="code">log4net.ObjectRenderer.RendererMap</span>
- which will locate any custom renderer
for the value type. The default behaviour for
+ which will locate any custom renderer
for the value type. The default behavior for
custom types is to call the object's
<span class="code">ToString()</span> method.
</p>
- <section name="Active Property Values">
+ <section id="active" name="Active Property
Values">
<p>
An active property value is one
who's value changes over time.
</p>
@@ -153,7 +153,7 @@
</section>
- <section name="Context Stacks">
+ <section id="stacks" name="Context Stacks">
<p>
Sometimes simple key value pairs are
not the most convenient way of capturing contextual
information. A stack of information is
a very convenient way of storing data especially
@@ -204,7 +204,7 @@
</p>
</section>
- <section name="Nested Diagnostic Contexts">
+ <section id="ndc" name="Nested Diagnostic Contexts">
<p>
The <span class="code">NDC</span>
(Nested Diagnostic Context) exists for compatibility
with older versions of log4net. This
helper class implements a stack which is stored
@@ -212,7 +212,7 @@
</p>
</section>
- <section name="Mapped Diagnostic Contexts">
+ <section id="mdc" name="Mapped Diagnostic Contexts">
<p>
The <span class="code">MDC</span>
(MappedDiagnostic Context) exists for compatibility
with older versions of log4net. This
helper class implements a properties map which is
1.4 +3 -3 logging-log4net/xdocs/src/release/manual/internals.xml
Index: internals.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/manual/internals.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- internals.xml 21 Mar 2005 19:40:10 -0000 1.3
+++ internals.xml 2 May 2005 20:57:50 -0000 1.4
@@ -24,10 +24,10 @@
<meta name="keywords" content="log4net internals, log4net" />
<body>
- <section name="log4net Manual - Internals">
+ <section id="main" name="log4net Manual - Internals">
<sectionMenu name="Contents" />
- <section name="Performance">
+ <section id="perf" name="Performance">
<p>
One of the often-cited arguments
against logging is its computational cost.
This is a legitimate concern as even
moderately sized applications can generate
@@ -140,7 +140,7 @@
</p>
</section>
- <section name="Logging Event Flow">
+ <section id="flow" name="Logging Event Flow">
<p>
The following is the series of steps
and checks that a messages goes through while being logged.
For the purposes of this example we
will document an <span class="code">INFO</span> level
1.6 +9 -9 logging-log4net/xdocs/src/release/manual/introduction.xml
Index: introduction.xml
===================================================================
RCS file:
/home/cvs/logging-log4net/xdocs/src/release/manual/introduction.xml,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- introduction.xml 14 Feb 2005 03:15:37 -0000 1.5
+++ introduction.xml 2 May 2005 20:57:50 -0000 1.6
@@ -24,10 +24,10 @@
<meta name="keywords" content="log4net manual, log4net" />
<body>
- <section name="log4net Manual - Introduction">
+ <section id="main" name="log4net Manual - Introduction">
<sectionMenu name="Contents" />
- <section name="Overview">
+ <section id="overview" name="Overview">
<p>
This document is based on <i>Short
introduction to log4j</i> by <i>Ceki Gülcü</i>.
</p>
@@ -76,7 +76,7 @@
</p>
</section>
- <section name="Frameworks">
+ <section id="frameworks" name="Frameworks">
<p>
Log4net is available for several
frameworks. For each supported framework an
assembly targeting that framework is
built:
@@ -96,7 +96,7 @@
</p>
</section>
- <section name="Loggers and Appenders">
+ <section id="loggers" name="Loggers and Appenders">
<p>
Log4net has three main components:
<i>loggers</i>, <i>appenders</i> and <i>layouts</i>.
These three types of components work
together to enable developers to log
@@ -106,7 +106,7 @@
<i>object renderers</i> that turn
objects into strings.
</p>
- <section name="Logger hierarchy">
+ <section id="hierarchy" name="Logger hierarchy">
<p>
The first and foremost
advantage of any logging API over plain
<span
class="code">System.Console.WriteLine</span>
@@ -548,7 +548,7 @@
</p>
</section>
- <section name="Appenders">
+ <section id="appenders" name="Appenders">
<p>
The ability to selectively
enable or disable logging requests based on their
logger is only part of the
picture. Log4net allows logging requests to print to
@@ -817,7 +817,7 @@
</div>
</section>
- <section name="Filters">
+ <section id="filters" name="Filters">
<p>
Appenders can filter the events
that are delivered to them. The filters can be
specified in the configuration
to allow fine control of the events that are
@@ -901,7 +901,7 @@
</p>
</section>
- <section name="Layouts">
+ <section id="layouts" name="Layouts">
<p>
More often than not, users wish
to customize not only the output destination
but also the output format.
This is accomplished by associating a <i>layout</i>
@@ -989,7 +989,7 @@
</div>
</section>
- <section name="Object Renderers">
+ <section id="renderers" name="Object Renderers">
<p>
Just as importantly, log4net
will render the content of the log message
according to user specified
criteria. For example, if you frequently need to
1.4 +3 -3 logging-log4net/xdocs/src/release/manual/plugins.xml
Index: plugins.xml
===================================================================
RCS file: /home/cvs/logging-log4net/xdocs/src/release/manual/plugins.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- plugins.xml 17 Jan 2005 20:25:51 -0000 1.3
+++ plugins.xml 2 May 2005 20:57:50 -0000 1.4
@@ -24,10 +24,10 @@
<meta name="keywords" content="log4net plugins, log4net" />
<body>
- <section name="log4net Manual - Plugins">
+ <section id="main" name="log4net Manual - Plugins">
<sectionMenu name="Contents" />
- <section name="Plugins">
+ <section id="plugins" name="Plugins">
<p>
Plugins are additional modular
components that are attached to a logger repository.
</p>
@@ -78,7 +78,7 @@
</li>
</ul>
- <section name="Plugin Attributes">
+ <section id="attributes" name="Plugin
Attributes">
<p>
Plugins can be configured using
the following assembly-level attributes:
</p>
1.4 +3 -3 logging-log4net/xdocs/src/release/manual/repositories.xml
Index: repositories.xml
===================================================================
RCS file:
/home/cvs/logging-log4net/xdocs/src/release/manual/repositories.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- repositories.xml 17 Jan 2005 20:25:51 -0000 1.3
+++ repositories.xml 2 May 2005 20:57:50 -0000 1.4
@@ -24,10 +24,10 @@
<meta name="keywords" content="building log4net, log4net" />
<body>
- <section name="log4net Manual - Repositories">
+ <section id="main" name="log4net Manual - Repositories">
<sectionMenu name="Contents" />
- <section name="Logging Repositories">
+ <section id="repository" name="Logging Repositories">
<p>
Logging repositories are considered
advanced functionality. The default behavior
should be sufficient for most users.
@@ -51,7 +51,7 @@
A repository created in this way will
need to be configured programmatically.
</p>
- <section name="Attributes">
+ <section id="attributes" name="Attributes">
<p>
An assembly may choose to
utilize a named logging repository rather than the default repository.
This completely separates the
logging for the assembly from the rest of the application.
