[jboss-cvs] JBoss Messaging SVN: r6770 - in trunk/examples/jms: clustered-queue and 12 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed May 13 11:14:22 EDT 2009
Author: jmesnil
Date: 2009-05-13 11:14:21 -0400 (Wed, 13 May 2009)
New Revision: 6770
Modified:
trunk/examples/jms/clustered-durable-subscription/readme.html
trunk/examples/jms/clustered-queue/readme.html
trunk/examples/jms/clustered-topic/readme.html
trunk/examples/jms/dead-letter/readme.html
trunk/examples/jms/delayed-redelivery/readme.html
trunk/examples/jms/expiry/readme.html
trunk/examples/jms/last-value-queue/readme.html
trunk/examples/jms/management-notifications/readme.html
trunk/examples/jms/management/readme.html
trunk/examples/jms/message-counters/readme.html
trunk/examples/jms/message-group/readme.html
trunk/examples/jms/queue-message-redistribution/readme.html
trunk/examples/jms/security/readme.html
trunk/examples/jms/transactional/readme.html
Log:
JMS examples
* updated readmes after recent configuration changes (no more jbm-queues.xml, etc.)
Modified: trunk/examples/jms/clustered-durable-subscription/readme.html
===================================================================
--- trunk/examples/jms/clustered-durable-subscription/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/clustered-durable-subscription/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -25,16 +25,15 @@
<p>Here's the relevant snippet from the server configuration, which tells the server to form a cluster between the two nodes
and to load balance the messages between the nodes.</p>
<pre>
- <code>
- <cluster-connection name="my-cluster">
- <address>jms</address>
- <retry-interval>500</retry-interval>
- <use-duplicate-detection>true</use-duplicate-detection>
- <forward-when-no-consumers>true</forward-when-no-consumers>
- <max-hops>1</max-hops>
- <discovery-group-ref discovery-group-name="my-discovery-group"/>
- </cluster-connection>
- </code>
+ <code><cluster-connection name="my-cluster">
+ <address>jms</address>
+ <retry-interval>500</retry-interval>
+ <use-duplicate-detection>true</use-duplicate-detection>
+ <forward-when-no-consumers>true</forward-when-no-consumers>
+ <max-hops>1</max-hops>
+ <discovery-group-ref discovery-group-name="my-discovery-group"/>
+ </cluster-connection>
+ </code>
</pre>
<p>For more information on JBoss Messaging load balancing, and clustering in general, please see the clustering
section of the user manual.</p>
Modified: trunk/examples/jms/clustered-queue/readme.html
===================================================================
--- trunk/examples/jms/clustered-queue/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/clustered-queue/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -16,16 +16,15 @@
<p>Here's the relevant snippet from the server configuration, which tells the server to form a cluster between the two nodes
and to load balance the messages between the nodes.</p>
<pre>
- <code>
- <cluster-connection name="my-cluster">
- <address>jms</address>
- <retry-interval>500</retry-interval>
- <use-duplicate-detection>true</use-duplicate-detection>
- <forward-when-no-consumers>true</forward-when-no-consumers>
- <max-hops>1</max-hops>
- <discovery-group-ref discovery-group-name="my-discovery-group"/>
- </cluster-connection>
- </code>
+ <code><cluster-connection name="my-cluster">
+ <address>jms</address>
+ <retry-interval>500</retry-interval>
+ <use-duplicate-detection>true</use-duplicate-detection>
+ <forward-when-no-consumers>true</forward-when-no-consumers>
+ <max-hops>1</max-hops>
+ <discovery-group-ref discovery-group-name="my-discovery-group"/>
+ </cluster-connection>
+ </code>
</pre>
<p>For more information on JBoss Messaging load balancing, and clustering in general, please see the clustering
section of the user manual.</p>
Modified: trunk/examples/jms/clustered-topic/readme.html
===================================================================
--- trunk/examples/jms/clustered-topic/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/clustered-topic/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -17,16 +17,15 @@
<p>Here's the relevant snippet from the server configuration, which tells the server to form a cluster between the two nodes
and to load balance the messages between the nodes.</p>
<pre>
- <code>
- <cluster-connection name="my-cluster">
- <address>jms</address>
- <retry-interval>500</retry-interval>
- <use-duplicate-detection>true</use-duplicate-detection>
- <forward-when-no-consumers>true</forward-when-no-consumers>
- <max-hops>1</max-hops>
- <discovery-group-ref discovery-group-name="my-discovery-group"/>
- </cluster-connection>
- </code>
+ <code><cluster-connection name="my-cluster">
+ <address>jms</address>
+ <retry-interval>500</retry-interval>
+ <use-duplicate-detection>true</use-duplicate-detection>
+ <forward-when-no-consumers>true</forward-when-no-consumers>
+ <max-hops>1</max-hops>
+ <discovery-group-ref discovery-group-name="my-discovery-group"/>
+ </cluster-connection>
+ </code>
</pre>
<p>For more information on JBoss Messaging load balancing, and clustering in general, please see the clustering
section of the user manual.</p>
Modified: trunk/examples/jms/dead-letter/readme.html
===================================================================
--- trunk/examples/jms/dead-letter/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/dead-letter/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -19,12 +19,12 @@
We will then consume the message from this dead letter queue.
</p>
<h2>Example setup</h2>
- <p><em>Dead letter destinations</em> and <em>maximum delivery attempts</em> are defined in the address settings configuration file <a href="server0/jbm-queues.xml">jbm-queues.xml</a>:</p>
+ <p><em>Dead letter destinations</em> and <em>maximum delivery attempts</em> are defined in the configuration file <a href="server0/jbm-configuration.xml">jbm-configuration.xml</a>:</p>
<pre>
- <code><address-settings match="jms.queue.exampleQueue">
+ <code><address-setting match="jms.queue.exampleQueue">
<dead-letter-address>jms.queue.deadLetterQueue</dead-letter-address>
<max-delivery-attempts>3</max-delivery-attempts>
- </address-settings>
+ </address-setting>
</code>
</pre>
<p>This configuration will moved dead letter messages from <code>exampleQueue</code> to the <code>deadLetterQueue</code>.</p>
Modified: trunk/examples/jms/delayed-redelivery/readme.html
===================================================================
--- trunk/examples/jms/delayed-redelivery/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/delayed-redelivery/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -18,16 +18,16 @@
matching on the address settings.</p>
<h2>Example setup</h2>
- <p>Redelivery delay is specified in the address settings configuration file <a href="server0/jbm-queues.xml">jbm-queues.xml</a>:</p>
+ <p>Redelivery delay is specified in the configuration file <a href="server0/jbm-configuration.xml">jbm-configuration.xml</a>:</p>
<p>In this example we set the redelivery delay to 5 seconds for the specific example queue. We could set redelivery delay on
on multiple queues by specifying a wild-card in the match, e.g. <code>match="jms.#"</code> would apply the settings
to all JMS queues and topics.</p>
<p>We then consume a message in a transacted session, and rollback, and note that the message is not redelivered until
after 5 seconds.</p>
<pre>
- <code><address-settings match="jms.queue.exampleQueue">
+ <code><address-setting match="jms.queue.exampleQueue">
<redelivery-delay>5000</redelivery-delay>
- </address-settings>
+ </address-setting>
</code>
</pre>
<p><i>To run the example, simply type <code>ant</code> from this directory</i></p>
Modified: trunk/examples/jms/expiry/readme.html
===================================================================
--- trunk/examples/jms/expiry/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/expiry/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -17,7 +17,7 @@
We will instead consume it from an <em>expiry queue</em> where it was moved when it expired.
</p>
<h2>Example setup</h2>
- <p>Expiry destinations are defined as in the queue settings configuration file <a href="server0/jbm-queues.xml">jbm-queues.xml</a>:</p>
+ <p>Expiry destinations are defined in the configuration file <a href="server0/jbm-configuration.xml">jbm-configuration.xml</a>:</p>
<pre>
<code><address-setting match="jms.queue.exampleQueue">
<expiry-address>jms.queue.expiryQueue</expiry-address>
Modified: trunk/examples/jms/last-value-queue/readme.html
===================================================================
--- trunk/examples/jms/last-value-queue/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/last-value-queue/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -16,11 +16,11 @@
We will then consume from the queue the <em>last</em> message.</p>
<h2>Example setup</h2>
- <p>Last-Value queues are defined in the queue settings configuration file <a href="server0/jbm-queues.xml">jbm-queues.xml</a>:</p>
+ <p>Last-Value queues are defined in the configuration file <a href="server0/jbm-configuration.xml">jbm-configuration.xml</a>:</p>
<pre>
- <code><address-settings match="jms.queue.lastValueQueue">
+ <code><address-setting match="jms.queue.lastValueQueue">
<last-value-queue>true</last-value-queue>
- </address-settings></code>
+ </address-setting></code>
</pre>
<h2>Example step-by-step</h2>
Modified: trunk/examples/jms/management/readme.html
===================================================================
--- trunk/examples/jms/management/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/management/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -17,11 +17,11 @@
</pre>
<p>The management queue requires a "special" user permission <code>manage</code> to be able to receive management messages.
- This is configured in <a href="server0/jbm-queues.xml">jbm-queues.xml</a></p>
+ This is also configured in <a href="server0/jbm-configuration.xml">jbm-configuration.xml</a></p>
<pre>
- <code><security match="jbm.management">
+ <code><security-setting match="jbm.management">
<permission type="manage" roles="guest" />
- </security></code>
+ </security-setting></code>
</pre>
<h2>Example step-by-step</h2>
Modified: trunk/examples/jms/management-notifications/readme.html
===================================================================
--- trunk/examples/jms/management-notifications/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/management-notifications/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -31,14 +31,14 @@
</queues></code>
</pre>
<p>The notification queue requires permission to create/delete temporary queues and consume messages.
- This is configured in <a href="server0/jbm-queues.xml">jbm-queues.xml</a></p>
+ This is also configured in <a href="server0/jbm-configuration.xml">jbm-configuration.xml</a></p>
<pre>
<code><!--security for notification queue-->
- <security match="example.notifications">
+ <security-setting match="example.notifications">
<permission type="consume" roles="guest"/>
<permission type="createTempQueue" roles="guest"/>
<permission type="deleteTempQueue" roles="guest"/>
- </security></code>
+ </security-setting></code>
</pre>
<h2>Example step-by-step</h2>
Modified: trunk/examples/jms/message-counters/readme.html
===================================================================
--- trunk/examples/jms/message-counters/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/message-counters/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -12,7 +12,7 @@
at different times to display the metrics on the queue.
</p>
<h2>Example setup</h2>
- <p>Message counter is configured in the server configuration file <a href="server0/jbm-configuration.xml">jbm-queues.xml</a>:</p>
+ <p>Message counter is configured in the server configuration file <a href="server0/jbm-configuration.xml">jbm-configuration.xml</a>:</p>
<pre>
<code><message-counter-enabled>true</message-counter-enabled>
<message-counter-sample-period>2000</message-counter-sample-period>
Modified: trunk/examples/jms/message-group/readme.html
===================================================================
--- trunk/examples/jms/message-group/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/message-group/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -19,9 +19,9 @@
<pre>
<code>
- <address-settings match="jms.queue.exampleQueue">
+ <address-setting match="jms.queue.exampleQueue">
<distribution-policy-class>org.jboss.messaging.core.server.impl.GroupingRoundRobinDistributor</distribution-policy-class>
- </address-settings>
+ </address-setting>
</code>
</pre>
Modified: trunk/examples/jms/queue-message-redistribution/readme.html
===================================================================
--- trunk/examples/jms/queue-message-redistribution/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/queue-message-redistribution/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -26,9 +26,9 @@
<code>jms.</code></p>
<pre>
<code>
- <address-settings match="jms.#">
+ <address-setting match="jms.#">
<redistribution-delay>0</redistribution-delay>
- </address-settings>
+ </address-setting>
</code>
</pre>
<p>For more information on JBoss Messaging load balancing, and clustering in general, please see the clustering
Modified: trunk/examples/jms/security/readme.html
===================================================================
--- trunk/examples/jms/security/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/security/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -56,36 +56,38 @@
<p>
User name and password consists of a valid account that can be used to establish connections to a JBoss Messaging server, while
roles are used in controling the access privileges against JBoss Messaging topics and queues. You can achieve this control by
- configuring proper permissions in <code>jbm-queues.xml</code>, like in the following
+ configuring proper permissions in <code>jbm-configuration.xml</code>, like in the following
</p>
<pre><code>
- <!-- any user can have full control of generic topics -->
- <security match="jms.topic.#">
+ <security-settings>
+ <!-- any user can have full control of generic topics -->
+ <security-setting match="jms.topic.#">
<permission type="createDurableQueue" roles="user"/>
<permission type="deleteDurableQueue" roles="user"/>
<permission type="createTempQueue" roles="user"/>
<permission type="deleteTempQueue" roles="user"/>
<permission type="send" roles="user"/>
<permission type="consume" roles="user"/>
- </security>
+ </security-setting>
- <security match="jms.topic.news.europe.#">
+ <security-setting match="jms.topic.news.europe.#">
<permission type="createDurableQueue" roles="user"/>
<permission type="deleteDurableQueue" roles="user"/>
<permission type="createTempQueue" roles="user"/>
<permission type="deleteTempQueue" roles="user"/>
<permission type="send" roles="europe-user"/>
<permission type="consume" roles="news-user"/>
- </security>
+ </security-setting>
- <security match="jms.topic.news.us.#">
+ <security-setting match="jms.topic.news.us.#">
<permission type="createDurableQueue" roles="user"/>
<permission type="deleteDurableQueue" roles="user"/>
<permission type="createTempQueue" roles="user"/>
<permission type="deleteTempQueue" roles="user"/>
<permission type="send" roles="us-user"/>
<permission type="consume" roles="news-user"/>
- </security>
+ </security-setting>
+ </security-settings>
</code></pre>
<p>Permissions can be defined on any group of queues, by using a wildcard. You can easily specify
Modified: trunk/examples/jms/transactional/readme.html
===================================================================
--- trunk/examples/jms/transactional/readme.html 2009-05-13 14:44:41 UTC (rev 6769)
+++ trunk/examples/jms/transactional/readme.html 2009-05-13 15:14:21 UTC (rev 6770)
@@ -1,6 +1,7 @@
<html>
<head>
<title>JBoss Messaging JMS Transactional Session Example</title>
+ <link rel="stylesheet" type="text/css" href="../common/common.css">
</head>
<body>
<h1>JMS Transactional Session Example</h1>
More information about the jboss-cvs-commits
mailing list