[jboss-cvs] JBossAS SVN: r108128 - projects/docs/community/6/JSF_Guide/en-US.

jboss-cvs-commits at lists.jboss.org jboss-cvs-commits at lists.jboss.org
Mon Sep 13 17:25:50 EDT 2010


Author: stan.silvert at jboss.com
Date: 2010-09-13 17:25:50 -0400 (Mon, 13 Sep 2010)
New Revision: 108128

Modified:
   projects/docs/community/6/JSF_Guide/en-US/JSF_Deployment.xml
   projects/docs/community/6/JSF_Guide/en-US/JSF_Quick_Start.xml
Log:
Update for addition of MyFaces-2.0 configuration.


Modified: projects/docs/community/6/JSF_Guide/en-US/JSF_Deployment.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/JSF_Deployment.xml	2010-09-13 16:51:59 UTC (rev 108127)
+++ projects/docs/community/6/JSF_Guide/en-US/JSF_Deployment.xml	2010-09-13 21:25:50 UTC (rev 108128)
@@ -18,8 +18,9 @@
         </para>
 	<para>
           The JSF Deployer is located in the <filename>deployers/jsf.deployer</filename>
-          directory.  By default, JBoss AS6 ships with two JSF implementations located
-          in the <filename>jsf.deployer/Mojarra-2.0</filename> and
+          directory.  By default, JBoss AS6 ships with three JSF implementations located
+          in the <filename>jsf.deployer/Mojarra-2.0</filename>,
+          <filename>jsf.deployer/MyFaces-2.0</filename>, and
           <filename>jsf.deployer/Mojarra-1.2</filename> directories.  These
           directories contain <firstterm>JSF Configurations</firstterm>.
         </para>
@@ -138,7 +139,8 @@
      <section id="changing.jsf.config">
        <title>Changing the JSF Configuration for your WAR</title>
        <para>
-         JBoss AS ships with two JSF Implementations, Mojarra 1.2 and Mojarra 2.0.  
+         JBoss AS ships with three JSF Implementations, Mojarra 1.2, Mojarra 2.0,
+         and MyFaces 2.0.
          By default, JSF applications will use Mojarra 2.0.  While most JSF 1.2 
          applications will run on JSF 2.0 without changes, there are a few rare 
          instances where this is not the case.  Also, when migrating to 
@@ -148,7 +150,7 @@
        <para>
          If you look at the <filename>deployers/jsf.deployer</filename> directory 
          you will see the JSF configurations that ship with JBoss AS6.  To 
-         tell your application to use another JSF configuration, add this to 
+         tell your application to use one of these JSF configurations, add this to
          your <filename>web.xml</filename>:
        <programlisting><![CDATA[<context-param>
       <param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name>

Modified: projects/docs/community/6/JSF_Guide/en-US/JSF_Quick_Start.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/JSF_Quick_Start.xml	2010-09-13 16:51:59 UTC (rev 108127)
+++ projects/docs/community/6/JSF_Guide/en-US/JSF_Quick_Start.xml	2010-09-13 21:25:50 UTC (rev 108128)
@@ -32,19 +32,27 @@
 </web-app>]]>
        </programlisting>
        <note>
-         You don't necessarily need to declare a FacesServlet or mappings in web.xml.  If you
+         As shown, you don't necessarily need to declare a FacesServlet or mappings in web.xml.  If you
          leave this out, JBoss AS6 will add it automatically with default mappings as
          demonstrated at the end of this chapter.
        </note>
      </section>
 
      <section id="create-markup">
-       <title>Create faces-config.xml</title>
+       <title>Create a minimal faces-config.xml</title>
        <para>
-         Create an empty <filename>faces-config.xml</filename> file and place it in <filename>/WEB-INF</filename>.
+         This <filename>faces-config.xml</filename> only needs the minimum
+         declarations shown below.  Place the file in <filename>/WEB-INF</filename>.
        </para>
+       <programlisting><![CDATA[<faces-config xmlns="http://java.sun.com/xml/ns/javaee"
+              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+              xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-facesconfig_2_0.xsd"
+              version="2.0">
+
+</faces-config>]]>
+       </programlisting>
        <para>
-         The faces-config.xml file can be completely empty.  It is only there to signal to
+         The faces-config.xml is only there to signal to
          JBoss AS that this is a JSF application.  There are many other ways that JBoss
          AS6 could recognize this as a JSF application.  This is explained in detail in chapter 3.
        </para>



More information about the jboss-cvs-commits mailing list