Author: mcaspers Date: 2011-03-16 23:06:43 -0400 (Wed, 16 Mar 2011) New Revision: 29850 Modified: trunk/jmx/docs/reference/en-US/images/eclipse-jmx_0.2.png trunk/jmx/docs/reference/en-US/images/invokemethod.png trunk/jmx/docs/reference/en-US/images/mbeans.png trunk/jmx/docs/reference/en-US/images/new_connection_icon.png trunk/jmx/docs/reference/en-US/introduction.xml trunk/jmx/docs/reference/en-US/tasks.xml Log: "Fixed spelling errors" Modified: trunk/jmx/docs/reference/en-US/images/eclipse-jmx_0.2.png =================================================================== (Binary files differ) Modified: trunk/jmx/docs/reference/en-US/images/invokemethod.png =================================================================== (Binary files differ) Modified: trunk/jmx/docs/reference/en-US/images/mbeans.png =================================================================== (Binary files differ) Modified: trunk/jmx/docs/reference/en-US/images/new_connection_icon.png =================================================================== (Binary files differ) Modified: trunk/jmx/docs/reference/en-US/introduction.xml =================================================================== --- trunk/jmx/docs/reference/en-US/introduction.xml 2011-03-17 03:03:24 UTC (rev 29849) +++ trunk/jmx/docs/reference/en-US/introduction.xml 2011-03-17 03:06:43 UTC (rev 29850) @@ -129,7 +129,7 @@ <para>Here, we are going to explain how to install the <productname>JMX plugin</productname> into Eclipse.</para> <para> - <productname>JBoss JMX Tools</productname> is one module of the <productname>JBoss Tools</productname> project. <productname> JBoss JMX Tools</productname> has no dependency on any other part of <productname>JBoss Tools</productname>, and can be downloaded as a standalone Eclipse plugin. Even though the <productname>JMX Tools</productname> have no dependencies on other plugins, such as <productname>AS Tools</productname>, <productname>JBoss JMX Tools</productname> do depend on the JMX Tooling and even extend it. + <productname>JBoss JMX Tools</productname> is one module of the <productname>JBoss Tools</productname> project. <productname> JBoss JMX Tools</productname> has no dependency on any other part of <productname>JBoss Tools</productname>, and can be downloaded as a stand alone Eclipse plugin. Even though the <productname>JMX Tools</productname> have no dependencies on other plugins, such as <productname>AS Tools</productname>, <productname>JBoss JMX Tools</productname> do depend on the JMX Tooling and even extend it. </para> <para> Modified: trunk/jmx/docs/reference/en-US/tasks.xml =================================================================== --- trunk/jmx/docs/reference/en-US/tasks.xml 2011-03-17 03:03:24 UTC (rev 29849) +++ trunk/jmx/docs/reference/en-US/tasks.xml 2011-03-17 03:06:43 UTC (rev 29850) @@ -60,7 +60,7 @@ </listitem> <listitem> - <para>Start the <code>Main</code> application, specifying the properties that expose Main for remote management:</para> + <para>Start the <code>Main</code> application, specifying the properties that expose <code>Main</code> for remote management:</para> <programlisting role="XML"><![CDATA[ java -Dcom.sun.management.jmxremote.port=9999 \ @@ -85,7 +85,7 @@ <listitem> <para> - In the <guilabel>Create JMX Connection</guilabel> dialog, click the <guibutton>Next</guibutton> button and then click the <property>Advanced</property> tab. + In the <guilabel>Create JMX Connection</guilabel> dialog, click the <guibutton>Next</guibutton> button and then click the <guilabel>Advanced</guilabel> tab. </para> </listitem> @@ -124,7 +124,7 @@ <para> You will get the "Operation invoked successfully" message. </para> <figure> - <title>Ivoking Method via JMX</title> + <title>Invoking Method via JMX</title> <mediaobject> <imageobject> <imagedata fileref="images/invokemethod.png"/> @@ -135,8 +135,15 @@ <listitem> <para> - The final step is to make sure the application worked as expected. Open the terminal where you launched the application in step 3. Now you see the "hello, world" message on the screen. + The final step is to make sure the application worked as expected. Open the terminal where you launched the application in step 3. You should see output similar to the following: </para> + + <screen>[matthew@localhost jmx_examples]$ java -Dcom.sun.management.jmxremote.port=9999 \ +> -Dcom.sun.management.jmxremote.authenticate=false \ +> -Dcom.sun.management.jmxremote.ssl=false \ +> com.example.Main +Waiting for incoming requests... +hello, world</screen> </listitem> </orderedlist>