[jboss-cvs] JBossAS SVN: r96541 - projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Nov 18 23:44:22 EST 2009
Author: gmeintjes
Date: 2009-11-18 23:44:22 -0500 (Wed, 18 Nov 2009)
New Revision: 96541
Modified:
projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Conversations.xml
projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Events.xml
projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Tutorial.xml
Log:
Amended as per JBPAPP-1714
Modified: projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Conversations.xml
===================================================================
--- projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Conversations.xml 2009-11-19 04:43:05 UTC (rev 96540)
+++ projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Conversations.xml 2009-11-19 04:44:22 UTC (rev 96541)
@@ -159,9 +159,9 @@
<para>
A conversation may be thought of as a <emphasis>continuable state</emphasis>. Nested conversations allow the application to capture a consistent continuable state at various points in a user interaction, thus insuring truly correct behavior in the face of backbuttoning and 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 current nested conversation, the nested conversation will use the same instance. Occasionally, it is useful to have a different instance in each nested conversation, so that the component instance that exists in the parent conversation is invisible to its child conversations. You can achieve this behavior by annotating the component <literal>@PerNestedConversation</literal>.
</para>
Modified: projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Events.xml
===================================================================
--- projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Events.xml 2009-11-19 04:43:05 UTC (rev 96540)
+++ projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Events.xml 2009-11-19 04:44:22 UTC (rev 96541)
@@ -76,9 +76,10 @@
The page action method can return a JSF outcome. If the outcome is non-null, Seam will use the defined navigation rules to navigate to a view.
</para>
<para>
- Furthermore, the view id mentioned in the <literal><page></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:
+ Furthermore, the view id mentioned in the <literal><page></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.
</para>
-<programlisting>TODO: translate struts action into page action</programlisting>
+ <!-- <para>For example:</para>
+<programlisting>TODO: translate struts action into page action</programlisting> -->
<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: projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Tutorial.xml
===================================================================
--- projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Tutorial.xml 2009-11-19 04:43:05 UTC (rev 96540)
+++ projects/docs/enterprise/4.2.8/Seam/Reference_Guide/en-US/Tutorial.xml 2009-11-19 04:44:22 UTC (rev 96541)
@@ -1263,12 +1263,12 @@
</para>
</section>
- <section id="Seam_and_jBPM_the_todo_list_example-How_it_works">
+ <!-- <section id="Seam_and_jBPM_the_todo_list_example-How_it_works">
<title>How it works</title>
<para>
TODO
</para>
- </section>
+ </section> -->
</section>
@@ -1534,12 +1534,12 @@
</para>
</section>
- <section id="Seam_pageflow_the_numberguess_example-How_it_works">
+ <!-- <section id="Seam_pageflow_the_numberguess_example-How_it_works">
<title>How it works</title>
<para>
TODO
</para>
- </section>
+ </section> -->
</section>
@@ -2096,12 +2096,13 @@
<imagedata align="center" fileref="images/dvdtasks.png" />
</imageobject>
</mediaobject>
- </screenshot><para>
+ </screenshot>
+ <!-- <para>
TODO
</para>
<para>
Look in the <literal>dvdstore</literal> directory.
- </para>
+ </para> -->
</section>
<section id="Seam_Tutorial-A_complete_application_featuring_Seam_workspace_management_the_Issue_Tracker_example">
@@ -2119,12 +2120,13 @@
<imagedata align="center" fileref="images/issues.png" />
</imageobject>
</mediaobject>
- </screenshot><para>
+ </screenshot>
+ <!-- <para>
TODO
</para>
<para>
Look in the <literal>issues</literal> directory.
- </para>
+ </para> -->
</section>
<section id="Seam_Tutorial-An_example_of_Seam_with_Hibernate_the_Hibernate_Booking_example">
@@ -2132,12 +2134,12 @@
<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>
+ <!-- <para>
TODO
</para>
<para>
Look in the <literal>hibernate</literal> directory.
- </para>
+ </para> -->
</section>
<section id="Seam_Tutorial-A_RESTful_Seam_application_the_Blog_example">
More information about the jboss-cvs-commits
mailing list