[jboss-cvs] JBossAS SVN: r95073 - projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/bridge.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Sun Oct 18 19:36:53 EDT 2009
Author: laubai
Date: 2009-10-18 19:36:53 -0400 (Sun, 18 Oct 2009)
New Revision: 95073
Modified:
projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/bridge/README.html
Log:
Corrected bridge readme.html.
Modified: projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/bridge/README.html
===================================================================
--- projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/bridge/README.html 2009-10-18 11:37:53 UTC (rev 95072)
+++ projects/docs/enterprise/5.0/Examples/jboss-messaging-examples/bridge/README.html 2009-10-18 23:36:53 UTC (rev 95073)
@@ -8,49 +8,39 @@
<body>
<br>
<h1>JBoss Messaging Bridge Example</h1>
-$Revision: 2310 $
+$ Revision: 2310 $
<h2>Overview</h2>
-<br>
-This example deploys a message bridge in JBoss AS, which is configured to
-move messages from one destination to another.
-<br>
-The example then sends some message to the source destination, then consumes the
-same messages from the target destionation, demonstrating that the bridge has
-successfully moved the messages from the source to the target.
-<br>
-The example is somewhat artificial in that normally a bridge would be used to move messages
-from source and target destinations on different servers, but it serves to illustrate how to
-use a bridge
-<br>
-This example relies on having access to a running JBoss Messaging
-instance.
-The JBoss Messaging instance must be installed according to the userguide.<br>
-<span style="font-style: italic;"></span>
+<p>
+ This example deploys a message bridge configured to move messages from one destination to another into JBoss Application Server.
+</p>
+<p>
+ The example sends some message to the source destination, then consumes the same message from the target destination. This demonstrates that the bridge has successfully moved the message from the source to the target.
+</p>
+<p>
+ A bridge usually moves messages between source and target destinations on different servers, so this example is somewhat contrived, but it serves to illustrate how to use a bridge.
+</p>
+<p>
+ This example requires access to a running instance of JBoss Messaging installed according to the release documentation.
+</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><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\bridge</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 in <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\messaging\deploy</span>, your JBOSS_HOME 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\bridge</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">
@@ -60,56 +50,76 @@
<div style="margin-left: 40px;"><br>
</div>
-[tim at Vigor14 bridge]$ ant<br>
-Buildfile: build.xml<br>
-<br>
-identify:<br>
- [echo] ###########################################################################<br>
- [echo] # Running the BRIDGE example #<br>
- [echo] ###########################################################################
- [echo] The queue: ${example.queue.name}<br>
- [echo] The client jar: ../../../output/lib/jboss-messaging-client.jar<br>
-<br>
-sanity-check:<br>
-<br>
-init:<br>
- [mkdir] Created dir: /home/tim/dev/jboss-messaging/trunk/docs/examples/bridge/output/classes<br>
- [mkdir] Created dir: /home/tim/dev/jboss-messaging/trunk/docs/examples/common/output/classes<br>
-<br>
-compile:<br>
- [javac] Compiling 5 source files to /home/tim/dev/jboss-messaging/trunk/docs/examples/common/output/classes<br>
- [javac] Compiling 1 source file to /home/tim/dev/jboss-messaging/trunk/docs/examples/bridge/output/classes>br>
-<br>
-deploy:<br>
- [copy] Copying 1 file to /home/tim/dev/jboss-4.2.0.GA/server/messaging/deploy<br>
-<br>sleep:<br> [echo] Sleeping for 5 seconds ...<br><br>run:<br> [java] Queue JBossQueue[A] exists<br> [java] Queue JBossQueue[B] exists<br> [java] The message was successfully sent to the A queue<br> [java] The message was successfully sent to the A queue<br> [java] The message was successfully sent to the A queue<br> [java] The message was successfully sent to the A queue<br> [java] The message was successfully sent to the A queue<br> [java] The message was successfully sent to the A queue<br> [java] The message was successfully sent to the A queue<br> [java] The message was successfully sent to the A queue<br> [java] The message was successfully sent to the A queue<br> [java] The message was successfully sent to the A queue<br> [java] The message was received successfully from the B queue<br> [java] The message was received successfully from the B queue<br> [java] The message was received successfully from t!
he B queue<br> [java] The message was received successfully from the B queue<br> [java] The message was received successfully from the B queue<br> [java] The message was received successfully from the B queue<br> [java] The message was received successfully from the B queue<br> [java] The message was received successfully from the B queue<br> [java] The message was received successfully from the B queue<br> [java] The message was received successfully from the B queue<br> [java] The example connected to JBoss Messaging version 1.3.0.GA (1.3)<br><br> [java] #####################<br> [java] ### SUCCESS! ###<br> [java] #####################<br><br>undeploy:<br> [delete] Deleting: /home/tim/dev/jboss-4.2.0.GA/server/messaging/deploy/test-bridge-service.xml<br><br>BUILD SUCCESSFUL<br>Total time: 9 seconds<br><br>
+<pre>
+[tim at Vigor14 bridge]$ ant
+Buildfile: build.xml
+
+identify:
+[echo] ###########################################################################
+[echo] # Running the BRIDGE example #
+[echo] ###########################################################################
+[echo] The queue: ${example.queue.name}
+[echo] The client jar: ../../../output/lib/jboss-messaging-client.jar
+
+sanity-check:
+
+init:
+[mkdir] Created dir: /home/tim/dev/jboss-messaging/trunk/docs/examples/bridge/output/classes
+[mkdir] Created dir: /home/tim/dev/jboss-messaging/trunk/docs/examples/common/output/classes
+
+compile:
+[javac] Compiling 5 source files to /home/tim/dev/jboss-messaging/trunk/docs/examples/common/output/classes
+[javac] Compiling 1 source file to /home/tim/dev/jboss-messaging/trunk/docs/examples/bridge/output/classes
+deploy:
+[copy] Copying 1 file to /home/tim/dev/jboss-4.2.0.GA/server/messaging/deploy
+
+sleep:
+[echo] Sleeping for 5 seconds ...
+
+run:
+[java] Queue JBossQueue[A] exists
+[java] Queue JBossQueue[B] exists
+[java] The message was successfully sent to the A queue
+[java] The message was successfully sent to the A queue
+[java] The message was successfully sent to the A queue
+[java] The message was successfully sent to the A queue
+[java] The message was successfully sent to the A queue
+[java] The message was successfully sent to the A queue
+[java] The message was successfully sent to the A queue
+[java] The message was successfully sent to the A queue
+[java] The message was successfully sent to the A queue
+[java] The message was successfully sent to the A queue
+[java] The message was received successfully from the B queue
+[java] The message was received successfully from the B queue
+[java] The message was received successfully from the B queue
+[java] The message was received successfully from the B queue
+[java] The message was received successfully from the B queue
+[java] The message was received successfully from the B queue
+[java] The message was received successfully from the B queue
+[java] The message was received successfully from the B queue
+[java] The message was received successfully from the B queue
+[java] The message was received successfully from the B queue
+[java] The example connected to JBoss Messaging version 1.3.0.GA (1.3)
+
+[java] #####################
+[java] ### SUCCESS! ###
+[java] #####################
+
+undeploy:
+[delete] Deleting: /home/tim/dev/jboss-4.2.0.GA/server/messaging/deploy/test-bridge-service.xml
+
+BUILD SUCCESSFUL
+Total time: 9 seconds
+</pre>
</td>
</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. 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>
+
+<h2>Troubleshooting</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 Application Server 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