You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by gg...@apache.org on 2012/11/13 04:04:19 UTC
svn commit: r1408569 - /logging/log4j/log4j2/trunk/src/site/xdoc/index.xml
Author: ggregory
Date: Tue Nov 13 03:04:18 2012
New Revision: 1408569
URL: http://svn.apache.org/viewvc?rev=1408569&view=rev
Log:
Use the active voice.
Modified:
logging/log4j/log4j2/trunk/src/site/xdoc/index.xml
Modified: logging/log4j/log4j2/trunk/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/index.xml?rev=1408569&r1=1408568&r2=1408569&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/index.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/index.xml Tue Nov 13 03:04:18 2012
@@ -20,6 +20,7 @@
<properties>
<title>Log4J2 Guide</title>
<author email="rgoers@apache.org">Ralph Goers</author>
+ <author email="ggregory@apache.org">Gary Gregory</author>
</properties>
<body>
@@ -35,19 +36,19 @@
<h3>API Separation</h3>
<p>
- The API for Log4j is separate from the implementation. It is now clear to application developers
- what classes and methods they can use with compatibility being assured while allowing
- improvements to be made to the implementation.
+ The API for Log4j is separate from the implementation making it clear for application developers
+ which classes and methods they can use while ensuring forward compatibility. This allows the
+ Log4j team to improve the implementation safely and in a compatible manner.
</p>
<h3>Improved Performance</h3>
<p>
- Faster performance than Log4j 1.x in critical areas and similar performance to Logback in
- most circumstances. See <a href="performance.html">Performance</a> for more information.
+ Log4j 2 performs faster than Log4j 1.x in critical areas and similarly to Logback under most circumstances.
+ See <a href="performance.html">Performance</a> for more information.
</p>
<h3>Support for multiple APIs</h3>
<p>
- While the Log4j 2 API will provide the best performance, support for the SLF4J and Commons Logging
- APIs are provided.
+ While the Log4j 2 API will provide the best performance, Log4j 2 provides support for the SLF4J and
+ Commons Logging APIs.
</p>
<h3>Automatic Reloading of Configurations</h3>
<p>
@@ -56,21 +57,22 @@
</p>
<h3>Advanced Filtering</h3>
<p>
- Like Logback, Log4j 2 supports filtering based on context data, markers, regular expressions and
- other components in the Log event and can be specified to apply to all events before being passed
- to Loggers or as they pass through appenders. In addition, filters can also be associated with
- Loggers. Unlike Logback, a common Filter class can be used in any of these circumstances.
+ Like Logback, Log4j 2 supports filtering based on context data, markers, regular expressions,
+ and other components in the Log event. Filtering can be specified to apply to all events
+ before being passed to Loggers or as they pass through Appenders. In addition, filters can also
+ be associated with Loggers. Unlike Logback, you can use a common Filter class in any of these
+ circumstances.
</p>
<h3>Plugin Architecture</h3>
<p>
- All configurable components are defined as Log4j plugins. As such, no Log4j code must be changed to
- create a new Appender, Layout, Pattern Converter, etc. Log4j will automatically
- recognize properly defined plugins and use them when they are referenced in the configuration.
+ Log4j uses the plugin pattern to configure components. As such, you do not need to write code
+ to create and configure an Appender, Layout, Pattern Converter, and so on. Log4j automatically
+ recognizes plugins and uses them when a configuration references them.
</p>
<h3>Property Support</h3>
<p>
- Properties can be referenced in the configuration and either be directly replace or passed to the
- underlying component where they can be dynamically resolved. Properties can come from values
+ You can reference properties in a configuration, Log4j will directly replace them, or Log4j will
+ pass them to an underlying component that will dynamically resolve them. Properties come from values
defined in the configuration file, system properties, environment variables, the ThreadContext
Map, and data present in the event. Users can further customize the property providers by
adding their own <a href="../lookups.html">Lookup</a> Plugin.
@@ -84,9 +86,8 @@
</section>
<section name="Requirements">
<p>
- Log4j 2 requires Java 5 but will take advantage of enhancements in Java 6 to improve performance.
- Some features may require optional dependencies. These dependencies are
- specified in the documentation for those features.
+ Log4j 2 requires Java 5 but takes advantage of enhancements in Java 6 to improve performance.
+ Some features require optional dependencies; the documentation for these features specifies the dependencies.
</p>
</section>
@@ -94,7 +95,7 @@
<p>
Log4j 2 is now available for testing. The API for Log4j 2 is not compatible with Log4j 1.x, however an adapter
is available to allow applications to continue to use the Log4j 1.x API. Adapters are also available for
- Commons Logging and SLF4J.
+ Apache Commons Logging and SLF4J.
</p>
</section>