[jboss-cvs] JBoss Messaging SVN: r6341 - 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 08:32:35 EDT 2009
Author: jmesnil
Date: 2009-04-07 08:32:35 -0400 (Tue, 07 Apr 2009)
New Revision: 6341
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' server0 dir
Modified: trunk/examples/jms/dead-letter/readme.html
===================================================================
--- trunk/examples/jms/dead-letter/readme.html 2009-04-07 12:18:56 UTC (rev 6340)
+++ trunk/examples/jms/dead-letter/readme.html 2009-04-07 12:32:35 UTC (rev 6341)
@@ -19,7 +19,7 @@
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="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="server0/jbm-queues.xml">jbm-queues.xml</a>:</p>
<pre>
<code><address-settings match="jms.queue.exampleQueue">
<dead-letter-address>jms.queue.deadLetterQueue</dead-letter-address>
@@ -33,7 +33,7 @@
<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="config/jbm-jms.xml">jbm-jms.xml</a></p>
+ This is configured in <a href="server0/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 12:18:56 UTC (rev 6340)
+++ trunk/examples/jms/expiry/readme.html 2009-04-07 12:32:35 UTC (rev 6341)
@@ -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="config/jbm-queues.xml">jbm-queues.xml</a>:</p>
+ <p>Expiry destinations are defined as in the queue settings configuration file <a href="server0/jbm-queues.xml">jbm-queues.xml</a>:</p>
<pre>
<code><address-settings match="jms.queue.exampleQueue">
<expiry-address>jms.queue.expiryQueue</expiry-address>
@@ -28,7 +28,7 @@
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="config/jbm-jms.xml">jbm-jms.xml</a></p>
+ This is configured in <a href="server0/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