svn commit: r1597688 - /logging/log4j/log4j2/trunk/src/site/xdoc/manual/lookups.xml

[ma...@apache.org]

Author: mattsicker
Date: Tue May 27 00:56:12 2014
New Revision: 1597688

URL: http://svn.apache.org/r1597688
Log:
Add XSD.

  - Moved anchors into sections.

Modified:
    logging/log4j/log4j2/trunk/src/site/xdoc/manual/lookups.xml

Modified: logging/log4j/log4j2/trunk/src/site/xdoc/manual/lookups.xml
URL: http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/manual/lookups.xml?rev=1597688&r1=1597687&r2=1597688&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/lookups.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/lookups.xml Tue May 27 00:56:12 2014
@@ -16,7 +16,9 @@
     limitations under the License.
 -->
 
-<document>
+<document xmlns="http://maven.apache.org/XDOC/2.0"
+          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+          xsi:schemaLocation="http://maven.apache.org/XDOC/2.0 http://maven.apache.org/xsd/xdoc-2.0.xsd">
     <properties>
         <title>Log4j 2 Lookups</title>
         <author email="rgoers@apache.org">Ralph Goers</author>
@@ -32,8 +34,8 @@
           <a href="./configuration.html#PropertySubstitution">Property Substitution</a> section of the
           <a href="./configuration.html">Configuration</a> page.
         </p>
-        <a name="ContextMapLookup"/>
         <subsection name="ContextMapLookup">
+          <a name="ContextMapLookup"/>
           <p>
             The ContextMapLookup allows applications to store data in the Log4j ThreadContext Map and
             then retrieve the values in the Log4j configuration. In the example below, the application
@@ -49,8 +51,8 @@
   </PatternLayout>
 </File>]]></pre>
         </subsection>
-        <a name="DateLookup"/>
         <subsection name="DateLookup">
+          <a name="DateLookup"/>
           <p>
             The DateLookup is somewhat unusual from the other lookups as it doesn't use the key to locate an item.
             Instead, the key can be used to specify a date format string that is valid for
@@ -65,8 +67,8 @@
   <SizeBasedTriggeringPolicy size="500" />
 </RollingFile>]]></pre>
         </subsection>
-        <a name="EnvironmentLookup"/>
         <subsection name="EnvironmentLookup">
+          <a name="EnvironmentLookup"/>
           <p>
             The EnvironmentLookup allows systems to configure environment variables, either in global files
             such as /etc/profile or in the startup scripts for applications, and then retrieve those variables
@@ -80,8 +82,8 @@
   </PatternLayout>
 </File>]]></pre>
         </subsection>
-        <a name="JNDILookup"/>
         <subsection name="JNDILookup">
+          <a name="JNDILookup"/>
           <p>
             The JNDILookup allows variables to be retrieved via JNDI. By default the key will be prefixed with
             java:comp/env/, however if the key contains a ":" no prefix will be added.
@@ -93,14 +95,16 @@
   </PatternLayout>
 </File>]]></pre>
         </subsection>
-        <a name="MapLookup"/>
         <subsection name="MapLookup">
+          <a name="MapLookup"/>
           <p>
             The MapLookup serves two purposes.
+          </p>
             <ol>
               <li>Provide the base for Properties declared in the configuration file.</li>
               <li>Retrieve values from MapMessages in LogEvents.</li>
             </ol>
+          <p>
             The first item simply means that the MapLookup is used to substitute properties that are defined
             in the configuration file. These variables are specified without a prefix - e.g. <code>${name}</code>.
             The second usage allows a value from the current
@@ -127,8 +131,8 @@
   </Routes>
 </Routing>]]></pre>
         </subsection>
-        <a name="StructuredDataLookup"/>
         <subsection name="StructuredDataLookup">
+          <a name="StructuredDataLookup"/>
           <p>
             The StructuredDataLookup is very similar to the MapLookup in that it will retrieve values from
             StructuredDataMessages. In addition to the Map values it will also return the name portion of the
@@ -152,8 +156,8 @@
   </Routes>
 </Routing>]]></pre>
         </subsection>
-        <a name="SystemPropertiesLookup"/>
         <subsection name="SystemPropertiesLookup">
+          <a name="SystemPropertiesLookup"/>
           <p>
             As it is quite common to define values inside and outside the application by using System Properties,
             it is only natural that they should be accessible via a Lookup. As system properties are often
@@ -164,8 +168,8 @@
   <File name="ApplicationLog" fileName="${sys:logPath}/app.log"/>
 </Appenders>]]></pre>
         </subsection>
-        <a name="WebLookup"/>
         <subsection name="WebLookup">
+          <a name="WebLookup"/>
           <p>
             The WebLookup allows applications to retrieve variables that are associated with the ServletContext.
             In addition to being able to retrieve various fields in the ServletContext, WebLookup supports looking