[jboss-cvs] JBossAS SVN: r95014 - projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/ordering-group.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Fri Oct 16 04:21:42 EDT 2009 

Author: laubai
Date: 2009-10-16 04:21:42 -0400 (Fri, 16 Oct 2009)
New Revision: 95014

Modified:
   projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/ordering-group/README.html
Log:
Corrected ordering-group readme.

Modified: projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/ordering-group/README.html
===================================================================
--- projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/ordering-group/README.html	2009-10-16 08:20:06 UTC (rev 95013)
+++ projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/ordering-group/README.html	2009-10-16 08:21:42 UTC (rev 95014)
@@ -9,64 +9,42 @@
 <br>
 <h1>JBoss Messaging Ordering Group Example</h1>
 
-$Revision: 2750 $
+$ Revision: 2750 $
 
 <h2>Overview</h2>
 
-<br>
+<p>
+  This example creates a Java Message Service connection to a JBoss Messaging instance. Through this instance, it creates a session and two message producers: a normal producer called <emphasis>producer1</emphasis>, and <emphasis>producer</emphasis>, which is used to produce ordering group messages.
+</p>
+<p>
+  These producers send five messages in total to <emphasis>queue/testQueue</emphasis>. The example starts two consumer threads to receive these messages, and checks the results once the messages are all received.
+</p>
+<p>
+  This example illustrates that ordering group messages will be delivered in the exact order in which they are sent, even if the messages have different priorities and are consumed by multiple consumers simultaneously.
+</p>
+<p>
+  This example requires access to a running JBoss Messaging instance that has been installed and started according to the <emphasis>Installation</emphasis> section in the release documentation. The example will automatically deploy its own queue unless a queue with the same name is already deployed.
+</p>
+<p>
+  Finally, this example requires access to the <span style="font-family: monospace;">jboss-messaging-client.jar</span> archive included in the release bundle. If you run this example from an unzipped installation bundle, the example run script is already configured to locate the archive. Otherwise, you must modify the example's <span style="font-family: monospace;">build.xml</span> as required.
+</p>
 
-This example creates a JMS Connection to a JBoss Messaging instance and uses it to create a
-session and two message producers, one normal producer called 'producer1', the other producer
-called 'producer' is used to produce ordering group messages. Then both producers send 5 messages
-(producer1 sending 2 and producer 3) to "queue/testQueue". The example then starts two consumer 
-threads to receive these messages. Once the messages are all received, it check the results.<br>
-<br>
-This example illustrates that ordering group messages will be delivered exactly in the same
-order as they are sent, even if the messages has different priorities and are consumed by
-multiple consumers at the same time.
-<br>
-This example relies on having access to a running JBoss Messaging
-instance.
-The JBoss Messaging instance must be installed and started according to
-the
-"Installation" paragraph from the release documentation. However, the
-example will automatically deploy its own queue, unless a queue with
-the same name is already deployed. <br>
-<br>
-This example also relies on having access to <span
- style="font-family: monospace;">jboss-messaging-client.jar</span>
-archive that comes with the release bundle. If you run this example
-from an unzipped installation bundle, the example run script is
-correctly configured to find the client jar. Otherwise, you must modify
-example's <span style="font-family: monospace;">build.xml</span>
-accordingly.<br>
-<br>
-<span style="font-style: italic;"></span>
 <h2>Running the example</h2>
-1. Set up the JBOSS_HOME environment variable to point to the JBoss
-instance you deployed JBoss Messaging into. For example, if you
-deployed JBoss Messaging in <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\messaging\deploy,</span>
-then your JBOSS_HOME value should be <span
- style="font-family: monospace;">C:\</span><span
- style="font-family: monospace;">jboss-4.2.0.GA</span><br>
-<span style="font-family: monospace;"></span><span
- style="font-family: monospace;"></span><br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><span style="font-family: monospace;">cd
-...\examples\ordering-group</span><br>
-</div>
-<br>
-3. Run the example:<br>
-<br>
-<div style="margin-left: 40px;"><span style="font-family: monospace;">ant</span>
-<br>
-<br>
-<br>
-</div>
-The output of a successful run should be similar to:<br>
-<div style="margin-left: 40px;"><br>
-</div>
+<ol>
+  <li>
+    <p>Set the JBOSS_HOME environment variable to point to the JBoss Application Server instance into which you deployed JBoss Messaging. If you deployed JBoss Messaging into <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\messaging\deploy</span>, your JBOSS_HOME value should be <span style="font-family: monospace;">C:\jboss-4.2.0.GA.</span>.</p>
+  </li>
+  <li>
+    <p>Go to the example's home directory:</p>
+    <div style="margin-left: 40px;"><span style="font-family: monospace;">cd ...\examples\ordering-group</span></div>
+  </li>
+  <li>
+    <p>Run the example:</p>
+    <div style="margin-left: 40px;"><span style="font-family: monospace;">ant</span></div>
+  </li>
+</ol>
+
+<p>A successful run should have output similar to the following:</p>
 <table
  style="width: 90%; text-align: left; font-family: monospace; background-color: rgb(204, 204, 204); margin-left: 40px;"
  border="1" cellpadding="2" cellspacing="2">
@@ -86,10 +64,12 @@
 sanity-check:
 
 init:
-    [mkdir] Created dir: /home/howard/apps/jboss-messaging-1.4.0.SP3-CP08/examples/ordering-group/output/classes
+    [mkdir] Created dir: /home/howard/apps/jboss-messaging-1.4.0.SP3-CP08/examples/
+       ordering-group/output/classes
 
 compile:
-    [javac] Compiling 2 source files to /home/howard/apps/jboss-messaging-1.4.0.SP3-CP08/examples/ordering-group/output/classes
+    [javac] Compiling 2 source files to /home/howard/apps/jboss-messaging-1.4.0.SP3-CP08/
+       examples/ordering-group/output/classes
 
 run:
      [java] Queue /queue/testQueue exists
@@ -114,29 +94,12 @@
     </tr>
   </tbody>
 </table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-<br>
+
 <h2>Troublesooting</h2>
-<h3>1. I get <span style="font-family: monospace;">"javax.jms.JMSSecurityException:
-User null is NOT authenticated" <br>
-</span></h3>
-You probably didn't install JBoss Messaging correctly. A fresh JBoss
-Messaging installation requires changes in the security configuration
-of a <span style="font-family: monospace;">default </span>JBoss
-instance, specifically a properly configured "<small><span
- style="font-family: courier new,courier,monospace;">messaging</span></small>"
-security domain.&nbsp; Follow the instructions from the "Installation"
-paragraph of the release documentation. <br>
-<br>
-<br>
-<hr style="width: 100%; height: 2px;"><br>
-<br>
-<br>
-<br>
-<br>
-<br>
-<br>
+<h3>1. I get a <span style="font-family: monospace;">"javax.jms.JMSSecurityException:
+User null is NOT authenticated"</span> exception</h3>
+<p>
+  JBoss Messaging may not have been installed correctly. A fresh installation of JBoss Messaging requires changes to the security configuration of a <span style="font-family: monospace;">default</span> JBoss instance. In particular, it requires a properly configured <span style="font-family: courier new,courier,monospace;">messaging</span> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
 </body>
 </html>

More information about the jboss-cvs-commits mailing list