Author: bodewig
Date: Mon Mar 30 11:07:01 2015
New Revision: 1670051
URL: http://svn.apache.org/r1670051
Log:
LOG4NET-441 talk about 'you must configure logging in order to log'
Modified:
logging/log4net/branches/log4net-1.2.x/src/site/xdoc/release/faq.xml
Modified: logging/log4net/branches/log4net-1.2.x/src/site/xdoc/release/faq.xml
URL:
http://svn.apache.org/viewvc/logging/log4net/branches/log4net-1.2.x/src/site/xdoc/release/faq.xml?rev=1670051&r1=1670050&r2=1670051&view=diff
==============================================================================
--- logging/log4net/branches/log4net-1.2.x/src/site/xdoc/release/faq.xml
(original)
+++ logging/log4net/branches/log4net-1.2.x/src/site/xdoc/release/faq.xml Mon
Mar 30 11:07:01 2015
@@ -1162,6 +1162,36 @@ if(!log4net.LogManager.GetRepository().C
</section>
<p><a href="#top">Back to Top</a></p>
+ <section id="no-explicit-configuration"
+ name="log4net doesn't log at all">
+ <p>
+ You may have overlooked initialization code for
+ log4net in your application. log4net can be
+ initialized explicitly by calling one of the
+ configurators
+ (e.g. <code>BasicConfigurator</code> or
+ <code>XmlConfigurator</code> in the
+ <code>log4net.Config</code> namespace, or
+ implicitly by including the
+ <code>[XmlConfiguratorAttribute]</code> in the
+ assembly where log4net is first used.
+ </p>
+
+ <p>
+ See <a href="manual/configuration.html">the
+ manual</a> for more information. If you use
+ attributes to configure log4net then the order
+ by which assemblies are loaded may determine
+ whether you attributes are used or not.
+ Assembly load order may be different in DEBUG
+ and RELEASE mode. See also <a
+ href="#log-early">log4net doesn't log when built
+ in RELEASE mode</a>.
+ </p>
+
+ </section>
+ <p><a href="#top">Back to Top</a></p>
+
</section>
<section id="misc" name="Miscellaneous">
