[jboss-cvs] jboss-seam/doc/reference/en/modules ...
Gavin King
gavin.king at jboss.com
Tue Jan 16 22:14:29 EST 2007
User: gavin
Date: 07/01/16 22:14:29
Modified: doc/reference/en/modules conversations.xml events.xml
jbpm.xml tutorial.xml
Log:
minor updates
Revision Changes Path
1.22 +4 -4 jboss-seam/doc/reference/en/modules/conversations.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: conversations.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/conversations.xml,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- conversations.xml 20 Nov 2006 23:58:18 -0000 1.21
+++ conversations.xml 17 Jan 2007 03:14:29 -0000 1.22
@@ -298,8 +298,8 @@
<para>
This action method is called at the beginning of the render response
phase, any time the page is about to be rendered. If a page action
- returns a non-null outcome, Seam will process any appropriate JSF
- navigation rules, possibly resulting in a completely different page
+ returns a non-null outcome, Seam will process any appropriate JSF and
+ Seam navigation rules, possibly resulting in a completely different page
being rendered.
</para>
@@ -605,7 +605,7 @@
<listitem>
<para>
Provide <emphasis>description</emphasis> text for each view id
- (when using JSF navigation rules) or page node (when using
+ (when using JSF or Seam navigation rules) or page node (when using
jPDL pageflows). This description text is displayed to the user
by the workspace switchers.
</para>
@@ -623,7 +623,7 @@
<section>
<title>Workspace management and JSF navigation</title>
<para>
- When you use JSF navigation rules, Seam switches to a
+ When you use JSF or Seam navigation rules, Seam switches to a
conversation by restoring the current <literal>view-id</literal>
for that conversation. The descriptive text for the
workspace is defined in a file called <literal>pages.xml</literal>
1.9 +2 -2 jboss-seam/doc/reference/en/modules/events.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: events.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/events.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -b -r1.8 -r1.9
--- events.xml 17 Jan 2007 02:52:11 -0000 1.8
+++ events.xml 17 Jan 2007 03:14:29 -0000 1.9
@@ -89,8 +89,8 @@
<para>
The page action method can return a JSF outcome. If the outcome is
- non-null, Seam will delegate to the defined JSF navigation rules and
- a different view may end up being rendered.
+ non-null, Seam will delegate to the defined JSFadn Seam navigation rules
+ and a different view may end up being rendered.
</para>
<para>
1.26 +25 -4 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.25
retrieving revision 1.26
diff -u -b -r1.25 -r1.26
--- jbpm.xml 23 Nov 2006 04:05:08 -0000 1.25
+++ jbpm.xml 17 Jan 2007 03:14:29 -0000 1.26
@@ -50,7 +50,7 @@
<para>
You don't have to know jDPL to use Seam. If you're perfectly happy defining
- pageflow using JSF's navigation rules, and if your application is more
+ pageflow using JSF or Seam navigation rules, and if your application is more
data-driven that process-driven, you probably don't need jBPM. But we're
finding that thinking of user interaction in terms of a well-defined graphical
representation is helping us build more robust applications.
@@ -65,7 +65,7 @@
<itemizedlist>
<listitem>
<para>
- Using JSF navigation rules - the <emphasis>stateless navigation
+ Using JSF or Seam navigation rules - the <emphasis>stateless navigation
model</emphasis>
</para>
</listitem>
@@ -124,6 +124,27 @@
</navigation-rule>]]></programlisting>
<para>
+ Here is the same example page flow definition using Seam navigation
+ rules:
+ </para>
+
+ <programlisting><![CDATA[<page view-id="/numberGuess.jsp">
+
+ <navigation>
+ <rule if-outcome="guess">
+ <redirect view-id="/numberGuess.jsp"/>
+ </rule>
+ <rule if-outcome="win">
+ <redirect view-id="/win.jsp"/>
+ </rule>
+ <rule if-outcome="lose">
+ <redirect view-id="/lose.jsp"/>
+ </rule>
+ </navigation-case>
+
+</navigation-rule>]]></programlisting>
+
+ <para>
If you find navigation rules overly verbose, you can return view ids
directly from your action listener methods:
</para>
@@ -202,7 +223,7 @@
<itemizedlist>
<listitem>
<para>
- The JSF navigation rules are <emphasis>much</emphasis> simpler.
+ The JSF/Seam navigation rules are <emphasis>much</emphasis> simpler.
(However, this obscures the fact that the underlying Java code
is more complex.)
</para>
@@ -248,7 +269,7 @@
<title>Seam and the back button</title>
<para>
- When JSF navigation rules are used, Seam lets the user freely
+ When JSF or Seam navigation rules are used, Seam lets the user freely
navigate via the back, forward and refresh buttons. It is the
responsibility of the application to ensure that conversational
state remains internally consistent when this occurs. Experience
1.76 +1 -1 jboss-seam/doc/reference/en/modules/tutorial.xml
(In the diff below, changes in quantity of whitespace are not shown.)
Index: tutorial.xml
===================================================================
RCS file: /cvsroot/jboss/jboss-seam/doc/reference/en/modules/tutorial.xml,v
retrieving revision 1.75
retrieving revision 1.76
diff -u -b -r1.75 -r1.76
--- tutorial.xml 5 Dec 2006 20:28:27 -0000 1.75
+++ tutorial.xml 17 Jan 2007 03:14:29 -0000 1.76
@@ -1669,7 +1669,7 @@
<title>Seam pageflow: the numberguess example</title>
<para>
- For Seam applications with relatively freeform (ad hoc) navigation, JSF
+ For Seam applications with relatively freeform (ad hoc) navigation, JSF/Seam
navigation rules are a perfectly good way to define the page flow.
For applications with a more constrained style of navigation, especially
for user interfaces which are more stateful, navigation rules make it
More information about the jboss-cvs-commits
mailing list