Author: laubai
Date: 2009-11-23 23:55:22 -0500 (Mon, 23 Nov 2009)
New Revision: 11663
Modified:
tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml
Log:
Edited JMS chapter.
Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml 2009-11-24
04:46:42 UTC (rev 11662)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jms.xml 2009-11-24
04:55:22 UTC (rev 11663)
@@ -9,7 +9,7 @@
</para>
<para>
- But for many usecases, JMS is overkill. Seam layers a simple asynchronous method
and event
+ But for many use cases, JMS is overkill. Seam layers a simple asynchronous method
and event
facility over your choice of <emphasis>dispatchers</emphasis>:
</para>
@@ -46,8 +46,8 @@
<programlisting
role="XML"><![CDATA[<async:timer-service-dispatcher/>]]></programlisting>
<para>
- then your asynchronous tasks will be processed by the container's EJB
timer service. If
- you're not familiar with the Timer service, don't worry, you
don't need to interact with
+ Your asynchronous tasks will be processed by the container's EJB timer
service. If
+ you are not familiar with the Timer service, don't worry, you don't
need to interact with
it directly if you want to use asynchronous methods in Seam. The important
thing to know
is that any good EJB 3.0 implementation will have the option of using
persistent timers,
which gives some guarantee that the tasks will eventually be processed.
@@ -250,7 +250,7 @@
processor.schedulePayment(new Date(), 60*60*1000, cal.getTime(), payment);
]]></programlisting>
- <para>Note that the method returns the
<literal>QuartzTriggerHandle</literal> object, which you can use later to
stop, pause, and resume the scheduler. The
<literal>QuartzTriggerHandle</literal> object is serializable, so you can save
it into the database if you need to keep it around for extended period of
time.</para>
+ <para>Note that the method returns the
<literal>QuartzTriggerHandle</literal> object, which you can use later to
stop, pause, and resume the scheduler. The
<literal>QuartzTriggerHandle</literal> object is serializable, so you can save
it into the database if you need to keep it around for an extended period of
time.</para>
<programlisting role="JAVA"><![CDATA[QuartzTriggerHandle
handle =
processor.schedulePayment(payment.getPaymentDate(),
@@ -286,7 +286,7 @@
processor.schedulePayment(new Date(), "0 10,44 14 ? 3 WED", payment);
]]></programlisting>
- <para>The <literal>@IntervalBusinessDay</literal> annotation
supports invocation on the "nth Business Day" scenario. For instance, the
following asynchronous method runs at 14:00 on the 2nd business day of each month. By
default, it excludes all weekends and US federal holidays until 2010 from the business
days.
+ <para>The <literal>@IntervalBusinessDay</literal> annotation
supports invocation on the "nth Business Day" scenario. For instance, the
following asynchronous method runs at 14:00 on the second business day of each month. By
default, it excludes all weekends and US federal holidays until 2010 from the business
days.
</para>
<programlisting role="JAVA"><![CDATA[
@@ -307,7 +307,7 @@
new NthBusinessDay(2, "14:00", WEEKLY), payment);
]]></programlisting>
- <para>The <literal>NthBusinessDay</literal> object contains the
configuration of the invocation trigger. You can specify more holidays (e.g., company
holidays, non-US holidays etc.) via the <literal>additionalHolidays</literal>
property.</para>
+ <para>The <literal>NthBusinessDay</literal> object contains the
configuration of the invocation trigger. You can specify more holidays (for example,
company holidays, non-US holidays etc.) via the
<literal>additionalHolidays</literal> property.</para>
<programlisting role="JAVA"><![CDATA[
public class NthBusinessDay implements Serializable
Show replies by date