[jboss-cvs] JBossAS SVN: r103366 - projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: laubai
Date: 2010-03-31 19:51:59 -0400 (Wed, 31 Mar 2010)
New Revision: 103366

Modified:
   projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Events.xml
   projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Tutorial.xml
Log:
JBPAPP-4035 Corrected issues 1,3; did not find issue 2.

Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Events.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Events.xml	2010-03-31 22:33:05 UTC (rev 103365)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Events.xml	2010-03-31 23:51:59 UTC (rev 103366)
@@ -329,7 +329,7 @@
 	 <section id="events.pageaction.navigation">
 		<title>Navigation</title>
 		 <para>
-			You can use standard JSF navigation rules defined in <filename>Faces-config.xml</filename> in a Seam application. However, these rules have several limitations:
+			You can use standard JSF navigation rules defined in <filename>faces-config.xml</filename> in a Seam application. However, these rules have several limitations:
 		</para>
 		 <itemizedlist>
 			<listitem>
@@ -349,7 +349,7 @@
 			</listitem>
 		</itemizedlist>
 		 <para>
-			Another problem is that "orchestration" logic is scattered between <filename>pages.xml</filename> and <filename>Faces-config.xml</filename>. It is better to unify this logic under <filename>pages.xml</filename>.
+			Another problem is that "orchestration" logic is scattered between <filename>pages.xml</filename> and <filename>faces-config.xml</filename>. It is better to unify this logic under <filename>pages.xml</filename>.
 		</para>
 		 <para>
 			This JSF navigation rule:

Modified: projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Tutorial.xml
===================================================================
--- projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Tutorial.xml	2010-03-31 22:33:05 UTC (rev 103365)
+++ projects/docs/enterprise/5.0.1/Seam_Reference_Guide/en-US/Tutorial.xml	2010-03-31 23:51:59 UTC (rev 103366)
@@ -2953,7 +2953,7 @@
 				The page parameter instructs Seam to link the <literal>searchPattern</literal> request parameter to the value held by <literal>#{searchService.searchPattern}</literal>, whenever the search page is requested, and whenever a link to the search page is generated. Seam takes responsibility for maintaining the link between URL state and application state.
 			</para>
 			 <para>
-				The URL for a search on the term <parameter>book</parameter> would ordinarily be <literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern= book</literal>. Seam can simplify this URL by using a rewrite rule. The first rewrite rule, for the pattern <literal>/search/{searchPattern}</literal>, states that whenever a URL for search.xhtml contains a searchPattern request parameter, that URL can be compressed into a simplified URL. So, the earlier URL (<literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern= book</literal>) can instead be written as <literal>http://localhost:8080/seam-blog/search/book</literal>.
+				The URL for a search on the term <parameter>book</parameter> would ordinarily be <literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern=book</literal>. Seam can simplify this URL by using a rewrite rule. The first rewrite rule, for the pattern <literal>/search/{searchPattern}</literal>, states that whenever a URL for search.xhtml contains a searchPattern request parameter, that URL can be compressed into a simplified URL. So, the earlier URL (<literal>http://localhost:8080/seam-blog/seam/search.xhtml?searchPattern= book</literal>) can instead be written as <literal>http://localhost:8080/seam-blog/search/book</literal>.
 			</para>
 			 <para>
 				As with page parameters, rewriting URLs is bidirectional. This means that Seam forwards requests for the simplified URL to the correct view, and it automatically generates the simplified view — users need not construct URLs. The entire process is handled transparently. The only requirement for rewriting URLs is to enable the rewrite filter in <filename>components.xml</filename>: