[jboss-cvs] JBoss Messaging SVN: r6960 - trunk/docs/user-manual/en.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu May 21 06:57:20 EDT 2009
Author: ataylor
Date: 2009-05-21 06:57:20 -0400 (Thu, 21 May 2009)
New Revision: 6960
Modified:
trunk/docs/user-manual/en/using-core.xml
Log:
more proof reading changes
Modified: trunk/docs/user-manual/en/using-core.xml
===================================================================
--- trunk/docs/user-manual/en/using-core.xml 2009-05-21 10:49:32 UTC (rev 6959)
+++ trunk/docs/user-manual/en/using-core.xml 2009-05-21 10:57:20 UTC (rev 6960)
@@ -20,14 +20,13 @@
values can be of type integer, long, short, byte, byte[], String, double, float or
boolean.</para>
<para>A message has a destination which represents the <emphasis>address</emphasis> it
- is being sent to. When the message arrives on the server the server route the
- message to zero or more queues depending on the address. Many queues can be bound to
- a particular address on the server. The server will route the message to all queues
- bound to that address.</para>
- <para>Messages can durable or non durable. Durable messages in a durable queue will
- survive a server crash or restart. Non durable messages will never survive a server
- crash or restart.</para>
- <para>Messages can be specified with a priority value betwen 0 and 9. 0 represents the
+ is being sent to. When the message arrives on the server it is routed to any queues
+ that are bound to the address. An address may have many queues bound to it or even
+ none.</para>
+ <para>Messages can either be durable or non durable. Durable messages in a durable queue
+ will survive a server crash or restart. Non durable messages will never survive a
+ server crash or restart.</para>
+ <para>Messages can be specified with a priority value betwen 0 and 9. 0 represents the
highest priority and 9 represents the lowest. JBoss Messaging will attempt to
deliver higher priority messages before lower priority ones.</para>
<para>Messages can be specified with an optional expiry time. JBoss Messaging will not
@@ -43,19 +42,22 @@
queues bound to the message's destination address. If any of the queues are bound
with a filter expression, then the message will only be routed to the subset of
bound queues which match that filter expression.</para>
- <para>Note that, in core, there is no concept of a Topic, Topic is a JMS only term.
- Instead, in core, we just deal with <emphasis>addresses</emphasis> and
- <emphasis>queues</emphasis>.</para>
- <para>For example, a JMS topic would implemented by a single address to which many
- queues are bound. Each queue represents a subscription of the topic. A JMS Queue
- would be implemented as a single address to which one queue is bound - that queue
- represents the JMS queue.</para>
+ <note>
+ <para>In core, there is no concept of a Topic, Topic is a JMS only term. Instead, in
+ core, we just deal with <emphasis>addresses</emphasis> and
+ <emphasis>queues</emphasis>.</para>
+ <para>For example, a JMS topic would implemented by a single address to which many
+ queues are bound. Each queue represents a subscription of the topic. A JMS Queue
+ would be implemented as a single address to which one queue is bound - that
+ queue represents the JMS queue.</para>
+ </note>
</section>
<section>
<title>Queue</title>
- <para>Queues can de durable, meaning they survive a server crash or restart, as long as
- the messages in them are durable. Non durable queues do not survive a server restart
- or crash even if the messages they contain are durable.</para>
+ <para>Queues can be durable, meaning the messages they contain survive a server crash or
+ restart, as long as the messages in them are durable. Non durable queues do not
+ survive a server restart or crash even if the messages they contain are
+ durable.</para>
<para>Queues can also be temporary, meaning they are automatically deleted when the
client connection is closed, if they are not explicitly deleted before that.</para>
<para>Queues can be bound with an optional filter expression. If a filter expression is
@@ -66,17 +68,18 @@
</section>
<section>
<title>ClientSessionFactory</title>
- <para>Clients use <literal>ClientSessionFactory</literal> instances to create <literal
- >ClientSession</literal> instances. <literal>ClientSessionFactory</literal>
- instances know how to connect to the server to create sessions.</para>
+ <para>Clients use <literal>ClientSessionFactory</literal> instances to create
+ <literal>ClientSession</literal> instances.
+ <literal>ClientSessionFactory</literal> instances know how to connect to the
+ server to create sessions.</para>
</section>
<section>
<title>ClientSession</title>
<para>A client uses a ClientSession for consuming and producing messages and for
grouping them in transactions. ClientSession instances can support both
- transactional and non transactional semantics and also provide an <literal
- >XAResource</literal> interface so messaging operations can be performed as part
- of a JTA transaction.</para>
+ transactional and non transactional semantics and also provide an
+ <literal>XAResource</literal> interface so messaging operations can be performed
+ as part of a JTA transaction.</para>
<para>ClientSession instances group ClientConsumers and ClientProducers.</para>
</section>
<section>
@@ -89,11 +92,11 @@
</section>
<section>
<title>ClientProducer</title>
- <para>Clients create <literal>ClientProducer</literal> instances on <literal
- >ClientSession</literal> instances so they can send messages. ClientProducer
- instances can specify an address to which all sent messages are routed, or they can
- have no specified address, and the address is specified at send time for the
- message.</para>
+ <para>Clients create <literal>ClientProducer</literal> instances on
+ <literal>ClientSession</literal> instances so they can send messages.
+ ClientProducer instances can specify an address to which all sent messages are
+ routed, or they can have no specified address, and the address is specified at send
+ time for the message.</para>
</section>
</section>
<section>
More information about the jboss-cvs-commits
mailing list