[seam-commits] Seam SVN: r11662 - tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US.

[seam-commits at lists.jboss.org]

Author: laubai
Date: 2009-11-23 23:46:42 -0500 (Mon, 23 Nov 2009)
New Revision: 11662

Modified:
   tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jbpm.xml
Log:
Edited jbpm chapter.

Modified: tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jbpm.xml
===================================================================
--- tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jbpm.xml	2009-11-24 04:28:32 UTC (rev 11661)
+++ tags/JBPAPP_4_3_CP07_FP_CR1a/doc/Seam_Reference_Guide/en-US/Jbpm.xml	2009-11-24 04:46:42 UTC (rev 11662)
@@ -5,7 +5,7 @@
         JBoss jBPM is a business process management engine for any Java SE or EE
         environment. jBPM lets you represent a business process or user 
         interaction as a graph of nodes representing wait states, decisions,
-        tasks, web pages, etc. The graph is defined using a simple, very readable, 
+        tasks, web pages, etc. The graph is defined using a simple, very readable
         XML dialect called jPDL, and may be edited and visualised graphically using
         an eclipse plugin. jPDL is an extensible language, and is suitable for 
         a range of problems, from defining web application page flow, to traditional
@@ -40,11 +40,11 @@
     </itemizedlist>
     
     <para>
-        Don't get these two things confused ! They operate at very different levels
+        These two definitions operate at very different levels
         or granularity. <emphasis>Pageflow</emphasis>, <emphasis>conversation</emphasis>
         and <emphasis>task</emphasis> all refer to a single
         interaction with a single user. A business process spans many tasks.
-        Futhermore, the two applications of jBPM are totally orthogonal. You can
+        Furthermore, the two applications of jBPM are totally orthogonal. You can
         use them together or independently or not at all.
     </para>
     
@@ -145,7 +145,7 @@
 </page>]]></programlisting>
 
         <para>
-            If you find navigation rules overly verbose, you can return view ids
+            If you find navigation rules overly verbose, you can return view IDs
             directly from your action listener methods:
         </para>
         
@@ -242,7 +242,7 @@
 	        constrained set of possible transitions to other states. The stateless
 	        model is an <emphasis>ad hoc</emphasis> model which is suitable to 
 	        relatively unconstrained, freeform navigation where the user decides
-	        where he/she wants to go next, not the application.
+	        where they want to go next, not the application.
 	    </para>
 	    
 	    <para>
@@ -391,7 +391,7 @@
         <programlisting role="JAVA"><![CDATA[@Begin(pageflow="numberguess")
 public void begin() { ... }]]></programlisting>
 
-		<para>Alternatively we can start a pageflow using pages.xml:</para>
+		<para>Alternatively we can start a pageflow using <filename>pages.xml</filename>:</para>
 		
 		<programlisting role="XML"><![CDATA[<page>
         <begin-conversation pageflow="numberguess"/>
@@ -400,7 +400,7 @@
         <para>
             If we are beginning the pageflow during the <literal>RENDER_RESPONSE</literal>
             phase&#8212;during a <literal>@Factory</literal> or <literal>@Create</literal>
-            method, for example&#8212;we consider ourselves to be already at the page being 
+            method, for example &#8212; we consider ourselves to be already at the page being 
             rendered, and use  a <literal>&lt;start-page&gt;</literal> node as the first node 
             in the pageflow, as in the example above.
         </para>
@@ -565,7 +565,7 @@
         <section>
             <title>Pageflow composition</title>
             <para>
-                It is possible to compose pageflows and have one pageflow pause 
+                It is possible to compose pageflows and have one pageflow  
                 pause while another pageflow executes. The <literal>&lt;process-state&gt;</literal>
                 node pauses the outer pageflow, and begins execution of a named 
                 pageflow:
@@ -669,7 +669,7 @@
             As jBPM processes are persistent across application restarts, 
             when using Seam in a production environment you won't want to
             install the process definition every time the application starts.
-            Therefore, in a production environment, you'll need to deploy
+            Therefore, in a production environment, you will need to deploy
             the process to jBPM outside of Seam. In other words, only install
             process definitions from <literal>components.xml</literal> when
             developing your application.
@@ -710,7 +710,7 @@
         <programlisting role="JAVA"><![CDATA[@CreateProcess(definition="todo")
 public void createTodo() { ... }]]></programlisting>
 
-        <para>Alternatively we can initiate a business process using pages.xml:</para>
+        <para>Alternatively we can initiate a business process using <filename>pages.xml</filename>:</para>
         
         <programlisting role="XML"><![CDATA[<page>
     <create-process definition="todo" />
@@ -803,7 +803,7 @@
         <programlisting role="JAVA"><![CDATA[@StartTask
 public String start() { ... }]]></programlisting>
 
-        <para>Alternatively we can begin work on a task using pages.xml:</para>
+        <para>Alternatively we can begin work on a task using <filename>pages.xml</filename>:</para>
         
         <programlisting role="XML"><![CDATA[<page>
     <start-task />
@@ -824,7 +824,7 @@
         <programlisting role="JAVA"><![CDATA[@EndTask(transition="completed")
 public String completed() { ... }]]></programlisting>
 
-        <para>Alternatively we can use pages.xml:</para>
+        <para>Alternatively we can use <filename>pages.xml</filename>:</para>
         
         <programlisting role="XML"><![CDATA[<page>
     <end-task transition="completed" />