[jboss-cvs] JBoss Messaging SVN: r6827 - trunk/docs/user-manual/en/modules.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Mon May 18 04:42:11 EDT 2009
Author: jmesnil
Date: 2009-05-18 04:42:11 -0400 (Mon, 18 May 2009)
New Revision: 6827
Modified:
trunk/docs/user-manual/en/modules/message-expiry.xml
trunk/docs/user-manual/en/modules/message-grouping.xml
Log:
user manual
described Core API before JMS
Modified: trunk/docs/user-manual/en/modules/message-expiry.xml
===================================================================
--- trunk/docs/user-manual/en/modules/message-expiry.xml 2009-05-18 08:35:15 UTC (rev 6826)
+++ trunk/docs/user-manual/en/modules/message-expiry.xml 2009-05-18 08:42:11 UTC (rev 6827)
@@ -9,17 +9,17 @@
<emphasis>expired</emphasis> messages can later be consumed for further inspection.</para>
<section>
<title>Message Expiry</title>
+ <para>Using JBoss Messaging Core API, you can set an expiration time directly on the
+ message:</para>
+ <programlisting>
+ // message will expire in 5000ms from now
+ message.setExpiration(System.currentTimeMillis() + 5000);
+ </programlisting>
<para>JMS MessageProducer allows to set a TimeToLive for the messages it sent:</para>
<programlisting>
// messages sent by this producer will be retained for 5s (5000ms) before expiration
producer.setTimeToLive(5000);
</programlisting>
- <para>Using JBoss Messaging Core API, you can set an expiration time directly on the
- message:</para>
- <programlisting>
-// message will expire in 5000ms from now
-message.setExpiration(System.currentTimeMillis() + 5000);
- </programlisting>
<para>Expired messages which are consumed from an expiry address have the following properties:</para>
<itemizedlist>
<listitem>
Modified: trunk/docs/user-manual/en/modules/message-grouping.xml
===================================================================
--- trunk/docs/user-manual/en/modules/message-grouping.xml 2009-05-18 08:35:15 UTC (rev 6826)
+++ trunk/docs/user-manual/en/modules/message-grouping.xml 2009-05-18 08:42:11 UTC (rev 6827)
@@ -25,8 +25,14 @@
</section>
<section>
- <title>Using JMSX Group properties</title>
- <para>Using JMS, the property name used to identify the message group is <literal>JMSXGroupID</literal>.</para>
+ <title>Using Core API</title>
+ <para>The property name used to identify the message group is <literal>"_JBM_GROUP_ID""</literal>
+ (or the constant <literal>MessageImpl.HDR_GROUP_ID</literal>).</para>
+ </section>
+
+ <section>
+ <title>Using JMS</title>
+ <para>The property name used to identify the message group is <literal>JMSXGroupID</literal>.</para>
<para>Within the same group, messages can also set a <literal>JMSXGroupSeq</literal>
<literal>int</literal> property (starting at 1).</para>
<programlisting>
@@ -45,12 +51,6 @@
</section>
<section>
- <title>Using JBoss Messaging Core Group properties</title>
- <para>Using JBoss Messaging Core API, the property name used to identify the message group is <literal>"_JBM_GROUP_ID""</literal>
- (or the constant <literal>MessageImpl.HDR_GROUP_ID</literal>).</para>
- </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>
More information about the jboss-cvs-commits
mailing list