[jboss-cvs] JBoss Messaging SVN: r5409 - in branches/Branch_1_4/docs/examples: distributed-topic and 2 other directories.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Fri Nov 21 00:05:42 EST 2008 

Author: clebert.suconic at jboss.com
Date: 2008-11-21 00:05:42 -0500 (Fri, 21 Nov 2008)
New Revision: 5409

Modified:
   branches/Branch_1_4/docs/examples/distributed-queue/README.html
   branches/Branch_1_4/docs/examples/distributed-topic/README.html
   branches/Branch_1_4/docs/examples/queue-failover/README.html
   branches/Branch_1_4/docs/examples/stateless-clustered/README.html
Log:
Adding instructions on readmes

Modified: branches/Branch_1_4/docs/examples/distributed-queue/README.html
===================================================================
--- branches/Branch_1_4/docs/examples/distributed-queue/README.html	2008-11-21 04:43:36 UTC (rev 5408)
+++ branches/Branch_1_4/docs/examples/distributed-queue/README.html	2008-11-21 05:05:42 UTC (rev 5409)
@@ -21,15 +21,16 @@
 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>
+<<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
+./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-01 -Djboss.messaging.ServerPeerID=1
+./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1
+<br><br>
 <span style="font-style: italic;"></span><br>
 <h2>Running the example</h2>
 <span style="font-family: monospace;"></span><span

Modified: branches/Branch_1_4/docs/examples/distributed-topic/README.html
===================================================================
--- branches/Branch_1_4/docs/examples/distributed-topic/README.html	2008-11-21 04:43:36 UTC (rev 5408)
+++ branches/Branch_1_4/docs/examples/distributed-topic/README.html	2008-11-21 05:05:42 UTC (rev 5409)
@@ -23,16 +23,17 @@
 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
+./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-01 -Djboss.messaging.ServerPeerID=1
-<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>
 <h2>Running the example</h2>
 <span style="font-family: monospace;"></span><span

Modified: branches/Branch_1_4/docs/examples/queue-failover/README.html
===================================================================
--- branches/Branch_1_4/docs/examples/queue-failover/README.html	2008-11-21 04:43:36 UTC (rev 5408)
+++ branches/Branch_1_4/docs/examples/queue-failover/README.html	2008-11-21 05:05:42 UTC (rev 5409)
@@ -22,6 +22,14 @@
 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:
@@ -33,14 +41,6 @@
 <br><br>
 ./run.sh -c messaging-node1 -Djboss.service.binding.set=ports-02 -Djboss.messaging.ServerPeerID=1
 <br><br>
-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>
 <h2>Running the example</h2>
 <span style="font-family: monospace;"></span><span
  style="font-family: monospace;"></span><br>

Modified: branches/Branch_1_4/docs/examples/stateless-clustered/README.html
===================================================================
--- branches/Branch_1_4/docs/examples/stateless-clustered/README.html	2008-11-21 04:43:36 UTC (rev 5408)
+++ branches/Branch_1_4/docs/examples/stateless-clustered/README.html	2008-11-21 05:05:42 UTC (rev 5409)
@@ -26,6 +26,7 @@
 documentation.&nbsp; However, the example will automatically deploy 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
@@ -33,7 +34,18 @@
 configured to find the client jar. Otherwise, you must modify example's
 <tt>build.xml</tt> accordingly.
 </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

More information about the jboss-cvs-commits mailing list