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

[Gavin King]

  User: gavin   
  Date: 06/07/14 14:34:40

  Modified:    doc/reference/en/modules  jbpm.xml
  Log:
  doc no-conversation-view-id
  
  Revision  Changes    Path
  1.21      +32 -2     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.20
  retrieving revision 1.21
  diff -u -b -r1.20 -r1.21
  --- jbpm.xml	10 Jun 2006 22:24:11 -0000	1.20
  +++ jbpm.xml	14 Jul 2006 18:34:40 -0000	1.21
  @@ -260,12 +260,23 @@
   	        the context of Seam, where there is a well-defined conversational
   	        model, backed by stateful session beans, it is actually quite 
   	        straightforward. Usually it is as simple as combining the use 
  -	        of the <literal>@Conversational</literal> annotation with null 
  +	        of <literal>no-conversation-view-id</literal> with null 
   	        checks at the beginning of action listener methods. We consider
   	        support for freeform navigation to be almost always desirable.
   	    </para>
   	    
   	    <para>
  +	        In this case, the <literal>no-conversation-view-id</literal> 
  +	        declaration goes in <literal>pages.xml</literal>. It tells
  +	        Seam to redirect to a different page if a request originates
  +	        from a page rendered during a conversation, and that conversation
  +	        no longer exists:
  +	    </para>
  +	    
  +	    <programlisting><![CDATA[<page view-id="/checkout.xhtml" 
  +        no-conversation-view-id="/main.xhtml"/>]]></programlisting>
  +	    
  +	    <para>
   	        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
  @@ -281,7 +292,9 @@
   	        setting <literal>back="enabled"</literal>.
   	    </para>
   	    
  -<programlisting><![CDATA[<page name="checkout" view-id="/checkout.xhtml" back="enabled">
  +        <programlisting><![CDATA[<page name="checkout" 
  +        view-id="/checkout.xhtml" 
  +        back="enabled">
       <redirect/>
       <transition to="checkout"/>
       <transition name="complete" to="complete"/>
  @@ -293,6 +306,23 @@
               state!</emphasis>
           </para>
   
  +        <para>
  +            Of course, we still need to define what happens if a request 
  +            originates from a page rendered during a pageflow, and the
  +            conversation with the pageflow no longer exists. In this case,
  +            the <literal>no-conversation-view-id</literal> declaration
  +            goes into the pageflow definition:
  +        </para>
  +
  +        <programlisting><![CDATA[<page name="checkout" 
  +        view-id="/checkout.xhtml" 
  +        back="enabled" 
  +        no-conversation-view-id="/main.xhtml">
  +    <redirect/>
  +    <transition to="checkout"/>
  +    <transition name="complete" to="complete"/>
  +</page>]]></programlisting>
  +
           </section>
       
   	    <para>