svn commit: r1604345 - /logging/log4j/log4j2/trunk/src/site/xdoc/manual/jmx.xml

[rpopma]

Author: rpopma
Date: Sat Jun 21 12:52:49 2014
New Revision: 1604345

URL: http://svn.apache.org/r1604345
Log:
update docs to reflect ClientGUI application class was renamed to ClientGui

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

Modified: logging/log4j/log4j2/trunk/src/site/xdoc/manual/jmx.xml
URL: 
http://svn.apache.org/viewvc/logging/log4j/log4j2/trunk/src/site/xdoc/manual/jmx.xml?rev=1604345&r1=1604344&r2=1604345&view=diff
==============================================================================
--- logging/log4j/log4j2/trunk/src/site/xdoc/manual/jmx.xml (original)
+++ logging/log4j/log4j2/trunk/src/site/xdoc/manual/jmx.xml Sat Jun 21 12:52:49 
2014
@@ -132,9 +132,9 @@
       <p>To run the Log4j JMX Client GUI as a stand-alone application,
                run the following command:
                </p>
-               <p><code>$JAVA_HOME/bin/java -cp 
/path/to/log4j-api-2.0.jar:/path/to/log4j-core-2.0.jar:/path/to/log4j-jmx-gui-2.0.jar
 org.apache.logging.log4j.jmx.gui.ClientGUI &lt;options&gt;</code></p>
+               <p><code>$JAVA_HOME/bin/java -cp 
/path/to/log4j-api-2.0.jar:/path/to/log4j-core-2.0.jar:/path/to/log4j-jmx-gui-2.0.jar
 org.apache.logging.log4j.jmx.gui.ClientGui &lt;options&gt;</code></p>
                <p>or on Windows:</p>
-               <p><code>%JAVA_HOME%\bin\java -cp 
\path\to\log4j-api-2.0.jar;\path\to\log4j-core-2.0.jar;\path\to\log4j-jmx-gui-2.0.jar
 org.apache.logging.log4j.jmx.gui.ClientGUI &lt;options&gt;</code></p>
+               <p><code>%JAVA_HOME%\bin\java -cp 
\path\to\log4j-api-2.0.jar;\path\to\log4j-core-2.0.jar;\path\to\log4j-jmx-gui-2.0.jar
 org.apache.logging.log4j.jmx.gui.ClientGui &lt;options&gt;</code></p>
                <p>Where <code>options</code> are one of the following:</p>
                <ul>
                <li><code>&lt;host&gt;:&lt;port&gt;</code></li>
@@ -155,9 +155,9 @@ com.sun.management.jmxremote.ssl=false</
         Monitoring and Management</a> provides details on how to configure
         JMX more securely with password authentication and SSL.)</b></p>
                <p>Then you can run the client with this command:</p>
-               <p><code>$JAVA_HOME/bin/java -cp 
/path/to/log4j-core-2.0.jar:/path/to/log4j-jmx-gui-2.0.jar 
org.apache.logging.log4j.jmx.gui.ClientGUI localhost:33445</code></p>
+               <p><code>$JAVA_HOME/bin/java -cp 
/path/to/log4j-core-2.0.jar:/path/to/log4j-jmx-gui-2.0.jar 
org.apache.logging.log4j.jmx.gui.ClientGui localhost:33445</code></p>
                <p>or on Windows:</p>
-               <p><code>%JAVA_HOME%\bin\java -cp 
\path\to\log4j-core-2.0.jar;\path\to\log4j-jmx-gui-2.0.jar 
org.apache.logging.log4j.jmx.gui.ClientGUI localhost:33445</code></p>
+               <p><code>%JAVA_HOME%\bin\java -cp 
\path\to\log4j-core-2.0.jar;\path\to\log4j-jmx-gui-2.0.jar 
org.apache.logging.log4j.jmx.gui.ClientGui localhost:33445</code></p>
                <p>The screenshot below shows the StatusLogger panel of the 
client
                GUI when running as a stand-alone application.</p>
         <p><img src="../images/jmx-standalone-statuslogger.png" alt="JMX GUI 
screenshot of StatusLogger display" /></p>