[seam-commits] Seam SVN: r11725 - branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US.

seam-commits at lists.jboss.org seam-commits at lists.jboss.org
Fri Dec 4 03:17:36 EST 2009


Author: laubai
Date: 2009-12-04 03:17:36 -0500 (Fri, 04 Dec 2009)
New Revision: 11725

Modified:
   branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Conversations.xml
   branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Events.xml
   branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Groovy.xml
   branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Tutorial.xml
Log:
Removed TODO items.

Modified: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Conversations.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Conversations.xml	2009-12-04 07:54:45 UTC (rev 11724)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Conversations.xml	2009-12-04 08:17:36 UTC (rev 11725)
@@ -260,10 +260,10 @@
             workspace management.
         </para>
         
-        <para>
+        <!--<para>
             TODO: an example to show how a nested conversation prevents bad 
             stuff happening when you backbutton.
-        </para>
+        </para>-->
         
         <para>
             Usually, if a component exists in a parent conversation of the 

Modified: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Events.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Events.xml	2009-12-04 07:54:45 UTC (rev 11724)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Events.xml	2009-12-04 08:17:36 UTC (rev 11725)
@@ -105,13 +105,13 @@
             Furthermore, the view id mentioned in the <literal>&lt;page&gt;</literal>
             element need not correspond to a real JSP or Facelets page! So, we can
             reproduce the functionality of a traditional action-oriented framework
-            like Struts or WebWork using page actions. For example:
+            like Struts or WebWork using page actions. <!--For example:
         </para> 
         
         <programlisting><![CDATA[TODO: translate struts action into page action]]></programlisting>
 
 
-        <para>
+        <para>-->
             This is quite useful if you want to do complex things in response to non-faces
             requests (for example, HTTP GET requests).
         </para>

Modified: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Groovy.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Groovy.xml	2009-12-04 07:54:45 UTC (rev 11724)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Groovy.xml	2009-12-04 08:17:36 UTC (rev 11725)
@@ -41,7 +41,7 @@
             </listitem>
         </itemizedlist>
 
-        <para>TODO: write a quick overview of the Groovy syntax add-on</para>
+        <!--<para>TODO: write a quick overview of the Groovy syntax add-on</para>-->
     </section>
 
     <section>

Modified: branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Tutorial.xml	2009-12-04 07:54:45 UTC (rev 11724)
+++ branches/enterprise/JBPAPP_4_3_CP07/doc/Seam2_Reference_Guide/en-US/Tutorial.xml	2009-12-04 08:17:36 UTC (rev 11725)
@@ -1325,11 +1325,6 @@
                 configuration and not very interesting. </para>
         </section>
 
-        <section>
-            <title>How it works</title>
-            <para>TODO</para>
-        </section>
-
     </section>
 
     <section id="numberguess">
@@ -1695,11 +1690,6 @@
             
         </section>
 
-        <section>
-            <title>How it works</title>
-            <para>TODO</para>
-        </section>
-
     </section>
 
     <section id="booking">
@@ -2299,7 +2289,7 @@
         </mediaobject>
       </screenshot>
 
-        <para> The administration screens take use jBPM to manage the approval and shipping cycle for orders. The
+        <para> The administration screens use jBPM to manage the approval and shipping cycle for orders. The
             business process may even be changed dynamically, by selecting a different process definition! </para>
 
         <screenshot>
@@ -2314,8 +2304,6 @@
         </mediaobject>
       </screenshot>
 
-        <para>TODO</para>
-        <para>Look in the <literal>dvdstore</literal> directory.</para>
     </section>
 
     <section id="hibernate">
@@ -2324,8 +2312,7 @@
         <para> The Hibernate Booking demo is a straight port of the Booking demo to an alternative architecture that
             uses Hibernate for persistence and JavaBeans instead of session beans. </para>
 
-        <para>TODO</para>
-        <para>Look in the <literal>hibernate</literal> directory.</para>
+
     </section>
 
     <section id="blog">



More information about the seam-commits mailing list