[jboss-cvs] JBoss Messaging SVN: r6334 - in trunk/examples/jms: expiry and 1 other directory.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue Apr 7 07:09:03 EDT 2009
Author: jmesnil
Date: 2009-04-07 07:09:03 -0400 (Tue, 07 Apr 2009)
New Revision: 6334
Modified:
trunk/examples/jms/dead-letter/readme.html
trunk/examples/jms/expiry/readme.html
Log:
Expiry and Dead Letter examples
* updated READMES so that links points to the examples' local config dir
Modified: trunk/examples/jms/dead-letter/readme.html
===================================================================
--- trunk/examples/jms/dead-letter/readme.html 2009-04-07 11:09:02 UTC (rev 6333)
+++ trunk/examples/jms/dead-letter/readme.html 2009-04-07 11:09:03 UTC (rev 6334)
@@ -19,25 +19,21 @@
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 queue settings configuration file <a href="../common/config/jbm-queues.xml">jbm-queues.xml</a>:</p>
+ <p><em>Dead letter destinations</em> and <em>maximum delivery attempts</em> are defined in the queue settings configuration file <a href="config/jbm-queues.xml">jbm-queues.xml</a>:</p>
<pre>
- <code><!--default for all queues-->
- <address-settings match="#">
- ...
- <dead-letter-address>queuejms.deadLetterQueue</dead-letter-address>
- ...
- <max-delivery-attempts>3</max-delivery-attempts>
- ...
- </address-settings></code>
+ <code><address-settings match="jms.queue.exampleQueue">
+ <dead-letter-address>jms.queue.deadLetterQueue</dead-letter-address>
+ <max-delivery-attempts>3</max-delivery-attempts>
+ </address-settings>
</pre>
- <p>This configuration will moved dead letter messages from any given queue (the wildcard <code>#</code>) to the <code>deadLetterQueue</code>.</p>
- <p>JBoss Messaging allows to specify either a <code>Queue</code> by prefixing the <code>dead-letter-address</code> with <code>queuejms.</code>
- or a <code>Topic</code> by prefixing with <code>topicjms.</code>.<br />
+ <p>This configuration will moved dead letter messages from <code>exampleQueue</code> to the <code>deadLetterQueue</code>.</p>
+ <p>JBoss Messaging allows to specify either a <code>Queue</code> by prefixing the <code>dead-letter-address</code> with <code>jms.queue.</code>
+ or a <code>Topic</code> by prefixing with <code>jms.topic.</code>.<br />
In this example, we will use a <code>Queue</code> to hold the dead letter messages.</p>
<p>The maximum attempts of delivery is <code>3</code>. Once this figure is reached, a message is considered a dead letter message and is moved to
the <code>deadLetterQueue</code>.
<p>Since we want to consume messages from this deadLetterQueue, we also need to add a JNDI binding to perform a lookup.
- This is configured in <a href="../common/config/jbm-jms.xml">jbm-jms.xml</a></p>
+ This is configured in <a href="config/jbm-jms.xml">jbm-jms.xml</a></p>
<pre>
<code><queue name="deadLetterQueue">
<entry name="/queue/deadLetterQueue"/>
Modified: trunk/examples/jms/expiry/readme.html
===================================================================
--- trunk/examples/jms/expiry/readme.html 2009-04-07 11:09:02 UTC (rev 6333)
+++ trunk/examples/jms/expiry/readme.html 2009-04-07 11:09:03 UTC (rev 6334)
@@ -17,20 +17,18 @@
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="../common/config/jbm-queues.xml">jbm-queues.xml</a>:</p>
+ <p>Expiry destinations are defined as in the queue settings configuration file <a href="config/jbm-queues.xml">jbm-queues.xml</a>:</p>
<pre>
- <code><!--default for all queues-->
- <address-settings match="#">
- ...
- <expiry-address>queuejms.expiryQueue</expiry-address>
- </address-settings></code>
+ <code><address-settings match="jms.queue.exampleQueue">
+ <expiry-address>jms.queue.expiryQueue</expiry-address>
+ </address-settings>
</pre>
- <p>This configuration will moved expired messages from any given queue (the wildcard <code>#</code>) to the <code>expiryQueue</code></p>
- <p>JBoss Messaging allows to specify either a <code>Queue</code> by prefixing the <code>expiry-address</code> with <code>queuejms.</code>
- or a <code>Topic</code> by prefixing with <code>topicjms.</code>.<br />
+ <p>This configuration will moved expired messages from the <code>exampleQueue</code> to the <code>expiryQueue</code></p>
+ <p>JBoss Messaging allows to specify either a <code>Queue</code> by prefixing the <code>expiry-address</code> with <code>jms.queue.</code>
+ or a <code>Topic</code> by prefixing with <code>jms.topic.</code>.<br />
In this example, we will use a <code>Queue</code> to hold the expired messages.</p>
<p>Since we want to consume messages from this expiryQueue, we also need to add a JNDI binding to perform a lookup.
- This is configured in <a href="../common/config/jbm-jms.xml">jbm-jms.xml</a></p>
+ This is configured in <a href="config/jbm-jms.xml">jbm-jms.xml</a></p>
<pre>
<code><queue name="expiryQueue">
<entry name="/queue/expiryQueue"/>
More information about the jboss-cvs-commits
mailing list