You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@logging.apache.org by ck...@apache.org on 2021/12/18 01:24:42 UTC

[logging-log4j2] 09/16: [DOC] update JNDI Lookup docs; property should be `enableJndiLookup`

This is an automated email from the ASF dual-hosted git repository.

ckozak pushed a commit to branch release-2.x
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git

commit 49de894e9a1cd15d3d702b6487bf9802e3ae3376
Author: Remko Popma <re...@yahoo.com>
AuthorDate: Sat Dec 18 09:31:30 2021 +0900

    [DOC] update JNDI Lookup docs; property should be `enableJndiLookup`
---
 src/site/xdoc/manual/lookups.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/site/xdoc/manual/lookups.xml b/src/site/xdoc/manual/lookups.xml
index b7df4fa..9bf6b80 100644
--- a/src/site/xdoc/manual/lookups.xml
+++ b/src/site/xdoc/manual/lookups.xml
@@ -267,9 +267,9 @@
         <a name="JndiLookup"/>
         <subsection name="Jndi Lookup">
           <p>
-            As of Log4j 2.16.0 JNDI operations require that <code>log4j2.enableJndiJava=true</code> be set as a system
+            As of Log4j 2.16.0 JNDI operations require that <code>log4j2.enableJndiLookup=true</code> be set as a system
             property or the corresponding environment variable for this lookup to function. See the
-            <a href="./configuration.html#enableJndiJava">enableJndiJava</a> system property.
+            <a href="./configuration.html#enableJndiLookup">enableJndiLookup</a> system property.
           </p>
           <p>
             The JndiLookup allows variables to be retrieved via JNDI. By default the key will be prefixed with