You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by ma...@apache.org on 2014/07/23 01:44:24 UTC
svn commit: r1612728 -
/logging/log4j/log4j2/trunk/src/site/xdoc/manual/extending.xml
Author: mattsicker
Date: Tue Jul 22 23:44:24 2014
New Revision: 1612728
URL: http://svn.apache.org/r1612728
Log:
Update extending manual to reference correct file names.
- Also added some more markup to make thing prettier.
Modified:
logging/log4j/log4j2/trunk/src/site/xdoc/manual/extending.xml
Modified: logging/log4j/log4j2/trunk/src/site/xdoc/manual/extending.xml
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/manual/extending.xml?rev=1612728&r1=1612727&r2=1612728&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/extending.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/extending.xml Tue Jul 22 23:44:24 2014
@@ -32,27 +32,28 @@
</p>
<subsection name="LoggerContextFactory">
<p>
- The LoggerContextFactory binds the Log4j API to its implementation. The Log4j LogManager
- locates a LoggerContextFactory by locating all instances of META-INF/log4j-provider.xml, a
- file that conforms to the java.util.Properties DTD, and then inspecting each to verify that it
- specifies a value for the "Log4jAPIVersion" property that conforms to the version required by the
- LogManager. If more than one valid implementation is located the value for "FactoryPriority" will
- be used to identify the factory with the highest priority.
- Finally, the value of the "LoggerContextFactory" property will be used to locate the
- LoggerContextFactory. In Log4j 2 this is provided by Log4jContextFactory.
+ The <code>LoggerContextFactory</code> binds the Log4j API to its implementation. The Log4j
+ <code>LogManager</code> locates a <code>LoggerContextFactory</code> by locating all instances of
+ <code>META-INF/log4j-provider.properties</code>, a standard <code>java.util.Properties</code> file,
+ and then inspecting each to verify that it specifies a value for the <var>Log4jAPIVersion</var> property
+ that conforms to the version required by the <code>LogManager</code>. If more than one valid
+ implementation is located the value for <var>FactoryPriority</var> will be used to identify the factory
+ with the highest priority. Finally, the value of the <var>LoggerContextFactory</var> property will be
+ used to locate the <code>LoggerContextFactory</code>. In Log4j 2 this is provided by
+ <code>Log4jContextFactory</code>.
</p>
<p>
Applications may change the LoggerContextFactory that will be used by
</p>
<ol>
- <li>Implementing a new LoggerContextFactory and creating a log4j-provider.xml to reference it making
- sure that it has the highest priority.
+ <li>Implementing a new <code>LoggerContextFactory</code> and creating a <code>log4j-provider.properties</code>
+ to reference it making sure that it has the highest priority.
</li>
- <li>Create a new log4j-provider.xml and configure it with the desired LoggerContextFactory making
- sure that it has the highest priority.
+ <li>Create a new <code>log4j-provider.xml</code> and configure it with the desired
+ <code>LoggerContextFactory</code> making sure that it has the highest priority.
</li>
- <li>Setting the system property "log4j2.loggerContextFactory" to the name of the LoggerContextFactory
- class to use.
+ <li>Setting the system property <var>log4j2.loggerContextFactory</var> to the name of the
+ <code>LoggerContextFactory</code> class to use.
</li>
<li>Setting the property "log4j2.loggerContextFactory" in a properties file named
"log4j2.LogManager.properties" to the name of the LoggerContextFactory class to use. The properties