[seam-commits] Seam SVN: r9912 - trunk/doc/Seam_Reference_Guide/en-US.

Author: nico.ben Date: 2009-01-11 12:46:16 -0500 (Sun, 11 Jan 2009) New Revision: 9912 Modified: trunk/doc/Seam_Reference_Guide/en-US/Jms.xml Log: Corrected errors Modified: trunk/doc/Seam_Reference_Guide/en-US/Jms.xml =================================================================== --- trunk/doc/Seam_Reference_Guide/en-US/Jms.xml 2009-01-10 20:47:47 UTC (rev 9911) +++ trunk/doc/Seam_Reference_Guide/en-US/Jms.xml 2009-01-11 17:46:16 UTC (rev 9912) @@ -4,12 +4,12 @@ Seam makes it very easy to perform work asynchronously from a web request. When most people think of asynchronicity in Java EE, they think of using JMS. This is certainly one way to approach the problem in Seam, and is the right way when you have strict and well-defined - quality of service requirements. Seam makes it easy to send and recieve JMS messages using + quality of service requirements. Seam makes it easy to send and receive JMS messages using Seam components. </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> @@ -394,7 +394,7 @@ <para> Here, for example, using <literal>java.util.concurrent</literal> - dispatcher, we inject it's control object and cancel all future + dispatcher, we inject its control object and cancel all future invocations when an exception is encountered </para>