[jboss-cvs] jboss-seam/doc/reference/en/modules ...

[Gavin King]

  User: gavin   
  Date: 07/06/19 23:26:56

  Modified:    doc/reference/en/modules   components.xml jms.xml
  Log:
  update
  
  Revision  Changes    Path
  1.60      +1 -1      jboss-seam/doc/reference/en/modules/components.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: components.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/components.xml,v
  retrieving revision 1.59
  retrieving revision 1.60
  diff -u -b -r1.59 -r1.60
  --- components.xml	15 Jun 2007 07:36:20 -0000	1.59
  +++ components.xml	20 Jun 2007 03:26:56 -0000	1.60
  @@ -1346,7 +1346,7 @@
           
           <variablelist>
               <varlistentry>
  -                <term><literal>org.jboss.seam.core.dispatcher</literal></term>
  +                <term><literal>org.jboss.seam.async.dispatcher</literal></term>
                   <listitem>
                       <para>
                           Dispatcher stateless session bean for asynchronous methods.
  
  
  
  1.17      +12 -7     jboss-seam/doc/reference/en/modules/jms.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: jms.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/jms.xml,v
  retrieving revision 1.16
  retrieving revision 1.17
  diff -u -b -r1.16 -r1.17
  --- jms.xml	12 Jun 2007 16:00:53 -0000	1.16
  +++ jms.xml	20 Jun 2007 03:26:56 -0000	1.17
  @@ -43,7 +43,7 @@
               EJB 3.0, and add the following line to <literal>components.xml</literal>:
           </para>
           
  -        <programlisting><![CDATA[<core:timer-service-dispatcher/>]]></programlisting>
  +        <programlisting><![CDATA[<async:timer-service-dispatcher/>]]></programlisting>
           
           <para>
               then your asynchronous tasks will be processed by the container's EJB timer service. If 
  @@ -54,14 +54,19 @@
           </para>
           
           <para>
  -            Another alternative is to use the open source Quartz library to manage asynchronous method. You need to bundle the Quartz library JAR (found in the <literal>lib</literal> directory) in your EAR and declare it as a Java module in <literal>application.xml</literal>. In addition, you need to add the following line to <literal>components.xml</literal> to install the Quartz dispatcher.
  +            Another alternative is to use the open source Quartz library to manage asynchronous method. 
  +            You need to bundle the Quartz library JAR (found in the <literal>lib</literal> directory) 
  +            in your EAR and declare it as a Java module in <literal>application.xml</literal>. In addition, 
  +            you need to add the following line to <literal>components.xml</literal> to install the Quartz 
  +            dispatcher.
           </para>
           
  -        <programlisting><![CDATA[<component name="org.jboss.seam.core.dispatcher" 
  -        class="org.jboss.seam.core.QuartzDispatcher"/>]]></programlisting>
  +        <programlisting><![CDATA[<async:quartz-dispatcher/>]]></programlisting>
               
           <para>
  -            The Seam API for the default <literal>ScheduledThreadPoolExecutor</literal>, the EJB3 <literal>Timer</literal>, and the Quartz <literal>Scheduler</literal> are largely the same. They can just "plug and play" by adding a line to <literal>components.xml</literal> as we shown above.
  +            The Seam API for the default <literal>ScheduledThreadPoolExecutor</literal>, the EJB3 
  +            <literal>Timer</literal>, and the Quartz <literal>Scheduler</literal> are largely the 
  +            same. They can just "plug and play" by adding a line to <literal>components.xml</literal>.
           </para>
           
           <sect2>