Repository: logging-log4j2 Updated Branches: refs/heads/master 19ca49174 -> 6b735e2ad
Anchors should precede subsections or subsection title will scroll offscreen when opening url with anchor link. Project: http://git-wip-us.apache.org/repos/asf/logging-log4j2/repo Commit: http://git-wip-us.apache.org/repos/asf/logging-log4j2/commit/6b735e2a Tree: http://git-wip-us.apache.org/repos/asf/logging-log4j2/tree/6b735e2a Diff: http://git-wip-us.apache.org/repos/asf/logging-log4j2/diff/6b735e2a Branch: refs/heads/master Commit: 6b735e2ad4acbf65fe8da120aa66cbb23738235f Parents: 19ca491 Author: rpopma <[email protected]> Authored: Sat Sep 27 23:35:26 2014 +0900 Committer: rpopma <[email protected]> Committed: Sat Sep 27 23:35:26 2014 +0900 ---------------------------------------------------------------------- src/site/xdoc/manual/lookups.xml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/logging-log4j2/blob/6b735e2a/src/site/xdoc/manual/lookups.xml ---------------------------------------------------------------------- diff --git a/src/site/xdoc/manual/lookups.xml b/src/site/xdoc/manual/lookups.xml index a7e2b8b..7bf01eb 100644 --- a/src/site/xdoc/manual/lookups.xml +++ b/src/site/xdoc/manual/lookups.xml @@ -34,8 +34,8 @@ <a href="./configuration.html#PropertySubstitution">Property Substitution</a> section of the <a href="./configuration.html">Configuration</a> page. </p> + <a name="AppMainArgsLookup"/> <subsection name="Application main arguments lookup"> - <a name="AppMainArgsLookup"/> <p> You can access the main arguments of an application if they have been set with: </p> @@ -112,8 +112,8 @@ public static void main(String args[]) { Using <code>${main:string}</code> gives you the next value in the argument list after the given string. </p> </subsection> + <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 @@ -129,8 +129,8 @@ public static void main(String args[]) { </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 @@ -145,8 +145,8 @@ public static void main(String args[]) { <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 @@ -160,8 +160,8 @@ public static void main(String args[]) { </PatternLayout> </File>]]></pre> </subsection> + <a name="JavaLookup"/> <subsection name="JavaLookup"> - <a name="JavaLookup"/> <p> The JavaLookup allows Java environment information to be retrieved in convenient preformatted strings using the <code>java:</code> prefix. @@ -224,8 +224,8 @@ public static void main(String args[]) { </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. @@ -238,8 +238,8 @@ public static void main(String args[]) { </File>]]></pre> <p><strong>Java's JNDI module is not available on Android.</strong></p> </subsection> + <a name="JmxRuntimeInputArgumentsLookup"/> <subsection name="JVM input arguments lookup (JMX)"> - <a name="JmxRuntimeInputArgumentsLookup"/> <p> Maps JVM input arguments -- but not <em>main</em> arguments -- using JMX to acquire the JVM arguments. </p> @@ -254,8 +254,8 @@ public static void main(String args[]) { </p> <p><strong>Java's JMX module is not available on Android.</strong></p> </subsection> + <a name="MapLookup"/> <subsection name="MapLookup"> - <a name="MapLookup"/> <p> The MapLookup serves several purposes. </p> @@ -291,8 +291,8 @@ public static void main(String args[]) { </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 @@ -316,8 +316,8 @@ public static void main(String args[]) { </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 @@ -328,8 +328,8 @@ public static void main(String args[]) { <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
