[jboss-cvs] JBossAS SVN: r95008 - projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/mdb.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Fri Oct 16 03:34:13 EDT 2009


Author: laubai
Date: 2009-10-16 03:34:13 -0400 (Fri, 16 Oct 2009)
New Revision: 95008

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

Modified: projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/mdb/README.html
===================================================================
--- projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/mdb/README.html	2009-10-16 07:18:03 UTC (rev 95007)
+++ projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/mdb/README.html	2009-10-16 07:34:13 UTC (rev 95008)
@@ -8,57 +8,34 @@
 <body>
 <br>
 <h1>JBoss Messaging Message Driven Bean Example</h1>
-$Revision: 2751 $
+$ Revision: 2751 $
 <h2>Overview</h2>
-<br>
-This example deploys a simple Message Driven Bean that processes
-messages sent to a test queue.&nbsp; Once it receives a message and
-"processes" it, the MDB sends an acknowledgment message to a&nbsp;
-temporary destination created by the sender for this purpose. The
-example is considered&nbsp; successful if the sender receives the
-acknowledgment message.<br>
-<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.&nbsp; 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.&nbsp;<br>
-<br>
+<p>
+  This example deploys a simple Message Driven Bean (MDB) that processes messages sent to a test queue. Once the queue receives and processes a message, the MDB sends an acknowledgement to a temporary destination created by the sender. The example is considered successful if the sender receives the acknowledgement.
+</p>
+<p>
+  This example requires access to a running instance of JBoss Messaging, installed and started according to the <emphasis>Installation</emphasis> section of the release documentation. The example automatically deploys 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> and correct the path to the archive.
+</p>
+
 <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><br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><span style="font-family: monospace;">cd
-...\examples\mdb</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\mdb</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">
@@ -118,28 +95,12 @@
     </tr>
   </tbody>
 </table>
-<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 style="font-family: courier new,courier,monospace;">
-<hr
- style="width: 100%; height: 2px; font-family: courier new,courier,monospace;"><br>
-<br>
-<br>
-<br>
-<br>
-<br>
-<br>
+<h2>Troublesooting</h2>
+<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