[jboss-cvs] JBossAS SVN: r95011 - projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/mdb-failure.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Fri Oct 16 03:53:45 EDT 2009
Author: laubai
Date: 2009-10-16 03:53:44 -0400 (Fri, 16 Oct 2009)
New Revision: 95011
Modified:
projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/mdb-failure/README.html
Log:
Corrected mdb-failure readme.
Modified: projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/mdb-failure/README.html
===================================================================
--- projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/mdb-failure/README.html 2009-10-16 07:51:11 UTC (rev 95010)
+++ projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/mdb-failure/README.html 2009-10-16 07:53:44 UTC (rev 95011)
@@ -8,67 +8,40 @@
<body>
<br>
<h1>Message Driven Bean Behavior on Failure Example</h1>
-$Revision: 1459 $
+$ Revision: 1459 $
<h2>Overview</h2>
-<br>
-This example deploys a simple Message Driven Bean that processes
-messages sent to a test queue. The Message Driven Bean is coded in such
-a way that upon the first arrival of a message, it throws a
-RuntimeException, simulating a runtime processing failure. <br>
-<br>
-The expected behavior of the MDB Container is to try to redeliver the
-message, which is what it hopefully does. Since the example framework
-took the precaution to insure that there is only one single type of MDB
-container listening on the example queue, the messages will be
-redelivered to an MDB of the same type. Upon the second arrival, the
-MDB
-instance will "let the message pass", will correctly "process" it and
-forward the result to temporary queue created by the sender for exactly
-this purpose. The
-example is considered successful if the sender receives the
-acknowledgment message. The successful example proves that message
-redelivery on failure works.<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. 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>
+<p>
+ This example deploys a simple Message Driven Bean (MDB) that processes messages that are sent to a test queue. The MDB is coded to throw a RuntimeException the first time a message arrives, simulating a runtime processing failure.
+</p>
+<p>
+ The expected behavior of the MDB container is to attempt redelivery of the message. Since the example framework ensures that there is only one type of MDB container listening on the example queue, the messages will be redelivered to a MDB on the same type. When the message arrives for the second time, the MDB instance lets the message pass, processes it correctly, and forwards it to a temporary queue created by the sender.
+</p>
+<p>
+ The example is considered successful if the sender receives the acknowledgement, so success relies upon the message being redelivered after the initial delivery failure.
+</p>
+<p>
+ This example requires access to a running instance of JBoss Messaging installed and started according to the <emphasis>Installation</emphasis> section in the release documentation. The example automatically deploys its own queue unless a queue of 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 with the release bundle. If you run this example from an unzipped installation bundle, the example's run script is already configured to locate the archive. Otherwise, you must modify the example's <span style="font-family: monospace;">build.xml</span> to match your archive's classpath.
+</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:\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-failure</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-failure</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">
@@ -96,7 +69,8 @@
compile:
[javac] Compiling 5 source files to C:\java\messaging\docs\examples\common\output\classes
[javac] Compiling 2 source files to C:\java\messaging\docs\examples\mdb-failure\output\classes
- [javac] Note: C:\java\messaging\docs\examples\mdb-failure\src\org\jboss\example\jms\mdbfailure\MDBFailureExample.java uses unchecked or unsafe operations.
+ [javac] Note: C:\java\messaging\docs\examples\mdb-failure
+ \src\org\jboss\example\jms\mdbfailure\MDBFailureExample.java uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
jar:
@@ -134,15 +108,6 @@
</tr>
</tbody>
</table>
-<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>
+
</body>
</html>
More information about the jboss-cvs-commits
mailing list