[jboss-cvs] JBoss Messaging SVN: r7013 - trunk/docs/user-manual/en.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Tue May 26 06:14:12 EDT 2009
Author: jmesnil
Date: 2009-05-26 06:14:12 -0400 (Tue, 26 May 2009)
New Revision: 7013
Modified:
trunk/docs/user-manual/en/embedding-jbm.xml
trunk/docs/user-manual/en/examples.xml
trunk/docs/user-manual/en/flow-control.xml
trunk/docs/user-manual/en/intercepting-operations.xml
trunk/docs/user-manual/en/large-messages.xml
trunk/docs/user-manual/en/last-value-queues.xml
trunk/docs/user-manual/en/management.xml
trunk/docs/user-manual/en/message-expiry.xml
trunk/docs/user-manual/en/message-grouping.xml
trunk/docs/user-manual/en/paging.xml
trunk/docs/user-manual/en/pre-acknowledge.xml
trunk/docs/user-manual/en/scheduled-messages.xml
trunk/docs/user-manual/en/security.xml
trunk/docs/user-manual/en/undelivered-messages.xml
Log:
user manual proof-reading
* updated examples links to link to the examples.xml chapter
instead of the examples directory
Modified: trunk/docs/user-manual/en/embedding-jbm.xml
===================================================================
--- trunk/docs/user-manual/en/embedding-jbm.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/embedding-jbm.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -170,8 +170,7 @@
</section>
<section>
<title>JMS Embedding Example</title>
- <para>The <ulink url="../../../../examples/jms/embedded/readme.html"><literal>JMS
- Embedding</literal> Example</ulink> shows how to setup and run JBoss Messaging
- embedded with JMS...</para>
+ <para>Please see <xref linkend="examples.embedded" /> for an example which shows how
+ to setup and run JBoss Messaging embedded with JMS.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/examples.xml
===================================================================
--- trunk/docs/user-manual/en/examples.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/examples.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -38,7 +38,7 @@
</section>
<section id="automatic-failover">
<title>Automatic (Transparent) Failover</title>
- <para>This example demonstrates two servers coupled as a live-backup pair for high
+ <para>The <literal>automatic-failover</literal> example demonstrates two servers coupled as a live-backup pair for high
availability (HA), and a client connection transparently failing over from live to
backup when the live server is crashed.</para>
<para>JBoss Messaging implements seamless, transparent failover of client connections
@@ -49,7 +49,7 @@
</section>
<section>
<title>Automatic Reconnect</title>
- <para>This example demonstrates how JBoss Messaging connections can be configured to be
+ <para>The <literal>reconnect-same-node</literal> example demonstrates how JBoss Messaging connections can be configured to be
resilient to temporary network failures.</para>
<para> In the case of a network failure being detected, either as a result of a failure
to read/write to the connection, or the failure of a pong to arrive back from the
@@ -58,9 +58,9 @@
JBoss Messaging can be configured to automatically retry the connection, and
reconnect to the server when it becomes available again across the network.</para>
</section>
- <section>
+ <section id="examples.browsers">
<title>Browser</title>
- <para>This example shows you how to use a JMS <literal>QueueBrowser</literal> with JBoss
+ <para>The <literal>browser</literal> example shows you how to use a JMS <literal>QueueBrowser</literal> with JBoss
Messaging.</para>
<para>Queues are a standard part of JMS, please consult the JMS 1.1 specification for
full details.</para>
@@ -68,9 +68,9 @@
without removing them. It can scan the entire content of a queue or only messages
matching a message selector.</para>
</section>
- <section>
+ <section id="examples.bridge">
<title>Core Bridge Example</title>
- <para>This example demonstrates a core bridge deployed on one server, which consumes
+ <para>The <literal>bridge</literal> example demonstrates a core bridge deployed on one server, which consumes
messages from a local queue and forwards them to an address on a second
server.</para>
<para>Core bridges are used to create message flows between any two JBoss Messaging
@@ -80,27 +80,27 @@
</section>
<section>
<title>Client Kickoff</title>
- <para>This example shows how to terminate client connections given an IP address using
+ <para>The <literal>client-kickoff</literal> example shows how to terminate client connections given an IP address using
the JMX management API.</para>
</section>
<section>
<title>Client Side Load-Balancing</title>
- <para>This example demonstrates how subsequent connections created from a JMS <literal
+ <para>The <literal>client-side-load-balancing</literal> example demonstrates how subsequent connections created from a JMS <literal
>ConnectionFactory</literal> can be created to different nodes of the cluster.
In other words it demonstrates how JBoss Messaging does client side load balancing
of connections across the cluster.</para>
</section>
<section>
<title>Clustered Topic</title>
- <para>This example demonstrates a JMS topic deployed on two different nodes. The two
+ <para>The <literal>clustered-topic</literal> example demonstrates a JMS topic deployed on two different nodes. The two
nodes are configured to form a cluster. We then create a subscriber on the topic on
each node, and we create a producer on only one of the nodes. We then send some
messages via the producer, and we verify that both subscribers receive all the sent
messages.</para>
</section>
- <section>
+ <section id="examples.dead-letter">
<title>Dead Letter</title>
- <para>This example shows you how to define and deal with dead letter messages. Messages
+ <para>The <literal>dead-letter</literal> example shows you how to define and deal with dead letter messages. Messages
can be delivered unsuccessfully (e.g. if the transacted session used to consume them
is rolled back). </para>
<para>Such a message goes back to the JMS destination ready to be redelivered. However,
@@ -111,9 +111,9 @@
instead in a dead letter destination where they can be consumed for further
investigation.</para>
</section>
- <section>
+ <section id="examples.delayed-redelivery">
<title>Delayed Redelivery</title>
- <para>This example demonstrates how JBoss Messaging can be configured to provide a
+ <para>The <literal>delayed-redelivery</literal> example demonstrates how JBoss Messaging can be configured to provide a
delayed redelivery in the case a message needs to be redelivered.</para>
<para>Delaying redelivery can often be useful in the case that clients regularly fail or
roll-back. Without a delayed redelivery, the system can get into a "thrashing"
@@ -129,7 +129,7 @@
</section>
<section>
<title>Durable Subscription</title>
- <para>This example shows you how to use a durable subscription with JBoss Messaging.
+ <para>The <literal>durable-subscription</literal> example shows you how to use a durable subscription with JBoss Messaging.
Durable subscriptions are a standard part of JMS, please consult the JMS 1.1
specification for full details.</para>
<para>Unlike non-durable subscriptions, the key function of durable subscriptions is
@@ -141,12 +141,12 @@
</section>
<section>
<title>Embedded</title>
- <para>This example shows how to embed the JBoss Messaging Server within your own
+ <para>The <literal>embedded</literal> example shows how to embed the JBoss Messaging Server within your own
code.</para>
</section>
<section>
<title>HTTP Transport</title>
- <para>This example shows you how to configure JBoss Messaging to use the HTTP protocol
+ <para>The <literal>http-transport</literal> example shows you how to configure JBoss Messaging to use the HTTP protocol
as its transport layer.</para>
</section>
<section>
@@ -160,25 +160,25 @@
administered objects on the client side so you don't have to use JNDI for
JMS.</para>
</section>
- <section>
+ <section id="examples.interceptor">
<title>Interceptor</title>
<para>JBoss Messaging allows an application to use an interceptor to hook into the
messaging system. Interceptors allow you to handle various message events in JBoss
Messaging.</para>
</section>
- <section>
+ <section id="examples.jaas">
<title>JAAS</title>
- <para>This example shows you how to configure JBoss Messaging to use JAAS for security.
+ <para>The <literal>jaas</literal> example shows you how to configure JBoss Messaging to use JAAS for security.
JBoss Messaging can leverage JAAS to delegate user authentication and authorization
to existing security infrastructure.</para>
</section>
- <section>
+ <section id="examples.jmx">
<title>JMX Management</title>
- <para>This example shows how to manage JBoss Messaging using JMX.</para>
+ <para>The <literal>jmx</literal> example shows how to manage JBoss Messaging using JMX.</para>
</section>
- <section>
+ <section id="examples.large-message">
<title>Large Message</title>
- <para>This example shows you how to send and receive very large messages with JBoss
+ <para>The <literal>large-message</literal> example shows you how to send and receive very large messages with JBoss
Messaging. JBoss Messaging supports the sending and receiving of huge messages, much
larger than can fit in available RAM on the client or server. Effectively the only
limit to message size is the amount of disk space you have on the server.</para>
@@ -186,9 +186,9 @@
In other words JBoss Messaging doesn't just do a simple socket stream from the
sender to the consumer.</para>
</section>
- <section>
+ <section id="examples.last-value-queue">
<title>Last-Value Queue</title>
- <para>This example shows you how to define and deal with last-value queues. Last-Value
+ <para>The <literal>last-value-queue</literal> example shows you how to define and deal with last-value queues. Last-Value
queues are special queues which discard any messages when a newer message with the
same value for a well-defined last-value property is put in the queue. In other
words, a last-value queue only retains the last value.</para>
@@ -197,7 +197,7 @@
</section>
<section>
<title>Load Balanced Clustered Queue</title>
- <para>This example demonstrates a JMS queue deployed on two different nodes. The two
+ <para>The <literal>clustered-queue</literal> example demonstrates a JMS queue deployed on two different nodes. The two
nodes are configured to form a cluster.</para>
<para>We then create a consumer on the queue on each node, and we create a producer on
only one of the nodes. We then send some messages via the producer, and we verify
@@ -205,19 +205,19 @@
<para>In other words, JBoss Messaging load balances the sent messages across all
consumers on the cluster</para>
</section>
- <section>
+ <section id="examples.management">
<title>Management</title>
- <para>This example shows how to manage JBoss Messaging using JMS Messages to invoke
+ <para>The <literal>management</literal> example shows how to manage JBoss Messaging using JMS Messages to invoke
management operations on the server.</para>
</section>
- <section>
+ <section id="examples.management-notifications">
<title>Management Notification</title>
- <para>This example shows how to receive management notifications from JBoss Messaging
+ <para>The <literal>management-notification</literal> example shows how to receive management notifications from JBoss Messaging
using JMS messages. JBoss Messaging servers emit management notifications when
events of interest occur (consumers are created or closed, destinations are created
or deleted, security authentication fails, etc.).</para>
</section>
- <section id="consumer-rate-limiting-example">
+ <section id="examples.consumer-rate-limit">
<title>Message Consumer Rate Limiting</title>
<para>With JBoss Messaging you can specify a maximum consume rate at which a JMS
MessageConsumer will consume messages. This can be specified when creating or
@@ -226,14 +226,14 @@
never consumed at a rate higher than the specified rate. This is a form of consumer
throttling.</para>
</section>
- <section>
+ <section id="examples.message-counters">
<title>Message Counter</title>
- <para>This example shows you how to use message counters to obtain message information
+ <para>The <literal>message-counters</literal> example shows you how to use message counters to obtain message information
for a JMS queue.</para>
</section>
- <section>
+ <section id="examples.expiry">
<title>Message Expiration</title>
- <para>This example shows you how to define and deal with message expiration. Messages
+ <para>The <literal>expiry</literal> example shows you how to define and deal with message expiration. Messages
can be retained in the messaging system for a limited period of time before being
removed. JMS specification states that clients should not receive messages that have
been expired (but it does not guarantee this will not happen).</para>
@@ -242,9 +242,9 @@
destination. These "expired" messages can later be consumed from the expiry
destination for further inspection.</para>
</section>
- <section>
+ <section id="examples.message-group">
<title>Message Group</title>
- <para>This example shows you how to configure and use message groups with JBoss
+ <para>The <literal>message-group</literal> example shows you how to configure and use message groups with JBoss
Messaging. Message groups allow you to pin messages so they are only consumed by a
single consumer. Message groups are sets of messages that has the following
characteristics:</para>
@@ -263,10 +263,10 @@
</section>
<section id="producer-rate-limiting-example">
<title>Message Producer Rate Limiting</title>
- <para>This example demonstrates how, with JBoss Messaging, you can specify a maximum
+ <para>The <literal>producer-rte-limit</literal> example demonstrates how, with JBoss Messaging, you can specify a maximum
send rate at which a JMS message producer will send messages.</para>
</section>
- <section>
+ <section id="examples.message-priority">
<title>Message Priority</title>
<para>Message Priority carries the delivery preference of messages.</para>
<para> It can be retrieved by the message's standard header field 'JMSPriority' as
@@ -281,10 +281,10 @@
</section>
<section>
<title>Message Redistribution</title>
- <para>This example demonstrates message redistribution between queues with the same name
+ <para>The <literal>queue-message-redistribution</literal> example demonstrates message redistribution between queues with the same name
deployed in different nodes of a cluster.</para>
</section>
- <section id="no-consumer-buffering-example">
+ <section id="examples.no-consumer-buffering">
<title>No Consumer Buffering</title>
<para>By default, JBoss Messaging consumers buffer messages from the server in a client
side buffer before you actually receive them on the client side. This improves
@@ -298,14 +298,14 @@
<para>In some case buffering is not desirable, and JBoss Messaging allows it to be
switched off. This example demonstrates that.</para>
</section>
- <section>
+ <section id="examples.paging">
<title>Paging</title>
- <para>This example shows how JBoss Messaging can support huge queues even when the
+ <para>The <literal>paging</literal> example shows how JBoss Messaging can support huge queues even when the
server is running in limited RAM. It does this by transparently
<emphasis>paging</emphasis> messages to disk, and <emphasis>depaging</emphasis>
them when they are required.</para>
</section>
- <section>
+ <section id="examples.pre-acknowledge">
<title>Pre-Acknowledge</title>
<para>Standard JMS supports three acknowledgement modes:<literal>
AUTO_ACKNOWLEDGE</literal>, <literal>CLIENT_ACKNOWLEDGE</literal>, and <literal
@@ -327,48 +327,48 @@
</section>
<section>
<title>Queue with Message Selector</title>
- <para>This example shows you how to selectively consume messages using message selectors
+ <para>The <literal>queue-selector</literal> example shows you how to selectively consume messages using message selectors
with queue consumers.</para>
</section>
<section>
<title>Request-Response</title>
<para>A simple example showing the JMS request-response pattern.</para>
</section>
- <section>
+ <section id="examples.scheduled-message">
<title>Scheduled Message</title>
- <para>This example shows you how to send a scheduled message to a JMS Queue with JBoss
+ <para>The <literal>scheduled-message</literal> example shows you how to send a scheduled message to a JMS Queue with JBoss
Messaging. Scheduled messages won't get delivered until a specified time in the
future.</para>
</section>
<section>
<title>Security</title>
- <para>This example shows you how configure and use role based queue security with JBoss
+ <para>The <literal>security</literal> example shows you how configure and use role based queue security with JBoss
Messaging.</para>
</section>
<section id="asynchronous-send-acknowledgements-example">
<title>Send Acknowledgements</title>
- <para>This example shows you how to use JBoss Messaging's advanced <emphasis>asynchronous send acknowledgements</emphasis> feature to obtain
+ <para>The <literal>send-acknowledgements</literal> example shows you how to use JBoss Messaging's advanced <emphasis>asynchronous send acknowledgements</emphasis> feature to obtain
acknowledgement from the server that sends have been received and processed in a separate stream to the sent messages.
</para>
</section>
<section>
<title>Static Message Selector</title>
- <para>This example shows you how to configure a JBoss Messaging core queue with static
+ <para>The <literal>static-selector</literal> example shows you how to configure a JBoss Messaging core queue with static
message selectors (filters).</para>
</section>
<section>
<title>Static Message Selector Using JMS</title>
- <para>This example shows you how to configure a JBoss Messaging queue with static
+ <para>The <literal>static-selector-jms</literal> example shows you how to configure a JBoss Messaging queue with static
message selectors (filters) using JMS.</para>
</section>
<section>
<title>SSL Transport</title>
- <para>This example shows you how to configure SSL with JBoss Messaging to send and
+ <para>The <literal>ssl-enabled</literal> shows you how to configure SSL with JBoss Messaging to send and
receive message.</para>
</section>
<section>
<title>Symmetric Cluster</title>
- <para>This examples demonstrates a symmetric cluster set-up with JBoss Messaging.</para>
+ <para>The <literal>symmetric-cluster</literal> example demonstrates a symmetric cluster set-up with JBoss Messaging.</para>
<para>JBoss Messaging has extremely flexible clustering which allows you to set-up
servers in many different topologies. The most common topology that you'll perhaps
be familiar with if you are used to application server clustering is a symmetric
@@ -393,38 +393,38 @@
</section>
<section>
<title>Topic Selector 1</title>
- <para>This example shows you how to send message to a JMS Topic, and subscribe them
+ <para>The <literal>topic-selector-example1</literal> example shows you how to send message to a JMS Topic, and subscribe them
using selectors with JBoss Messaging.</para>
</section>
<section>
<title>Topic Selector 2</title>
- <para>This example shows you how to selectively consume messages using message selectors
+ <para>The <literal>topic-selector-example1</literal> example shows you how to selectively consume messages using message selectors
with topic consumers.</para>
</section>
<section>
<title>Transactional Session</title>
- <para>This example shows you how to use a transactional Session with JBoss
+ <para>The <literal>transactional</literal> example shows you how to use a transactional Session with JBoss
Messaging.</para>
</section>
<section>
<title>XA Heuristic</title>
- <para>This example shows you how to make an XA heuristic decision through JBoss
+ <para>The <literal>xa-heuristic</literal> example shows you how to make an XA heuristic decision through JBoss
Messaging Management Interface. A heuristic decision is a unilateral decision to
commit or rollback an XA transaction branch after it has been prepared.</para>
</section>
<section>
<title>XA Receive</title>
- <para>This example shows you how message receiving behaves in an XA transaction in JBoss
+ <para>The <literal>xa-receive</literal> example shows you how message receiving behaves in an XA transaction in JBoss
Messaging.</para>
</section>
<section>
<title>XA Send</title>
- <para>This example shows you how message sending behaves in an XA transaction in JBoss
+ <para>The <literal>xa-send</literal> example shows you how message sending behaves in an XA transaction in JBoss
Messaging.</para>
</section>
<section>
<title>XA with Transaction Manager</title>
- <para>This example shows you how to use JTA interfaces to control transactions with
+ <para>The <literal>xa-with-jta</literal> example shows you how to use JTA interfaces to control transactions with
JBoss Messaging.</para>
</section>
</section>
@@ -432,7 +432,7 @@
<title>Core API Examples</title>
<para>To run a core example, simply <literal>cd</literal> into the appropriate example
directory and type <literal>ant</literal></para>
- <section>
+ <section id="examples.embedded">
<title>Embedded</title>
<para>This example shows how to embed the JBoss Messaging server within your own
code.</para>
Modified: trunk/docs/user-manual/en/flow-control.xml
===================================================================
--- trunk/docs/user-manual/en/flow-control.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/flow-control.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -32,7 +32,7 @@
</listitem>
<listitem>
<para><literal>0</literal> to not buffer any messages. See <xref
- linkend="no-consumer-buffering-example" />
+ linkend="examples.no-consumer-buffering" />
for working example of a consumer with no buffering.</para>
</listitem>
<listitem>
@@ -101,11 +101,7 @@
<para>If the connection factory is directly instantiated, the consumer window size is
specified by <literal>JBossConnectionFactory.setConsumerWindowSize()</literal>
method.</para>
- </section>
- <section>
- <title>Example</title>
- <para>The <ulink url="../../../../examples/jms/no-consumer-buffering/readme.html">
- <literal>no-consumer-buffering</literal> example</ulink> shows how to configure
+ <para>Please see <xref linkend="examples.no-consumer-buffering" /> for an example which shows how to configure
JBoss Messaging to prevent consumer buffering when dealing with slow
consumers.</para>
</section>
@@ -119,7 +115,7 @@
consumption rate specified in units of messages per second. Setting this to <literal
>-1</literal> disables rate limited flow control. The default value is <literal
>-1</literal>.</para>
- <para>Please see <xref linkend="consumer-rate-limiting-example" /> for a working example
+ <para>Please see <xref linkend="examples.consumer-rate-limit" /> for a working example
of limiting consumer rate.</para>
<section id="flow-control.rate.core.api">
<title>Using Core API</title>
@@ -152,12 +148,8 @@
slow rate limit and a high window based limit the clients internal buffer would
soon fill up with messages.</para>
</note>
- </section>
- <section>
- <title>Example</title>
- <para>The <ulink url="../../../../examples/jms/consumer-rate-limit/readme.html">
- <literal>consumer-rate-limit</literal> example</ulink> shows how to configure
- JBoss Messaging to prevent consumer buffering when dealing with slow
+ <para>Please see <xref linkend="examples.consumer-rate-limit" /> for an example which shows
+ how to configure JBoss Messaging to prevent consumer buffering when dealing with slow
consumers.</para>
</section>
</section>
Modified: trunk/docs/user-manual/en/intercepting-operations.xml
===================================================================
--- trunk/docs/user-manual/en/intercepting-operations.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/intercepting-operations.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -43,8 +43,7 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/interceptor/readme.html"><literal
- >interceptor</literal> example</ulink> shows how to use interceptors to add
- properties to a message on the server.</para>
+ <para>See <xref linkend="examples.interceptor" /> for an example which
+ shows how to use interceptors to add properties to a message on the server.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/large-messages.xml
===================================================================
--- trunk/docs/user-manual/en/large-messages.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/large-messages.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -256,8 +256,7 @@
</section>
<section id="large-messages.example">
<title>Large message example</title>
- <para>The <ulink url="../../../../examples/jms/large-message/readme.html"><literal
- >large-message</literal> Example</ulink> shows how large message is configured
- and used with JMS.</para>
+ <para>Please see <xref linkend="examples.large-message" /> for an example which
+ shows how large message is configured and used with JMS.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/last-value-queues.xml
===================================================================
--- trunk/docs/user-manual/en/last-value-queues.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/last-value-queues.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -48,8 +48,7 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/last-value-queue/readme.html"><literal
- >last-value-queue</literal> example</ulink> shows how last value queues are
- configured and used with JMS.</para>
+ <para>See <xref linkend="examples.last-value-queue" /> for an example which
+ shows how last value queues are configured and used with JMS.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/management.xml
===================================================================
--- trunk/docs/user-manual/en/management.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/management.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -478,8 +478,8 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/jmx/readme.html"><literal>jmx</literal>
- example</ulink> shows how to use a remote connection to JMX and MBean proxies to
+ <para>See <xref linkend="examples.jmx" /> for an example which
+ shows how to use a remote connection to JMX and MBean proxies to
manage JBoss Messaging.</para>
</section>
</section>
@@ -627,9 +627,8 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/management/readme.html"><literal
- >management</literal> example</ulink> shows how to use JMS messages to manage
- JBoss Messaging server.</para>
+ <para>See <xref linkend="examples.management" /> for an example which shows how to use
+ JMS messages to manage JBoss Messaging server.</para>
</section>
</section>
<section id="management.replication">
@@ -764,8 +763,8 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/management-notifications/readme.html"
- ><literal>management-notifications</literal> example</ulink> shows how to use a
+ <para>See <xref linkend="examples.management-notifications" /> for an example which
+ shows how to use a
JMS <literal>MessageListener</literal> to receive management notifications from JBoss
Messaging server.</para>
</section>
@@ -854,8 +853,8 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/message-counters/readme.html"><literal
- >message-counters</literal> example</ulink> shows how to use message counters to
+ <para>See <xref linkend="examples.message-counters" /> for an example which
+ shows how to use message counters to
retrieve information on a JMS <literal>Queue</literal>.</para>
</section>
</section>
Modified: trunk/docs/user-manual/en/message-expiry.xml
===================================================================
--- trunk/docs/user-manual/en/message-expiry.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/message-expiry.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -70,7 +70,7 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/expiry/readme.html"><literal>expiry</literal>
- example</ulink> shows how message expiry is configured and used with JMS.</para>
+ <para>See <xref linkend="examples.expiry" /> for an example which
+ shows how message expiry is configured and used with JMS.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/message-grouping.xml
===================================================================
--- trunk/docs/user-manual/en/message-grouping.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/message-grouping.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -71,8 +71,7 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/message-group/readme.html"><literal
- >message-group</literal> example</ulink> shows how message groups are configured and
- used with JMS.</para>
+ <para>See <xref linkend="examples.message-group" /> for an example which
+ shows how message groups are configured and used with JMS.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/paging.xml
===================================================================
--- trunk/docs/user-manual/en/paging.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/paging.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -165,8 +165,8 @@
messages.</para>
</section>
<section>
- <title>Paging Example</title>
- <para>The <ulink url="../../../../examples/jms/paging/readme.html"><literal>Paging</literal>
- Example</ulink> shows how to use paging with JBoss Messaging.</para>
+ <title>Example</title>
+ <para>See <xref linkend="examples.paging" /> for an example which
+ shows how to use paging with JBoss Messaging.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/pre-acknowledge.xml
===================================================================
--- trunk/docs/user-manual/en/pre-acknowledge.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/pre-acknowledge.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -50,8 +50,7 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/pre-acknowledge/readme.html"><literal
- >pre-acknowledge</literal> example</ulink> shows how to use pre-acknowledgement mode
- with with JMS.</para>
+ <para>See <xref linkend="examples.pre-acknowledge" /> for an example which
+ shows how to use pre-acknowledgement mode with with JMS.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/scheduled-messages.xml
===================================================================
--- trunk/docs/user-manual/en/scheduled-messages.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/scheduled-messages.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -28,8 +28,7 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/scheduled-message/readme.html"><literal
- >scheduled-message</literal> example</ulink> shows how scheduled messages can be used
- with JMS.</para>
+ <para>See <xref linkend="examples.scheduled-message" /> for an example which
+ shows how scheduled messages can be used with JMS.</para>
</section>
</chapter>
Modified: trunk/docs/user-manual/en/security.xml
===================================================================
--- trunk/docs/user-manual/en/security.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/security.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -230,8 +230,8 @@
</itemizedlist>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/jaas/readme.html"><literal>jaas</literal>
- example</ulink> shows how JBoss Messaging can be configured to use JAAS.</para>
+ <para>See <xref linkend="examples.jaas" /> for an example which
+ shows how JBoss Messaging can be configured to use JAAS.</para>
</section>
</section>
<section>
Modified: trunk/docs/user-manual/en/undelivered-messages.xml
===================================================================
--- trunk/docs/user-manual/en/undelivered-messages.xml 2009-05-26 10:00:40 UTC (rev 7012)
+++ trunk/docs/user-manual/en/undelivered-messages.xml 2009-05-26 10:14:12 UTC (rev 7013)
@@ -44,9 +44,8 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/delayed-redelivery/readme.html"><literal
- >delayed-redelivery</literal> example</ulink> shows how delayed redelivery is
- configured and used with JMS.</para>
+ <para>See <xref linkend="examples.delayed-redelivery" /> for an example which
+ shows how delayed redelivery is configured and used with JMS.</para>
</section>
</section>
<section>
@@ -97,9 +96,8 @@
</section>
<section>
<title>Example</title>
- <para>The <ulink url="../../../../examples/jms/dead-letter/readme.html"><literal
- >dead-letter</literal> example</ulink> shows how dead letter is configured and
- used with JMS.</para>
+ <para>See <xref linkend="examples.dead-letter" /> for an example which
+ shows how dead letter is configured and used with JMS.</para>
</section>
</section>
<section id="configuring.delivery.count.persistence">
More information about the jboss-cvs-commits
mailing list