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

[Gavin King]

  User: gavin   
  Date: 07/06/26 21:41:39

  Modified:    doc/reference/en/modules  jbpm.xml
  Log:
  doc pageflow composition
  
  Revision  Changes    Path
  1.34      +25 -1     jboss-seam/doc/reference/en/modules/jbpm.xml
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: jbpm.xml
  ===================================================================
  RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/jbpm.xml,v
  retrieving revision 1.33
  retrieving revision 1.34
  diff -u -b -r1.33 -r1.34
  --- jbpm.xml	26 Jun 2007 02:23:11 -0000	1.33
  +++ jbpm.xml	27 Jun 2007 01:41:39 -0000	1.34
  @@ -301,7 +301,7 @@
   	        On the other hand, in the stateful model, backbuttoning is 
   	        interpreted as an undefined transition back to a previous state.
   	        Since the stateful model enforces a defined set of transitions
  -	        from the current state, back buttoning is be default disallowed 
  +	        from the current state, back buttoning is by default disallowed 
   	        in the stateful model! Seam transparently detects the use of the
   	        back button, and blocks any attempt to perform an action from
   	        a previous, "stale" page, and simply redirects the user to 
  @@ -563,6 +563,30 @@
   
           </section>
   
  +        <section>
  +            <title>Pageflow composition</title>
  +            <para>
  +                It is possible to compose pageflows and have one pageflow pause 
  +                pause while another pageflow executes. The <literal>&lt;process-state&gt;</literal>
  +                node pauses the outer pageflow, and begins execution of a named 
  +                pageflow:
  +            </para>
  +            
  +<programlisting><![CDATA[<process-state name="cheat">
  +    <sub-process name="cheat"/>
  +    <transition to="displayGuess"/>
  +</process-state>]]></programlisting>
  +
  +            <para>
  +                The inner flow begins executing at a <literal>&lt;start-state&gt;</literal>
  +                node. When it reaches an <literal>&lt;end-state&gt;</literal> node, 
  +                execution of the inner flow ends, and execution of the outer flow
  +                resumes with the transition defined by the <literal>&lt;process-state&gt;</literal>
  +                element.
  +            </para>
  +            
  +        </section>
  +
       </section>
       
       <section>