[jboss-cvs] JBoss Messaging SVN: r7872 - in tags/JBossMessaging_1_4_6_GA/docs/examples: distributed-queue and 14 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Oct 27 21:52:11 EDT 2009
Author: laubai
Date: 2009-10-27 21:52:10 -0400 (Tue, 27 Oct 2009)
New Revision: 7872
Modified:
tags/JBossMessaging_1_4_6_GA/docs/examples/bridge/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/distributed-queue/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/distributed-topic/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/ejb3mdb/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/http/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/mdb-failure/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/mdb/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/ordering-group/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/queue-failover/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/queue/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/secure-socket/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/servlet/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/stateless-clustered/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/stateless/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/topic/README.html
tags/JBossMessaging_1_4_6_GA/docs/examples/web-service/README.html
Log:
Edited readme files for all examples.
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/bridge/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/bridge/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/bridge/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -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>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/distributed-queue/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/distributed-queue/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/distributed-queue/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -8,128 +8,101 @@
<body>
<br>
<h1>JBoss Messaging Distributed Queue Example</h1>
-$Revision: 1017 $
+$ Revision: 1017 $
<h2>Overview</h2>
-<br>
-This example demonstrates how to write JMS code that connects to a
-JBoss Messaging cluster and sends messages to a distributed queue.
-The example creates two connections to two distinct cluster nodes
-on which we have previously deployed a distributed queue.
-The example sends and receives messages using both connections.
-<br>
-<br>
-This example relies on having access to a running JBoss Messaging
-cluster with at least two nodes. The JBoss Messaging cluster must be
-installed and started according to the user guide.
-<<br><br>
-For JBoss5, you should copy all as messaging-node0, configure mysql as a database, make it clustered, and copy it as messaging-node1. Start each instance as:
-<br><br>
-./run.sh -c messaging-node0 -Djboss.service.binding.set=ports-01
-<br><br>
-<br>
-and in another window
-<br><br>
-./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1
-<br><br>
-<span style="font-style: italic;"></span><br>
+<p>
+ This example shows you how to write Java Message Service (JMS) code that connects to a JBoss Messaging cluster and sends messages to a distributed queue. The example creates two connections to two distinct cluster nodes on which we have previously deployed a distributed queue. The example sends and receives using both connections.
+</p>
+<p>
+ This example requires access to a running JBoss Messaging cluster with a minimum of two nodes that has been installed and started according to the release documentation.
+</p>
+<p>
+ The root directory of your JBoss Enterprise Application Platform installation contains a <span style="font-family: monospace;">server/all/</span> directory.
+</p>
+<ol>
+ <li>
+ <p>Copy the <span style="font-family: monospace;">all</span> directory as <span style="font-family: monospace;">messaging-node0</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r all messaging-node0</span></div>
+ </li>
+ <li>
+ <p>In your new <span style="font-family: monospace;">messaging-node0</span> directory, modify <span style="font-family: monospace;">configure</span> to use a MySQL data source, and the messaging configuration files to make JBoss Messaging clustered.</p>
+ </li>
+ <li>
+ <p>Copy <span style="font-family: monospace;">messaging-node0</span> to another directory as <span style="font-family: monospace;">messaging-node1</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r messaging-node0 messaging-node1</span></div>
+ </li>
+</ol>
+<p>
+ Start the first instance:
+</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node0 -Djboss.service.binding.set=ports-01</span></div>
+<p>
+ In a separate window, start the second instance:
+</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1</span></div>
+
<h2>Running the example</h2>
-<span style="font-family: monospace;"></span><span
- style="font-family: monospace;"></span><br>
-1. Make sure that a JBoss Messaging cluster with at least two nodes is
-up and running.<br>
-<br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><span style="font-family: monospace;">cd
-...\examples\distributed-queue</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>Ensure that a JBoss Messaging cluster with a minimum of two nodes is running.</p>
+ </li>
+ <li>
+ <p>Go to the example's home directory:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cd ...\examples\distributed-queue</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">
<tbody>
<tr>
- <td style="vertical-align: top;">
- <div style="margin-left: 40px;"><br>
- </div>
-$ ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-###########################################################################<br>
- [echo]
-#
-Running the DISTRIBUTED QUEUE
-example
-#<br>
- [echo]
-###########################################################################<br>
- [echo] The
-topic: testDistributedQueue<br>
- [echo] The client jar:
-../../../output/lib/jboss-messaging-client.jar<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- [mkdir] Created dir:
-C:\work\src\svn\messaging\docs\examples\distributed-queue\output<br>
- [mkdir] Created dir:
-C:\work\src\svn\messaging\docs\examples\common\output<br>
- <br>
-compile:<br>
- [javac] Compiling 2 source files to
-C:\work\src\svn\messaging\docs\examples\common\output<br>
- [javac] Compiling 2 source files to
-C:\work\src\svn\messaging\docs\examples\distributed-queue\output<br>
- <br>
-run:<br>
- [java] Distributed queue
-/queue/testDistributedQueue exists<br>
- [java] The message was successfully sent
-to the distributed queue<br>
- [java] MessageListener0 received message:
-Hello!<br>
- [java] MessageListener1 received message:
-Another Hello!<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>
-BUILD SUCCESSFUL<br>
-Total time: 4 seconds<br>
- <br>
- <br>
+ <td>
+<pre>
+$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] ###########################################################################
+ [echo] # Running the DISTRIBUTED QUEUE example #
+ [echo] ###########################################################################
+ [echo] The topic: testDistributedQueue
+ [echo] The client jar: ../../../output/lib/jboss-messaging-client.jar
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\work\src\svn\messaging\docs\examples\distributed-queue\output
+ [mkdir] Created dir: C:\work\src\svn\messaging\docs\examples\common\output
+
+compile:
+ [javac] Compiling 2 source files to C:\work\src\svn\messaging\docs\examples\common\output
+ [javac] Compiling 2 source files to C:\work\src\svn\messaging\docs\examples\distributed-queue\output
+
+run:
+ [java] Distributed queue /queue/testDistributedQueue exists
+ [java] The message was successfully sent to the distributed queue
+ [java] MessageListener0 received message: Hello!
+ [java] MessageListener1 received message: Another Hello!
+ [java] The example connected to JBoss Messaging version 1.3.0.GA (1.3)
+
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+BUILD SUCCESSFUL
+Total time: 4 seconds
+</pre>
</td>
</tr>
</tbody>
</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-<br>
-<br>
-<hr style="width: 100%; height: 2px;"><br>
-<br>
-<br>
-<br>
-<br>
-<br>
-<br>
</body>
</html>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/distributed-topic/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/distributed-topic/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/distributed-topic/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -8,131 +8,98 @@
<body>
<br>
<h1>JBoss Messaging Distributed Topic Example</h1>
-$Revision$
+$ Revision: 5409 $
<h2>Overview</h2>
-<br>
-This example demonstrates how to write JMS code that connects to a
-JBoss Messaging cluster and sends messages to a distributed topic. The
-client code creates two distinct JMS connections to two different
-cluster nodes. Each connection is then used to create a subscriber for
-the distributed topic. The example is considered
-successful
-if both subscribers receive a message sent to the topic.<br>
-<br>
-This example relies on having access to a running JBoss Messaging
-cluster with at least two nodes. The JBoss Messaging cluster must be
-installed and started according to the userguide.
-<br><br>
-<br>
-<br><br>
-For JBoss5, you should copy all as messaging-node0, configure mysql as a database, make it clustered, and copy it as messaging-node1. Start each instance as:
-<br><br>
-./run -c messaging-node0 -Djboss.service.binding.set=ports-01
-<br><br>
-<br>
-and in another window
-<br><br>
-./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1
-<br><br>
-<span style="font-style: italic;"></span><br>
+<p>This example demonstrates how to write Java Message Service code that connects to a JBoss Messaging cluster and sends messages to a distributed topic. Each connection is then used to create a subscriber for the distributed topic. The example is considered successful if both subscribers receive a message sent to the topic.</p>
+<p>This example requires access to a running JBoss Messaging cluster with a minimum of two nodes. The JBoss Messaging cluster must be installed and started according to the JBoss Messaging User Guide.</p>
+
+<p>
+ The root directory of your JBoss Enterprise Application Platform installation contains a <span style="font-family: monospace;">server/all/</span> directory.
+</p>
+<ol>
+ <li>
+ <p>Copy the <span style="font-family: monospace;">all</span> directory as <span style="font-family: monospace;">messaging-node0</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r all messaging-node0</span></div>
+ </li>
+ <li>
+ <p>In your new <span style="font-family: monospace;">messaging-node0</span> directory, modify <span style="font-family: monospace;">configure</span> to use a MySQL data source, and the messaging configuration files to make JBoss Messaging clustered.</p>
+ </li>
+ <li>
+ <p>Copy <span style="font-family: monospace;">messaging-node0</span> to another directory as <span style="font-family: monospace;">messaging-node1</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r messaging-node0 messaging-node1</span></div>
+ </li>
+</ol>
+<p>
+ Start the first instance:
+</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node0 -Djboss.service.binding.set=ports-01</span></div>
+<p>
+ In a separate window, start the second instance:
+</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1</span></div>
+
+
<h2>Running the example</h2>
-<span style="font-family: monospace;"></span><span
- style="font-family: monospace;"></span><br>
-1. Make sure that a JBoss Messaging cluster with at least two nodes is
-up and running.<br>
-<br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><span style="font-family: monospace;">cd
-...\examples\distributed-topic</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>Ensure that a JBoss Messaging cluster with a minimum of two nodes is running and available.</p>
+ </li>
+ <li>
+ <p>Go to the example's home directory:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cd ...\examples\distributed-topic</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">
<tbody>
<tr>
<td style="vertical-align: top;">
- <div style="margin-left: 40px;"><br>
- </div>
-$ ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-###########################################################################<br>
- [echo]
-#
-Running the DISTRIBUTED TOPIC
-example
-#<br>
- [echo]
-###########################################################################<br>
- [echo] The
-topic: testDistributedTopic<br>
- [echo] The client jar:
-../../../output/lib/jboss-messaging-client.jar<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- [mkdir] Created dir:
-C:\work\src\svn\messaging\docs\examples\distributed-topic\output<br>
- [mkdir] Created dir:
-C:\work\src\svn\messaging\docs\examples\common\output<br>
- <br>
-compile:<br>
- [javac] Compiling 2 source files to
-C:\work\src\svn\messaging\docs\examples\common\output<br>
- [javac] Compiling 2 source files to
-C:\work\src\svn\messaging\docs\examples\distributed-topic\output<br>
- <br>
-run:<br>
- [java] Distributed topic
-/topic/testDistributedTopic exists<br>
- [java] The message was successfully published
-on the distributed topic<br>
- [java] MessageListener 1 received message:
-Hello!<br>
- [java] MessageListener 2 received message:
-Hello!<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>
-BUILD SUCCESSFUL<br>
-Total time: 4 seconds<br>
- <br>
- <br>
+ <pre>
+$ ant
+Buildfile: build.xml
+
+identify:
+[echo] ###########################################################################
+[echo] # Running the DISTRIBUTED TOPIC example #
+[echo] ###########################################################################
+[echo] The topic: testDistributedTopic
+[echo] The client jar: ../../../output/lib/jboss-messaging-client.jar
+
+sanity-check:
+
+init:
+[mkdir] Created dir: C:\work\src\svn\messaging\docs\examples\distributed-topic\output
+[mkdir] Created dir: C:\work\src\svn\messaging\docs\examples\common\output
+
+compile:
+[javac] Compiling 2 source files to C:\work\src\svn\messaging\docs\examples\common\output
+[javac] Compiling 2 source files to C:\work\src\svn\messaging\docs\examples\distributed-topic\output
+
+run:
+[java] Distributed topic /topic/testDistributedTopic exists
+[java] The message was successfully published on the distributed topic
+[java] MessageListener 1 received message: Hello!
+[java] MessageListener 2 received message: Hello!
+[java] The example connected to JBoss Messaging version 1.3.0.GA (1.3)
+
+[java] #####################
+[java] ### SUCCESS! ###
+[java] #####################
+
+BUILD SUCCESSFUL
+Total time: 4 seconds
+</pre>
</td>
</tr>
</tbody>
</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-<br>
-<br>
-<hr style="width: 100%; height: 2px;"><br>
-<br>
-<br>
-<br>
-<br>
-<br>
-<br>
</body>
</html>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/ejb3mdb/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/ejb3mdb/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/ejb3mdb/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -8,140 +8,87 @@
<body>
<br>
<h1>JBoss Messaging EJB3 Message Driven Bean Example</h1>
-$Revision$
+$ Revision: 2751 $
<h2>Overview</h2>
-<br>
-This example deploys a simple EJB3 Message Driven Bean that processes
-messages sent to a test queue. Once it receives a message and
-"processes" it, the EJB3 MDB sends an acknowledgment message to a
-temporary destination created by the sender for this purpose. The
-example is considered successful if the sender receives the
-acknowledgment message.<br>
-<br>
-<span style="font-style: italic;"></span><br>
+<p>This example deploys a simple Enterprise JavaBean 3.0 Message Driven Bean (MDB), which processes the 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. This example is considered successful if the sender receives the acknowledgement.</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\default\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;"><br>
-</span><br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><span style="font-family: monospace;">cd
-...\examples\ejb3mdb</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. For example, if you deployed JBoss Messaging in <span style="font-family: monospace;">C:\jboss-4.2.0.GA\server\default\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\ejb3mdb</span></div>
+ </li>
+ <li>
+ Run the example:
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">ant</span></div>
+ </li>
+</ol>
+<p>A successful run will 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">
<tbody>
<tr>
<td style="vertical-align: top;">
- <div style="margin-left: 40px;"><br>
- </div>
-$ ant<br>
+ $ ant<br>
Buildfile: build.xml<br>
- <br>
+<br>
identify:<br>
- [echo]
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
- [echo]
-X
-Running the EJB3 MDB
-example
-X<br>
- [echo]
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
- [echo] The queue: testQueue<br>
- <br>
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
+ [echo] X Running the EJB3 MDB example X<br>
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
+ [echo] The queue: testQueue<br>
+<br>
sanity-check:<br>
- <br>
+<br>
init:<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\ejb3mdb\output\classes\META-INF<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\ejb3mdb\output\lib\META-INF<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
- <br>
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\ejb3mdb\output\classes\META-INF<br>
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\ejb3mdb\output\lib\META-INF<br>
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
+<br>
compile:<br>
- [javac] Compiling 2 source files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
- [javac] Compiling 2 source files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\ejb3mdb\output\classes<br>
- <br>
+ [javac] Compiling 2 source files to C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
+ [javac] Compiling 2 source files to C:\work\src\cvs\jboss-head\jms\docs\examples\ejb3mdb\output\classes<br>
+<br>
jar:<br>
- [jar] Building jar:
-C:\work\src\cvs\jboss-head\jms\docs\examples\ejb3mdb\output\lib\mdb-example.ejb3<br>
- <br>
+ [jar] Building jar: C:\work\src\cvs\jboss-head\jms\docs\examples\ejb3mdb\output\lib\mdb-example.ejb3<br>
+<br>
deploy:<br>
- [copy] Copying 1 file to
-C:\work\src\jboss-4.0.3SP1-src\build\output\jboss-4.0.3SP1\server\messaging\deploy<br>
- <br>
+ [copy] Copying 1 file to C:\work\src\jboss-4.0.3SP1-src\build\output\jboss-4.0.3SP1\server\messaging\deploy<br>
+<br>
sleep:<br>
- [echo] Sleeping for 5 seconds ...<br>
- <br>
+ [echo] Sleeping for 5 seconds ...<br>
+<br>
run:<br>
- <br>
+<br>
send:<br>
- [java] Queue /queue/testQueue exists<br>
- [java] The Hello! message was successfully
-sent to the testQueue queue<br>
- [java] Received message: !olleH<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>
+ [java] Queue /queue/testQueue exists<br>
+ [java] The Hello! message was successfully sent to the testQueue queue<br>
+ [java] Received message: !olleH<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:
-C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy\mdb-example.ejb3<br>
- <br>
+ [delete] Deleting: C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy\mdb-example.ejb3<br>
+<br>
BUILD SUCCESSFUL<br>
-Total time: 10 seconds<br>
- <br>
+Total time: 10 seconds
</td>
</tr>
</tbody>
</table>
-<br>
+
+
<h2>Troubleshooting</h2>
-<br>
-<h3>2. 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 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>
+<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 JBoss Messaging installation requires changes to the security configuration of a <span style="font-family: monospace;">default</span> JBoss instance. In particular, you must configure a <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>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/http/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/http/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/http/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -6,86 +6,43 @@
<title>JBoss Messaging Example - HTTP Transport</title>
</head>
<body>
-<br>
+
<h1>JBoss Messaging HTTP Transport Example</h1>
-$Revision$
+$ Revision: 5394 $
<h2>Overview</h2>
<p>
-This example shows how to configure a ConnectionFactory to send
-messages using the HTTP protocol. The example will use
-such a ConnectionFactory to create two JMS connections: the first one
-to send a message to the queue and the second one to read the message
-from the queue. In both cases, the message will be sent over
-an HTTP connection. The example is considered successful
-if the client receives without any error the message that was
-previously sent to the queue.</p>
+ This example demonstrates how to configure a ConnectionFactory to send messages with the HTTP protocol.
+</p>
<p>
-This example needs to have 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.
+ The example uses a ConnectionFactory to create two Java Message Service connections. The first connection sends a message to the queue; the second connection reads the message from the queue. In both cases, the message will be sent via a HTTP connection. This example is considered successful if the client receives, without error, the message that was sent to the queue.
</p>
-<br>
-This example also needs to have 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>
-<br>
+<p>
+ This example requires access to a running instance of JBoss Messaging, which must be 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 with the release bundle. If you run this example from an unzipped installation bundle, the example's run script is configured with the archive's path. Otherwise, you must modify the example's <span style="font-family: monospace;">build.xml</span> to reflect the path of 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:\jboss-4.2.0.GA</span><br>
-<br>
-2. Go to the example's home directory<br>
-<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>
+ <span style="font-family: monospace;">cd ...\examples\http</span>
+ </li>
+ <li>
+ <p>Run the example:</p>
+ <span style="font-family: monospace;">ant</span>
+ </li>
+</ol>
+<p>
+ A successful run should have output similar to the following:
+</p>
+
<table
- style="width: 90%; text-align: left; font-family: monospace; margin-left: 40px; background-color: rgb(255, 255, 255);"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;"><br>
- <span style="font-family: monospace;">cd
-...\examples\http</span><br>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<span style="font-family: monospace;"></span><br>
-3. Run the example:<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<table
- style="width: 90%; text-align: left; font-family: monospace; margin-left: 40px; background-color: rgb(255, 255, 255);"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;"><br>
- <span style="font-family: monospace;">ant</span><br>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-The output of a successful run should be similar to:<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<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">
<tbody>
@@ -141,26 +98,9 @@
</div>
<br>
<h2>Troubleshooting</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>
-<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 JBoss Messaging installation 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 from the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
</body>
</html>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/mdb/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/mdb/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/mdb/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -8,57 +8,34 @@
<body>
<br>
<h1>JBoss Messaging Message Driven Bean Example</h1>
-$Revision$
+$ Revision: 2751 $
<h2>Overview</h2>
-<br>
-This example deploys a simple Message Driven Bean that processes
-messages sent to a test queue. Once it receives a message and
-"processes" it, the MDB sends an acknowledgment message to a
-temporary destination created by the sender for this purpose. The
-example is considered 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. 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 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. 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>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 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>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/mdb-failure/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/mdb-failure/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/mdb-failure/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -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>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/ordering-group/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/ordering-group/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/ordering-group/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -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. 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>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/queue/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/queue/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/queue/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -8,60 +8,33 @@
<body>
<br>
<h1>JBoss Messaging Queue Example</h1>
-$Revision$
+$ Revision: 2750 $
<h2>Overview</h2>
-<br>
-This example creates a JMS Connection to a JBoss Messaging instance
-and uses it to create a session and a message producer, which sends a
-message to the queue "queue/testQueue". Then, the example uses
-the same connection to create a consumer that that reads
-a single message from the queue. The example is considered successful
-if the message consumer receives without any error the message that was
-sent by the producer. <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>
-<span style="font-style: italic;"></span>
+<p>
+ This example creates a Java Message Service connection to a JBoss Messaging instance and uses it to create a session and a message producer, which sends a message to the <emphasis>queue/testQueue</emphasis>. The example then uses that connection to create a consumer that reads a single message from the queue. This example is considered successful if the message consumer receives, without error, the message that was sent by the producer.
+</p>
+<p>
+ This example requires access to a running JBoss Messaging instance 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> to reference the correct path.
+</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\queue</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>
-<table
+<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\queue</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">
<tbody>
@@ -104,29 +77,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. 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 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>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/queue-failover/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/queue-failover/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/queue-failover/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -6,210 +6,135 @@
<title>JBoss Messaging Example - Queue failover</title>
</head>
<body>
-<br>
<h1>JBoss Messaging Queue Failover Example</h1>
-$Revision: 1017 $
+$ Revision: 1017 $
<h2>Overview</h2>
-<br>
-This example demonstrates the transparent failover of a JMS consumer. A
-connection is made on one node of the cluster and two messages are
-sent. A consumer is created and one of the messages is consumed. The
-node the connection is connected to then fails and the connection fails
-over onto the second node. The second message is then consumed using
-the same consumer.<span style="font-weight: bold;"></span>
-<br>
-<br>
-This example relies on having access to a running JBoss Messaging
-cluster with at least two nodes. The JBoss Messaging cluster must be
-installed and started according to the userguide.
-This example also relies on having 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 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>
-<span style="font-style: italic;"></span><br>
-<br>
-<br><br>
-For JBoss5, you should copy all as messaging-node0, configure mysql as a database, make it clustered, and copy it as messaging-node1. Start each instance as:
-<br><br>
-./run -c messaging-node0 -Djboss.service.binding.set=ports-01
-<br><br>
-<br>
-and in another window
-<br><br>
-./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1
-<br><br>
+<p>
+ This example demonstrates transparent failover in a Java Message Service (JMS) consumer. The example creates a connection on one node of the cluster and sends two messages. It then creates a consumer, which consumes one of these messages.
+<p>
+<p>
+ The node to which the connection is connected then fails, and the connection fails over onto the second node. The second message is then consumed using the same consumer.
+</p>
+<p>
+ This example requires access to a running JBoss Messaging cluster with a minimum of two nodes that has been installed and started according to the JBoss Messaging User Guide.
+</p>
+<p>
+ This example also 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'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 specify the location of the archive.
+</p>
+<p>
+ The root directory of your JBoss Enterprise Application Platform installation contains a <span style="font-family: monospace;">server/all/</span> directory.
+</p>
+<ol>
+ <li>
+ <p>Copy the <span style="font-family: monospace;">all</span> directory as <span style="font-family: monospace;">messaging-node0</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r all messaging-node0</span></div>
+ </li>
+ <li>
+ <p>In your new <span style="font-family: monospace;">messaging-node0</span> directory, modify <span style="font-family: monospace;">configure</span> to use a MySQL data source, and the messaging configuration files to make JBoss Messaging clustered.</p>
+ </li>
+ <li>
+ <p>Copy <span style="font-family: monospace;">messaging-node0</span> to another directory as <span style="font-family: monospace;">messaging-node1</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r messaging-node0 messaging-node1</span></div>
+ </li>
+</ol>
+<p>
+ Start the first instance:
+</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node0 -Djboss.service.binding.set=ports-01</span></div>
+<p>
+ In a separate window, start the second instance:
+</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1</span></div>
+
+
<h2>Running the example</h2>
-<span style="font-family: monospace;"></span><span
- style="font-family: monospace;"></span><br>
-1. Make sure that a JBoss Messaging cluster with at least two nodes is
-up and running.<br>
-<br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><span style="font-family: monospace;">cd
-...\examples\queue-failover</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>Ensure that a JBoss Messaging cluster with a minimum of two nodes is running.</p>
+ </li>
+ <li>
+ <p>Go to the example's home directory:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cd ...\examples\queue-failover</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">
<tbody>
<tr>
<td style="vertical-align: top;">
- <div style="margin-left: 40px;"><br>
- </div>
-$ ant<br>
-Buildfile: build.xml<br>
- <br>
+ <pre>
+$ ant
+Buildfile: build.xml
+
identify:
- <br>
- [echo]
-###########################################################################
- <br>
- [echo]
-#
-Running the QUEUE FAILOVER example
-
- #
- <br>
- [echo]
-###########################################################################
- <br>
- [echo] The
-queue: testDistributedQueue
- <br>
- [echo] The client jar:
-../../../output/lib/jboss-messaging-client.jar
- <br>
- <br>
+ [echo] ###########################################################################
+ [echo] # Running the QUEUE FAILOVER example #
+ [echo] ###########################################################################
+ [echo] The queue: testDistributedQueue
+ [echo] The client jar: ../../../output/lib/jboss-messaging-client.jar
+
sanity-check:
- <br>
- <br>
+
init:
- <br>
- <br>
+
compile:
- <br>
- <br>
+
jar:
- <br>
- <br>
+
deploy:
- <br>
- <br>
+
sleep:
- <br>
- [echo] Sleeping for 5 seconds ...
- <br>
- <br>
+ [echo] Sleeping for 5 seconds ...
+
run:
- <br>
- [java] Distributed queue
-/queue/testDistributedQueue exists
- <br>
- [java] The messages were successfully sent to
-the distributed queue
- <br>
- [java] Received message: Hello1!
- <br>
- [java] 11:12:22,359 ERROR @Timer-0
-[SocketClientInvoker] Got marshalling exception, exiting
- <br>
- [java] java.io.IOException: Connection reset
-by peer: socket write error
- <br>
- [java] at
-java.net.SocketOutputStream.socketWrite0(Native Method)
- <br>
- [java] at
-java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
- <br>
- [java] at
-java.net.SocketOutputStream.write(SocketOutputStream.java:136)
- <br>
- [java] at
-java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
- <br>
- [java] at
-java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
- <br>
- [java] at
-java.io.DataOutputStream.flush(DataOutputStream.java:106)
- <br>
- [java] at
-org.jboss.serial.io.JBossObjectOutputStream.flush(JBossObjectOutputStream.java:248)
- <br>
- [java] at
-org.jboss.jms.server.remoting.JMSWireFormat.serialize(JMSWireFormat.java:1035)
- <br>
- [java] at
-org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:413)
- <br>
- [java] at
-org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:518)
- <br>
- [java] at
-org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:340)
- <br>
- [java] at
-org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125)
- <br>
- [java] at
-org.jboss.remoting.ConnectionValidator.checkConnection(ConnectionValidator.java:184)
- <br>
- [java] at
-org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:114)
- <br>
- [java] at
-java.util.TimerThread.mainLoop(Timer.java:512)
- <br>
- [java] at
-java.util.TimerThread.run(Timer.java:462)
- <br>
- [java] 11:12:24,406 INFO @Thread-3
-[HAAspect] HAAspect.ClusteredClientConnectionFactoryDelegate[1]
-completed client-side failover
- <br>
- [java] Received message: Hello2!
- <br>
- [java] The example connected to JBoss
-Messaging version 1.2.0.Beta1 (1.2)
- <br>
- <br>
- [java] #####################
- <br>
- [java] ###
-SUCCESS! ###
- <br>
- [java] #####################
- <br>
- <br>
+ [java] Distributed queue /queue/testDistributedQueue exists
+ [java] The messages were successfully sent to the distributed queue
+ [java] Received message: Hello1!
+ [java] 11:12:22,359 ERROR @Timer-0 [SocketClientInvoker] Got marshalling exception, exiting
+ [java] java.io.IOException: Connection reset by peer: socket write error
+ [java] at java.net.SocketOutputStream.socketWrite0(Native Method)
+ [java] at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
+ [java] at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
+ [java] at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
+ [java] at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
+ [java] at java.io.DataOutputStream.flush(DataOutputStream.java:106)
+ [java] at org.jboss.serial.io.JBossObjectOutputStream.flush(JBossObjectOutputStream.java:248)
+ [java] at org.jboss.jms.server.remoting.JMSWireFormat.serialize(JMSWireFormat.java:1035)
+ [java] at org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:413)
+ [java] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite
+ (MicroSocketClientInvoker.java:518)
+ [java] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport
+ (MicroSocketClientInvoker.java:340)
+ [java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:125)
+ [java] at org.jboss.remoting.ConnectionValidator.checkConnection(ConnectionValidator.java:184)
+ [java] at org.jboss.remoting.ConnectionValidator.run(ConnectionValidator.java:114)
+ [java] at java.util.TimerThread.mainLoop(Timer.java:512)
+ [java] at java.util.TimerThread.run(Timer.java:462)
+ [java] 11:12:24,406 INFO @Thread-3 [HAAspect] HAAspect.ClusteredClientConnectionFactoryDelegate[1]
+ completed client-side failover
+ [java] Received message: Hello2!
+ [java] The example connected to JBoss Messaging version 1.2.0.Beta1 (1.2)
+
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
undeploy:
- <br>
- [delete] Deleting:
-C:\dev\jboss-4.0.5.GA\server\messaging-node0\deploy\application-server-killer.jar
- <br>
- <br>
+ [delete] Deleting: C:\dev\jboss-4.0.5.GA\server\messaging-node0\deploy\application-server-killer.jar
+
BUILD SUCCESSFUL
- <br>
-Total time: 41 seconds
- <br>
- <br>
- <br>
- <br>
+Total time: 41 seconds
+
+</pre>
</td>
</tr>
</tbody>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/secure-socket/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/secure-socket/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/secure-socket/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -8,176 +8,95 @@
<body>
<br>
<h1>JBoss Messaging Secure Socket Connection Example</h1>
-$Revision$
+$ Revision: 2751 $
<h2>Overview</h2>
-<br>
-This example shows how to use a secure ConnectionFactory, which creates
-a SSL socket connection between client and server. The example will use
-such a ConnectionFactory to create two JMS connections: the first one
-to send a message to the queue and the second one to read the message
-from the queue. In both cases, the message will be securely sent over
-an encrypted connection. The example is considered successful
-if the client receives without any error the message that was
-previously sent to the queue.<br>
-<br>
-This example needs to have 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>
-<span style="font-style: italic;"></span></div>
-<br>
-This example also needs to have 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>
-<br>
+<p>
+ This example shows you how to use a secure ConnectionFactory, which creates a SSL socket connection between client and server. The example uses this ConnectionFactory to create two JMS connections. The first connection sends a message to the queue; the second reads the message from the queue. Both connections send and receive messages over an encrypted connection. The example is considered successful if the client receives the message without any errors.
+</p>
+<p>
+ This example requires access to a running JBoss Messaging instance that was installed and started according to the <emphasis>Installation</emphasis> section in the JBoss Messaging User Guide. The example automatically deploys its own queue unless a queue with the same name is already deployed.
+</p>
+<p>
+ This example also 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'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 specify the location of 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:\jboss-4.2.0.GA</span><br>
-<br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
+<ol>
+ <li>
+ <p>Set the JBOSS_HOME environment variable to point to the instance of JBoss Application Server 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\secure-socket</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; margin-left: 40px; background-color: rgb(255, 255, 255);"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;"><br>
- <span style="font-family: monospace;">cd
-...\examples\secure-socket</span><br>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<span style="font-family: monospace;"></span><br>
-3. Run the example:<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<table
- style="width: 90%; text-align: left; font-family: monospace; margin-left: 40px; background-color: rgb(255, 255, 255);"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;"><br>
- <span style="font-family: monospace;">ant</span><br>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-The output of a successful run should be similar to:<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<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">
<tbody>
<tr>
- <td style="vertical-align: top;"><br>
-$ ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-############################################################################<br>
- [echo]
-#
-Running the SECURE SOCKET
-example
-#<br>
- [echo]
-############################################################################<br>
- [echo] The queue: testQueue<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\secure-socket\output<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
- <br>
-compile:<br>
- [javac] Compiling 2 source files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
- [javac] Compiling 1 source file to
-C:\work\src\cvs\jboss-head\jms\docs\examples\secure-socket\output<br>
- <br>
-deploy:<br>
- [copy] Copying 1 file to
-C:\jboss-4.2.0.GA\server\messaging\deploy\jboss-messaging.sar<br>
- [copy] Copying 1 file to
-C:\jboss-4.2.0.GA\server\messaging\deploy<br>
- <br>
-sleep:<br>
- [echo] Sleeping for 10 seconds ...<br>
- <br>
-run:<br>
- [java] Queue /queue/testQueue exists<br>
- [java] The message was successfully sent to
-the testQueue queue<br>
- [java] Received message: Hello!<br>
- [java] The example connected to JBoss
-Messaging version 1.3.0.GA (1.0)<br>
- <br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 15 seconds<br>
- <br>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-<h2>Configuration details</h2>
-<br>
-The example client looks up a specially-configured connection factory (<span
- style="font-family: monospace;">"/SecureConnectionFactory"</span>)
-that is deployed by the example run script. The secure
-ConnectionFactory relies on a "secured" Remoting Connector to provide
-the SSL connection. The definition of the required services is
-specified in the <span style="font-family: monospace;">etc/messaging-secure-socket-service.xml
-</span>deployment descriptor. <br>
+ <td style="vertical-align: top;">
+<pre>
+$ ant
+Buildfile: build.xml
- <br>
+identify:
+ [echo] ############################################################################
+ [echo] # Running the SECURE SOCKET example #
+ [echo] ############################################################################
+ [echo] The queue: testQueue
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\secure-socket\output
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\common\output
+
+compile:
+ [javac] Compiling 2 source files to C:\work\src\cvs\jboss-head\jms\docs\examples\common\output
+ [javac] Compiling 1 source file to C:\work\src\cvs\jboss-head\jms\docs\examples\secure-socket\output
+
+deploy:
+ [copy] Copying 1 file to C:\jboss-4.2.0.GA\server\messaging\deploy\jboss-messaging.sar
+ [copy] Copying 1 file to C:\jboss-4.2.0.GA\server\messaging\deploy
+
+sleep:
+ [echo] Sleeping for 10 seconds ...
+
+run:
+ [java] Queue /queue/testQueue exists
+ [java] The message was successfully sent to the testQueue queue
+ [java] Received message: Hello!
+ [java] The example connected to JBoss Messaging version 1.3.0.GA (1.0)
+
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+BUILD SUCCESSFUL
+Total time: 15 seconds
+</pre>
</td>
</tr>
</tbody>
</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-The SSLSocketBuilder needs a keystore with a public/private key pair.
-The example provides one (<span style="font-family: monospace;">etc/messaging.keystore</span>)
-which is deployed with the rest of the artifacts. In case you need to
-create your own keystore, this is how you do it:<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
+
+<h2>Configuration details</h2>
+<p>
+ The example client looks up <span style="font-family: monospace;">/SecureConnectionFactory</span>, a specially-configured connection factory deployed by the example's run script. The SecureConnectionFactory requires a secured Remoting Connector to provide the SSL connection. The required services are specified in the <span style="font-family: monospace;">etc/messaging-secure-socket-service.xml</span> deployment descriptor.
+</p>
+<p>
+ The SSLSocketBuilder requires a keystore with a public/private key pair. The example provides <span style="font-family: monospace;">etc/messaging.keystore</span>, which is deployed alongside the rest of the artifacts. However, you can create your own keystore by running the following command:
+</p>
<table
style="width: 90%; text-align: left; font-family: monospace; margin-left: 40px; background-color: rgb(255, 255, 255);"
border="1" cellpadding="2" cellspacing="2">
@@ -190,21 +109,10 @@
</tr>
</tbody>
</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-<p>By default, the client will try to contact a Certificate Authority
-to
-insure the authenticity of the public key it uses to encrypt the
-communication. However, the example's certificate is self-signed, so no
-Certificate Authority will
-recognize it. In order to get the SSL client to trust it and the
-example to complete successfully, we use a client truststore (<span
- style="font-family: monospace;">/etc/messaging.truststore</span>). In
-case you need to create your own truststore, this is how you do it:<br>
+<p>
+ By default, the client attempts to contact a Certificate Authority to ensure that the public key it uses to encrypt the communication is authentic. However, the example's certificate is self-signed, so it will not be recognized by any Certificate Authority. We use a client truststore (<span style="font-family: monospace;">/etc/messaging.truststore</span>) to make the SSL client trust our client. To create your own truststore:
</p>
-<div style="margin-left: 40px;"><br>
-</div>
+
<table
style="width: 90%; text-align: left; font-family: monospace; margin-left: 40px; background-color: rgb(255, 255, 255);"
border="1" cellpadding="2" cellspacing="2">
@@ -217,35 +125,14 @@
</tr>
</tbody>
</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<p> </p>
-<p>In order for the truststore to be recognized, the client's
-environment must contain the <tt>javax.net.ssl.trustStore</tt> and <tt>javax.net.ssl.trustStorePassword</tt>
-properties.<br>
+<p>
+ The client's environment must contain the <tt>javax.net.ssl.trustStore</tt> and <tt>javax.net.ssl.trustStorePassword</tt> properties for the truststore to be recognised.
</p>
<br>
<h2>Troubleshooting</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>
-<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" exception</span></h3>
+<p>
+ JBoss Messaging may not have been installed correctly. A fresh JBoss Messaging installation 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 <tt>messaging</tt> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
</body>
</html>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/servlet/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/servlet/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/servlet/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -6,86 +6,38 @@
<title>JBoss Messaging Example - Servlet Transport</title>
</head>
<body>
-<br>
<h1>JBoss Messaging Servlet Transport Example</h1>
-$Revision: 5394 $
+$ Revision: 5394 $
<h2>Overview</h2>
<p>
-This example shows how to configure a ConnectionFactory to send
-messages using the Servlet protocol. The example will use
-such a ConnectionFactory to create two JMS connections: the first one
-to send a message to the queue and the second one to read the message
-from the queue. In both cases, the message will be sent over
-an Servlet connection. The example is considered successful
-if the client receives without any error the message that was
-previously sent to the queue.</p>
+ This example demonstrates how to configure a ConnectionFactory to send messages with the Servlet protocol. The example uses this ConnectionFactory to create two Java Message Service connections. The first connection sends a message to the queue; the second reads the message from the queue. Both connections send and receive messages over a Servlet connection. The example is considered successful if the client receives the message without any errors.
+</p>
<p>
-This example needs to have 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.
+ This example requires access to a running JBoss Messaging instance that was installed and started according to the <emphasis>Installation</emphasis> section in the JBoss Messaging User Guide. The example automatically deploys its own queue unless a queue with the same name is already deployed.
</p>
-<br>
-This example also needs to have 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>
-<br>
+<p>
+ This example also 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'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 specify the location of 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:\jboss-4.2.0.GA</span><br>
-<br>
-2. Go to the example's home directory<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
+<ol>
+ <li>
+ <p>Set the JBOSS_HOME environment variable to point to the instance of JBoss Application Server 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\servlet</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; margin-left: 40px; background-color: rgb(255, 255, 255);"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;"><br>
- <span style="font-family: monospace;">cd
-...\examples\servlet</span><br>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<span style="font-family: monospace;"></span><br>
-3. Run the example:<br>
-<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<table
- style="width: 90%; text-align: left; font-family: monospace; margin-left: 40px; background-color: rgb(255, 255, 255);"
- border="1" cellpadding="2" cellspacing="2">
- <tbody>
- <tr>
- <td style="vertical-align: top;"><br>
- <span style="font-family: monospace;">ant</span><br>
- <br>
- </td>
- </tr>
- </tbody>
-</table>
-<div style="margin-left: 40px;"><br>
-</div>
-<br>
-The output of a successful run should be similar to:<br>
-<div style="margin-left: 40px;"><br>
-</div>
-<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">
<tbody>
@@ -144,26 +96,9 @@
</div>
<br>
<h2>Troubleshooting</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>
-<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" exception</span></h3>
+<p>
+ JBoss Messaging may not have been installed correctly. A fresh JBoss Messaging installation 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 <tt>messaging</tt> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
</body>
</html>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/stateless/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/stateless/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/stateless/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -6,153 +6,102 @@
<title>JBoss Messaging Example - Stateless Session Bean</title>
</head>
<body>
-<br>
-<h1>Sending JMS messages from a Stateless Session Bean<br>
-</h1>
-$Revision$
+<h1>Sending JMS messages from a Stateless Session Bean</h1>
+$ Revision: 2751 $
<h2>Overview</h2>
-<br>
-This example deploys a stateless session bean that then sends and
-receives messages from a queue. This is a very simple example that
-demonstrates using JBoss Messaging in a managed environment. The
-session bean sends a message to a test queue and then pulls the message
-from the queue using a different connection. The
-example is considered successful if the message is received correctly.<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 stateless session bean that sends and receives messages from a queue. This is a simple example that demonstrates using JBoss Messaging in a managed environment. The session bean sends a message to a test queue and then retrieves the message from the queue via a different connection. The example is considered successful if the message is received correctly.
+</p>
+<p>
+ This example requires access to a running JBoss Messaging instance that was installed and started according to the <emphasis>Installation</emphasis> section in the JBoss Messaging User Guide. The example automatically deploys its own queue unless a queue with the same name is already deployed.
+</p>
+<p>
+ This example also 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'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 specify the location of 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\default\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\stateless</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 instance of JBoss Application Server 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\stateless</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">
<tbody>
<tr>
- <td style="vertical-align: top;">
- <div style="margin-left: 40px;"><br>
- </div>
-$ ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
- [echo]
-X
-Running the STATELESS SESSION BEAN
-example
-X<br>
- [echo]
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
- [echo] The queue: testQueue<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\classes\META-INF<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\lib<br>
- <br>
-compile:<br>
- [javac] Compiling 4 source files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\classes<br>
- <br>
-jar:<br>
- [copy] Copying 2 files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\classes\META-INF<br>
- [jar] Building jar:
-C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\lib\stateless-example.jar<br>
- <br>
-deploy:<br>
- [copy] Copying 1 file to
-C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy<br>
- <br>
-sleep:<br>
- [echo] Sleeping for 5 seconds ...<br>
- <br>
-run:<br>
- <br>
-send-and-receive:<br>
- [java] The Hello! message was successfully
-sent to the /queue/testQueue queue<br>
- [java] Queue browse result: Hello!<br>
- [java] Received Hello!<br>
- <br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-undeploy:<br>
- [delete] Deleting:
-C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy\stateless-example.jar<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 9 seconds<br>
- <br>
- <br>
+ <td style="vertical-align: top;"><pre>
+$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ [echo] X Running the STATELESS SESSION BEAN example X
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ [echo] The queue: testQueue
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\classes
+ \META-INF
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\lib
+
+compile:
+ [javac] Compiling 4 source files to C:\work\src\cvs\jboss-head\jms\docs\examples\stateless
+ \output\classes
+
+jar:
+ [copy] Copying 2 files to C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output
+ \classes\META-INF
+ [jar] Building jar: C:\work\src\cvs\jboss-head\jms\docs\examples\stateless\output\lib
+ \stateless-example.jar
+
+deploy:
+ [copy] Copying 1 file to C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server
+ \messaging\deploy
+
+sleep:
+ [echo] Sleeping for 5 seconds ...
+
+run:
+
+send-and-receive:
+ [java] The Hello! message was successfully sent to the /queue/testQueue queue
+ [java] Queue browse result: Hello!
+ [java] Received Hello!
+
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+undeploy:
+ [delete] Deleting: C:\work\src\jboss-4.2.0.GA\build\output\jboss-4.0.3SP1\server\messaging\deploy\
+ stateless-example.jar
+
+BUILD SUCCESSFUL
+Total time: 9 seconds</pre>
</td>
</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. 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" exception</span></h3>
+<p>
+ JBoss Messaging may not have been installed correctly. A fresh JBoss Messaging installation 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 <tt>messaging</tt> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
</body>
</html>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/stateless-clustered/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/stateless-clustered/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/stateless-clustered/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -8,68 +8,72 @@
<body>
<h1>Sending JMS messages from a Stateless Clustered Session Bean</h1>
+$ Revision: 5409 $
-<p>$Revision$</p>
-
<h2>Overview</h2>
<p>
-This example deploys in a cluster a stateless session bean that can then
-send and receive messages from a queue. This is a very simple example that
-demonstrates using JBoss Messaging in a clustered environment.
-The client uses HA-JNDI to look up the session bean. It then invokes the
-session bean to send a message to a test queue and afterwards consumes the same message.
+ This example deploys a stateless session bean in a cluster. The bean then sends and receives messages from a queue. This is a simple example that demonstrates using JBoss Messaging in a clustered environment. The client uses HA-JNDI to lookup the session bean. The client then invokes the session bean to send a message to a test queue, and then consumes the same message from the queue.
</p>
<p>
-This example relies on having access to a running JBoss Messaging cluster.
-The JBoss Messaging cluster must be installed and started according to
-the "JBoss Messaging Clustered Installation" chapter from the release
-documentation. However, the example will automatically deploy its own
-queue, unless a queue with the same name is already deployed.
+ The example requires access to a running JBoss Messaging cluster installed and started according to the <emphasis>Clustered Installation</emphasis> section in the release documentation. The example automatically deploys its own queue unless a queue with the same name is already deployed.
</p>
-<br>
<p>
-This example also relies on having access to <tt>jboss-messaging-client.jar</tt>
-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
-<tt>build.xml</tt> accordingly.
+ This example also requires access to the <tt>jboss-messaging-client.jar</tt> archive included in 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 <tt>build.xml</tt> to specify the location of the archive.
</p>
-<br><br>
-For JBoss5, you should copy all as messaging-node0, configure mysql as a database, make it clustered, and copy it as messaging-node1. Start each instance as:
-<br><br>
-./run -c messaging-node0 -Djboss.service.binding.set=ports-01
-<br><br>
-<br>
-and in another window
-<br><br>
-./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1
-<br><br>
-
-<h2>Running the example</h2>
<p>
-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 <tt>C:\jboss-4.2.0.GA\server\messaging-node0\deploy</tt>,
-then your JBOSS_HOME value should be <tt>C:\jboss-4.2.0.GA</tt>.
+ The root directory of your JBoss Enterprise Application Platform installation contains a <span style="font-family: monospace;">server/all/</span> directory.
</p>
+<ol>
+ <li>
+ <p>Copy the <span style="font-family: monospace;">all</span> directory as <span style="font-family: monospace;">messaging-node0</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r all messaging-node0</span></div>
+ </li>
+ <li>
+ <p>In your new <span style="font-family: monospace;">messaging-node0</span> directory, modify <span style="font-family: monospace;">configure</span> to use a MySQL data source, and the messaging configuration files to make JBoss Messaging clustered.</p>
+ </li>
+ <li>
+ <p>Copy <span style="font-family: monospace;">messaging-node0</span> to another directory as <span style="font-family: monospace;">messaging-node1</span>:</p>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">cp -r messaging-node0 messaging-node1</span></div>
+ </li>
+</ol>
<p>
-2. Go to the example's home directory
+ Start the first instance:
</p>
-<blockquote>
- <pre>cd ...\examples\stateless</pre>
-</blockquote>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node0 -Djboss.service.binding.set=ports-01</span></div>
<p>
-3. Run the example:
+ In a separate window, start the second instance:
</p>
-<blockquote>
- <pre>ant</pre>
-</blockquote>
+ <div style="margin-left: 40px;"><span style="font-family: monospace;">./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1</span></div>
+
+
+
+
+<h2>Running the example</h2>
+<ol>
+ <li>
+ <p>Set the JBOSS_HOME environment variable to point to the instance of JBoss Application Server 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\stateless-clustered</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>
-The output of a successful run should be similar to:
+ A successful run should have output similar to the following:
</p>
-<blockquote>
- <pre>$ ant
+
+<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">
+ <tbody>
+ <tr>
+ <td style="vertical-align: top;"><pre>
+$ ant
Buildfile: build.xml
identify:
@@ -82,17 +86,23 @@
sanity-check:
init:
- [mkdir] Created dir: C:\java\messaging\docs\examples\stateless-clustered\output\classes\META-INF
+ [mkdir] Created dir: C:\java\messaging\docs\examples\stateless-clustered\output\classes
+ \META-INF
[mkdir] Created dir: C:\java\messaging\docs\examples\stateless-clustered\output\lib
compile:
- [javac] Compiling 4 source files to C:\java\messaging\docs\examples\stateless-clustered\output\classes
- [javac] Note: C:\java\messaging\docs\examples\stateless-clustered\src\org\jboss\example\jms\statelessclustered\bean\StatelessClusteredSessionExampleBean.java uses unchecked or unsafe operations.
+ [javac] Compiling 4 source files to C:\java\messaging\docs\examples\stateless-clustered
+ \output\classes
+ [javac] Note: C:\java\messaging\docs\examples\stateless-clustered\src\org\jboss\example
+ \jms\statelessclustered\bean\StatelessClusteredSessionExampleBean.java
+ uses unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
jar:
- [copy] Copying 2 files to C:\java\messaging\docs\examples\stateless-clustered\output\classes\META-INF
- [jar] Building jar: C:\java\messaging\docs\examples\stateless-clustered\output\lib\stateless-clustered-example.jar
+ [copy] Copying 2 files to C:\java\messaging\docs\examples\stateless-clustered\output
+ \classes\META-INF
+ [jar] Building jar: C:\java\messaging\docs\examples\stateless-clustered\output
+ \lib\stateless-clustered-example.jar
deploy:
[copy] Copying 1 file to C:\jboss-4.2.0.GA\server\messaging-node0\farm
@@ -118,17 +128,16 @@
[delete] Deleting: C:\jboss-4.2.0.GA\server\messaging-node0\farm\destinations-farm-service.xml
BUILD SUCCESSFUL
-Total time: 19 seconds
-</pre></blockquote>
+Total time: 19 seconds</pre>
+ </td>
+ </tr>
+ </tbody>
+</table>
-<h2>Troublesooting</h2>
-<h3>1. I get <tt>"javax.jms.JMSSecurityException: User null is NOT authenticated"</tt></h3>
+<h2>Troubleshooting</h2>
+<h3>1. I get a <span style="font-family: monospace;">"javax.jms.JMSSecurityException: User null is NOT authenticated" exception</span></h3>
<p>
-You probably didn't install JBoss Messaging correctly. A fresh JBoss
-Messaging installation requires changes in the security configuration
-of the JBoss instance, specifically a properly configured "<tt>messaging</tt>"
-security domain. Follow the instructions from the "Installation" paragraph of
-the release documentation.
+ JBoss Messaging may not have been installed correctly. A fresh JBoss Messaging installation 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 <tt>messaging</tt> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
</p>
</body>
</html>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/topic/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/topic/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/topic/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -8,136 +8,84 @@
<body>
<br>
<h1>JBoss Messaging Topic Example</h1>
-$Revision$
+$ Revision: 2751 $
<h2>Overview</h2>
-<br>
-This example creates a JMS Connection to a JBoss Messaging instance
-and uses it to create a session, a publisher and a subscriber. The
-publisher sends a message to the topic. The example is considered
-successful
-if the topic subscriber receives the 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. However,
-the example will automatically deploy its own topic, unless a topic
-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>
-<span style="font-style: italic;"></span><br>
+<p>
+ This example creates a Java Message Service (JMS) connection to a JBoss Messaging instance and uses it to create a session, a publisher, and a subscriber. The publisher sends a message to the topic. The example is considered successful if the subscriber receives the message.
+</p>
+<p>
+ This example requires access to a running JBoss Messaging instance that was installed and started according to the <emphasis>Installation</emphasis> section in the JBoss Messaging User Guide. The example automatically deploys its own queue unless a queue with the same name is already deployed.
+</p>
+<p>
+ This example also 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'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 specify the location of 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\default\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\topic</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 instance of JBoss Application Server 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\topic</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">
<tbody>
<tr>
<td style="vertical-align: top;">
- <div style="margin-left: 40px;"><br>
- </div>
-$ ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
- [echo]
-X
-Running the TOPIC
-example
-X<br>
- [echo]
-XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX<br>
- [echo] The topic: testTopic<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\topic\output<br>
- [mkdir] Created dir:
-C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
- <br>
-compile:<br>
- [javac] Compiling 2 source files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\common\output<br>
- [javac] Compiling 2 source files to
-C:\work\src\cvs\jboss-head\jms\docs\examples\topic\output<br>
- <br>
-run:<br>
- [java] Topic /topic/testTopic exists<br>
- [java] The message was successfully published
-on the topic<br>
- [java] Received message: Hello!<br>
- [java] The example connected to JBoss
-Messaging version 1.2.0.GA (1.2)<br>
- <br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 4 seconds<br>
- <br>
- <br>
+ <div style="margin-left: 40px;"><pre>$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ [echo] X Running the TOPIC example X
+ [echo] XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ [echo] The topic: testTopic
+
+sanity-check:
+
+init:
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\topic\output
+ [mkdir] Created dir: C:\work\src\cvs\jboss-head\jms\docs\examples\common\output
+
+compile:
+ [javac] Compiling 2 source files to C:\work\src\cvs\jboss-head\jms\docs\examples\common\output
+ [javac] Compiling 2 source files to C:\work\src\cvs\jboss-head\jms\docs\examples\topic\output
+
+run:
+ [java] Topic /topic/testTopic exists
+ [java] The message was successfully published on the topic
+ [java] Received message: Hello!
+ [java] The example connected to JBoss Messaging version 1.2.0.GA (1.2)
+
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+BUILD SUCCESSFUL
+Total time: 4 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" exception</span></h3>
+<p>
+ JBoss Messaging may not have been installed correctly. A fresh JBoss Messaging installation 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 <tt>messaging</tt> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
</body>
</html>
Modified: tags/JBossMessaging_1_4_6_GA/docs/examples/web-service/README.html
===================================================================
--- tags/JBossMessaging_1_4_6_GA/docs/examples/web-service/README.html 2009-10-27 05:28:03 UTC (rev 7871)
+++ tags/JBossMessaging_1_4_6_GA/docs/examples/web-service/README.html 2009-10-28 01:52:10 UTC (rev 7872)
@@ -7,175 +7,113 @@
</head>
<body>
<br>
-<h1>Sending JMS messages from a WebService<br>
-</h1>
+<h1>Sending JMS messages from a WebService</h1>
<h2>Overview</h2>
-<br>
-This example deploys a WebServices that sends messages to a queue.
-The same client will then read the message from the queue, validating
-if the WebService could complete the message send.
-<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>
-This example will also generate client classes using wsdltools from
-JBoss Web Services.<br>
-<br>
+<p>
+ This example deploys a WebService that sends messages to a queue. The same client then reads the message from the queue, confirming that the WebService could complete the message send operation.
+</p>
+<p>
+ This example requires access to a running JBoss Messaging instance that was installed and started according to the <emphasis>Installation</emphasis> section in the JBoss Messaging User Guide. The example automatically deploys its own queue unless a queue with the same name is already deployed.
+</p>
+<p>
+ This example also 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'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 specify the location of the archive.
+</p>
+<p>
+ This example also generates client classes using <tt>wsdltools</tt> from JBoss Web Services.
+</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\web-services</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 instance of JBoss Application Server 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\web-services</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">
<tbody>
<tr>
- <td style="vertical-align: top;">
- <div style="margin-left: 40px;"><br>
- </div>
-example at example:/workspace/jboss-messaging-1.3.0.GA/examples/web-services$
-ant<br>
-Buildfile: build.xml<br>
- <br>
-identify:<br>
- [echo]
-###########################################################################<br>
- [echo]
-#
-Running the WebServices
-example
-#<br>
- [echo]
-###########################################################################<br>
- [echo] The
-queue: testQueue<br>
- [echo] The client jar:
-../..//jboss-messaging-client.jar<br>
- <br>
-sanity-check:<br>
- <br>
-init:<br>
- <br>
-compile:<br>
- <br>
-war:<br>
- [jar] Building jar:
-/workspace/jboss-messaging-1.3.0.GA/examples/web-services/output/lib/jms-web-service.war<br>
- <br>
-deploy:<br>
- [copy] Copying 1 file to
-/jboss-4.2.0.GA/server/messaging/deploy<br>
- <br>
-sleep:<br>
- [echo] Sleeping for 5 seconds ...<br>
- <br>
-run-wsdl-client:<br>
- [get] Getting:
-http://127.0.0.1:8080/jms-web-service/JMSWebServiceExample?wsdl<br>
- [get] To:
-/workspace/jboss-messaging-1.3.0.GA/examples/web-services/output/service.wsdl<br>
- [wstools] log4j:WARN No appenders could be found for logger
-(org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory).<br>
- [wstools] log4j:WARN Please initialize the log4j system properly.<br>
- <br>
-compile-client:<br>
- [mkdir] Created dir:
-/workspace/jboss-messaging-1.2.0.SP2/examples/web-services/output/client-classes<br>
- [javac] Compiling 5 source files to
-/workspace/jboss-messaging-1.2.0.SP2/examples/web-services/output/client-classes<br>
- <br>
-run:<br>
- <br>
-send-and-receive:<br>
- [java] log4j:WARN No appenders could be found
-for logger
-(org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder).<br>
- [java] log4j:WARN Please initialize the log4j
-system properly.<br>
- [java] Message was received ok!<br>
- [java]<br>
- [java] #####################<br>
- [java] ###
-SUCCESS! ###<br>
- [java] #####################<br>
- <br>
-undeploy:<br>
- [delete] Deleting:
-/jboss-4.2.0.GA/server/messaging/deploy/jms-web-service.war<br>
- <br>
-BUILD SUCCESSFUL<br>
-Total time: 12 seconds<br>
- <br>
- <br>
+ <td style="vertical-align: top;"><pre>example at example:/workspace/jboss-messaging-1.3.0.GA/examples/web-services$ ant
+Buildfile: build.xml
+
+identify:
+ [echo] ###########################################################################
+ [echo] # Running the WebServices example #
+ [echo] ###########################################################################
+ [echo] The queue: testQueue
+ [echo] The client jar: ../..//jboss-messaging-client.jar
+
+sanity-check:
+
+init:
+
+compile:
+
+war:
+ [jar] Building jar: /workspace/jboss-messaging-1.3.0.GA/examples/web-services/output
+ /lib/jms-web-service.war
+
+deploy:
+ [copy] Copying 1 file to /jboss-4.2.0.GA/server/messaging/deploy
+
+sleep:
+ [echo] Sleeping for 5 seconds ...
+
+run-wsdl-client:
+ [get] Getting: http://127.0.0.1:8080/jms-web-service/JMSWebServiceExample?wsdl
+ [get] To: /workspace/jboss-messaging-1.3.0.GA/examples/web-services/output/service.wsdl
+ [wstools] log4j:WARN No appenders could be found for logger
+ (org.jboss.ws.tools.wsdl.WSDLDefinitionsFactory).
+ [wstools] log4j:WARN Please initialize the log4j system properly.
+
+compile-client:
+ [mkdir] Created dir: /workspace/jboss-messaging-1.2.0.SP2/examples/web-services/output
+ /client-classes
+ [javac] Compiling 5 source files to /workspace/jboss-messaging-1.2.0.SP2/examples
+ /web-services/output/client-classes
+
+run:
+
+send-and-receive:
+ [java] log4j:WARN No appenders could be found for logger
+ (org.jboss.ws.metadata.builder.jaxrpc.JAXRPCClientMetaDataBuilder).
+ [java] log4j:WARN Please initialize the log4j system properly.
+ [java] Message was received ok!
+ [java]
+ [java] #####################
+ [java] ### SUCCESS! ###
+ [java] #####################
+
+undeploy:
+ [delete] Deleting: /jboss-4.2.0.GA/server/messaging/deploy/jms-web-service.war
+
+BUILD SUCCESSFUL
+Total time: 12 seconds</pre>
</td>
</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. Follow the instructions from the "Installation"
-paragraph of the release documentation. <br>
-<h3>2. <span style="font-family: monospace;">wstools doesn't work</span></h3>
-You could aways using "ant -debug" to verify what Exceptions wstools is
-generating. A common error is a NullPointerException due to a xerces
-update required by JBoss Web Services. You could have more information
-at this <a
- href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQXercesNPE">page</a>:<br>
-<br>
-<a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQXercesNPE">http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQXercesNPE</a><br>
-<br>
-<br>
-<br>
-<br>
-<hr style="width: 100%; height: 2px;"><br>
-<br>
-<br>
-<br>
-<br>
-<br>
-<br>
-</span>
+<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 JBoss Messaging installation 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 <tt>messaging</tt> security domain. Follow the instructions in the <emphasis>Installation</emphasis> section of the release documentation.
+</p>
+<h3>2. <span style="font-family: monospace;">wstools</span> does not work</h3>
+<p>
+ Try using <tt>ant -debug</tt> to verify the exceptions that <tt>wstools</tt> is generating. One common error is a <tt>NullPointerException</tt> because of a xerces update required by JBoss Web Services. You can find more information on the <a href="http://wiki.jboss.org/wiki/Wiki.jsp?page=JBWSFAQXercesNPE">JBoss Wiki</a>.
+</p>
</body>
</html>
More information about the jboss-cvs-commits
mailing list