[jboss-cvs] JBossAS SVN: r107821 - in projects/docs/community/6: Admin_Console_Guide and 3 other directories.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Thu Aug 26 19:47:34 EDT 2010
Author: stan.silvert at jboss.com
Date: 2010-08-26 19:47:34 -0400 (Thu, 26 Aug 2010)
New Revision: 107821
Added:
projects/docs/community/6/JSF_Guide/
projects/docs/community/6/JSF_Guide/en-US/
projects/docs/community/6/JSF_Guide/en-US/Author_Group.xml
projects/docs/community/6/JSF_Guide/en-US/Book_Info.xml
projects/docs/community/6/JSF_Guide/en-US/JSF_And_Serialization.xml
projects/docs/community/6/JSF_Guide/en-US/JSF_Deployment.xml
projects/docs/community/6/JSF_Guide/en-US/JSF_Guide.xml
projects/docs/community/6/JSF_Guide/en-US/JSF_Guide_Introduction.xml
projects/docs/community/6/JSF_Guide/en-US/JSF_Guide_Reference.xml
projects/docs/community/6/JSF_Guide/en-US/JSF_Quick_Start.xml
projects/docs/community/6/JSF_Guide/en-US/Legal_Notice.xml
projects/docs/community/6/JSF_Guide/pom.xml
Modified:
projects/docs/community/6/Admin_Console_Guide/
projects/docs/community/6/Admin_Console_Guide/en-US/Legal_Notice.xml
projects/docs/community/6/Admin_Console_Guide/pom.xml
Log:
AS6 JSF Guide
Property changes on: projects/docs/community/6/Admin_Console_Guide
___________________________________________________________________
Name: svn:ignore
+ target
Modified: projects/docs/community/6/Admin_Console_Guide/en-US/Legal_Notice.xml
===================================================================
--- projects/docs/community/6/Admin_Console_Guide/en-US/Legal_Notice.xml 2010-08-26 21:47:42 UTC (rev 107820)
+++ projects/docs/community/6/Admin_Console_Guide/en-US/Legal_Notice.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -3,15 +3,15 @@
]>
<legalnotice id="Book-Legal_Notice">
- <title>Legal Notice</title>
- <para>
- <address>
- <street>1801 Varsity Drive</street>
- <city>Raleigh</city>, <state>NC</state><postcode>27606-2072</postcode><country>USA</country><phone>Phone: +1 919 754 3700</phone>
- <phone>Phone: 888 733 4281</phone>
- <fax>Fax: +1 919 754 3701</fax>
- <pob>PO Box 13588</pob><city>Research Triangle Park</city>, <state>NC</state><postcode>27709</postcode><country>USA</country>
- </address>
- </para>
+ <title>Legal Notice</title>
+ <para>
+ <address>
+ <street>1801 Varsity Drive</street>
+ <city>Raleigh</city>, <state>NC</state><postcode>27606-2072</postcode><country>USA</country><phone>Phone: +1 919 754 3700</phone>
+ <phone>Phone: 888 733 4281</phone>
+ <fax>Fax: +1 919 754 3701</fax>
+ <pob>PO Box 13588</pob><city>Research Triangle Park</city>, <state>NC</state><postcode>27709</postcode><country>USA</country>
+ </address>
+ </para>
</legalnotice>
Modified: projects/docs/community/6/Admin_Console_Guide/pom.xml
===================================================================
--- projects/docs/community/6/Admin_Console_Guide/pom.xml 2010-08-26 21:47:42 UTC (rev 107820)
+++ projects/docs/community/6/Admin_Console_Guide/pom.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -9,7 +9,15 @@
<version>1.0-SNAPSHOT</version>
<packaging>jdocbook</packaging>
<name>Administration Console Guide (${translation})</name>
-
+
+ <distributionManagement>
+ <repository>
+ <id>docs.jboss.org</id>
+ <name>JBoss AS Doco Repo</name>
+ <url>sftp://jbossas@filemgmt.jboss.org:/docs_htdocs/jbossas/6/Admin_Console_Guide</url>
+ </repository>
+ </distributionManagement>
+
<build>
<plugins>
<plugin>
Added: projects/docs/community/6/JSF_Guide/en-US/Author_Group.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/Author_Group.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/en-US/Author_Group.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,15 @@
+<?xml version='1.0'?>
+<!DOCTYPE authorgroup PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+ ]>
+<authorgroup>
+ <author>
+ <firstname>Stan</firstname>
+ <surname>Silvert</surname>
+ <!--<affiliation>
+ <shortaffil></shortaffil>
+ <jobtitle></jobtitle>
+ <orgname>Red Hat</orgname>
+ </affiliation>-->
+ </author>
+
+</authorgroup>
Added: projects/docs/community/6/JSF_Guide/en-US/Book_Info.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/Book_Info.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/en-US/Book_Info.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,20 @@
+<?xml version="1.0" standalone="no"?>
+<!DOCTYPE bookinfo PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [ ]>
+
+<bookinfo>
+<title>JBoss AS 6.0 JSF Guide</title>
+ <subtitle>JSF with JBoss Application Server 6</subtitle>
+ <!-- <edition>2</edition>
+ <issuenum>1</issuenum>
+ <pubsnumber>1</pubsnumber>-->
+ <productname>JBoss Application Server</productname>
+ <productnumber>6.0</productnumber>
+ <pubdate>Sep 2010</pubdate>
+ <abstract>
+ <para>
+ This book is the JBoss Application Server 6 JSF Guide.
+ </para>
+ </abstract>
+ <!-- <subtitle>Authors</subtitle>-->
+ <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</bookinfo>
Added: projects/docs/community/6/JSF_Guide/en-US/JSF_And_Serialization.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/JSF_And_Serialization.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/en-US/JSF_And_Serialization.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
+
+ <chapter id="jsf.serialization.chapt">
+ <title>JSF and Serialization</title>
+
+ <para>
+ Serialization can be one of the most costly operations in a JSF application.
+ This is especially true when using client side state-saving, but it can
+ also come into play when you use server-side state saving as well.
+ </para>
+
+ <section id="jboss.serialization">
+ <title>Using JBoss Serialization</title>
+ <para>
+ JBoss AS6 ships with a serialization provider that allows you to use
+ the JBossSerialization project with Mojarra 1.2 and 2.0. While your
+ results will vary, using JBossSerialization may boost performance,
+ especially with older versions of Java.
+ </para>
+
+ <para>
+ To enable JBossSerialization in Mojarra JSF, set the following context
+ parameter in your <filename>web.xml</filename> file.
+ </para>
+
+ <programlisting><![CDATA[<context-param>
+ <param-name>com.sun.faces.serializationProvider</param-name>
+ <param-value>org.jboss.web.jsf.integration.serialization.JBossSerializationProvider</param-value>
+</context-param>]]>
+ </programlisting>
+
+ </section>
+
+ </chapter>
+
Added: projects/docs/community/6/JSF_Guide/en-US/JSF_Deployment.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/JSF_Deployment.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/en-US/JSF_Deployment.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,238 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
+
+ <chapter id="jsf.deployer.config">
+ <title>Deploying Your JSF Applications</title>
+
+ <para>
+ In this chapter, we cover all the deployment options for your JSF applications.
+ </para>
+
+ <section id="jsf.deployer">
+ <title>The JSF Deployer</title>
+ <para>
+ JSF integration for JBoss AS6 has been re-written to take
+ advantage of the JBoss deployer architecture. So instead of having
+ JSF tightly coupled to the Servlet container, it is now an independent deployer
+ that adds JSF to your WAR when needed.
+ </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
+ <filename>jsf.deployer/Mojarra-1.2</filename> directories. These
+ directories contain <firstterm>JSF Configurations</firstterm>.
+ </para>
+ <note>
+ A JSF Configuration is more than just the implementation jars. It can
+ contain supporting jars such as parsers and JSF component libraries. It also
+ contains initialization and configuration settings that are applied to your
+ application when the JSF Configuration is added to your WAR deployment.
+ </note>
+ <para>
+ Inside the <filename>jsf.deployer/META-INF</filename> directory you will
+ find a file called <filename>jsf-integration-deployer-jboss-beans.xml</filename>.
+ You can use this file for advanced configuration of the deployer, which we
+ will describe in some of the sections that follow.
+ </para>
+ </section>
+ <section id="how.deployer.decides">
+ <title>How the JSF Deployer Recognizes your JSF Application</title>
+ <para>
+ In past versions of JBoss AS, <emphasis>every</emphasis> web
+ application had a JSF implementation
+ and its supporting jars placed on its classpath. In addition, every
+ web application went through at least some of the JSF initialization
+ process - even when it didn't use JSF. With JBoss AS6, JSF jars are
+ only added to the classpath when needed.
+ </para>
+ <para>
+ When a web application is deployed, the JSF Deployer determines if it
+ is a JSF application. It recognizes a web application if any of the
+ following are true:
+ </para>
+ <itemizedlist>
+ <listitem>A FacesServlet is declared in <filename>WEB-INF/web.xml</filename> or a <filename>web-fragment.xml</filename></listitem>
+ <listitem>A <filename>faces-config.xml</filename> file is found in <filename>WEB-INF</filename></listitem>
+ <listitem>A <filename>faces-config.xml</filename> file is found in <filename>META-INF</filename> of some jar in <filename>WEB-INF/lib</filename></listitem>
+ <listitem>A <filename>*.faces-config.xml</filename> file is found in <filename>META-INF</filename> of some jar in <filename>WEB-INF/lib</filename></listitem>
+ <listitem>The <filename>javax.faces.CONFIG_FILES</filename> context param is declared in <filename>WEB-INF/web.xml</filename> or a <filename>web-fragment.xml</filename></listitem>
+ <listitem>The <filename>org.jboss.jbossfaces.JSF_CONFIG_NAME</filename> context param is declared in <filename>WEB-INF/web.xml</filename> or a <filename>web-fragment.xml</filename></listitem>
+ <listitem>"alwaysAddJSF" is set to true in <filename>jsf-integration-deployer-jboss-beans.xml</filename></listitem>
+ </itemizedlist>
+
+
+ </section>
+
+ <section id="auto.adding.jsf.declarations">
+ <title>Auto-adding of the JSF FacesServlet</title>
+ <para>
+ If the JSF Deployer determines that a WAR is a JSF application, but
+ <classname>javax.faces.webapp.FacesServlet</classname> is not already declared
+ as a servlet, the deployer will add an instance of this servlet for you.
+ </para>
+ <para>
+ If it adds the FacesServlet, it will also add the following mappings for it:
+ <itemizedlist>
+ <listitem>/faces/*</listitem>
+ <listitem>*.jsf</listitem>
+ <listitem>*.faces</listitem>
+ </itemizedlist>
+ </para>
+ </section>
+
+ <section id="non.standard.facesservlet">
+ <title>Using a Non-standard FacesServlet</title>
+ <para>
+ Though it is not recommended, some applications use a non-standard
+ servlet to control JSF services. You can configure the JSF Deployer
+ to recognize a non-standard servlet as a JSF application.
+ Edit the file <filename>jsf.deployer/META-INF/jsf-integration-deployer-jboss-beans.xml</filename>
+ and add your servlet to the facesServlets property.
+ </para>
+ <para>
+ In this example, we add <classname>org.foo.MyWrapperFacesServlet</classname>.
+ When an application is deployed with this servlet it will be recognized as a
+ JSF application.
+ <programlisting><![CDATA[<bean name="JSFImplManagementDeployer">
+
+
+ <!--
+ * Specify the servlet classes that signal this deployer to add JSF to a WAR.
+ -->
+ <property name="facesServlets">
+ <collection elementClass="java.lang.String">
+ <value>javax.faces.webapp.FacesServlet</value>
+ <value>org.foo.MyWrapperFacesServlet</value>
+ </collection>
+ </property>]]>
+ </programlisting>
+ </para>
+
+ </section>
+
+ <section id="bundling.jsf.with.war">
+ <title>Bundling JSF Inside Your WAR</title>
+ <para>
+ Some containers such as Tomcat 6 require you to bundle a JSF implementation
+ in the <filename>WEB-INF/lib</filename> directory of your WAR. If you
+ would like to use such a WAR with JBoss AS6 then you can signal the
+ JSF Deployer to ignore your WAR and let it use the bundled JSF version.
+ </para>
+ <para>
+ To do that, just specify the WAR_BUNDLES_JSF context param in your
+ web.xml file like this:
+ <programlisting><![CDATA[<context-param>
+ <param-name>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</param-name>
+ <param-value>true</param-value>
+</context-param>]]>
+ </programlisting>
+ </para>
+ <note>
+ This context-param was available in earlier versions of JBoss AS.
+ However, it only worked when bundling MyFaces and when using the default
+ classloader configuration. Now in AS6 you can use this context-param
+ any time you want to bundle your own JSF impl.
+ </note>
+ </section>
+ <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.
+ 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
+ JBoss AS6 from AS5, you might want to first use the older JSF
+ implementation and "ease into" the world of JSF 2.0 later.
+ </para>
+ <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
+ your <filename>web.xml</filename>:
+ <programlisting><![CDATA[<context-param>
+ <param-name>org.jboss.jbossfaces.JSF_CONFIG_NAME</param-name>
+ <param-value>Mojarra-1.2</param-value>
+ </context-param>]]>
+ </programlisting>
+ </para>
+ </section>
+ <section id="adding.jsf.config">
+ <title>Adding a New JSF Configuration</title>
+ <para>
+ A new JSF Configuration is useful when you want to add a new JSF
+ implementation to JBoss AS or you just want to enhance an implementation
+ with extra jars such as component libraries. This can save you from
+ bundling the same jars over and over in your WARs.
+ </para>
+ <para>
+ It's also useful for testing the same application against different JSF
+ implementations, library versions, and configurations. You can create
+ a JSF Configuration and then apply it to your WAR with a a simple
+ context param.
+ </para>
+ <para>
+ A JSF Configuration consists of some jars and a special <filename>web.xml</filename>
+ file. When a JSF Configuration is added to a WAR by the JSF Deployer,
+ the jars are added to the classpath and the elements in the
+ <filename>web.xml</filename> file are activated. To add your own
+ JSF Confguration, just create the directory structure below.
+ This is usually done in the jsf.deployer directory:
+ <itemizedlist>
+ <listitem><filename>jsf.deployer/MyJSFConfig/jsf-libs</filename></listitem>
+ <listitem><filename>jsf.deployer/MyJSFConfig/META-INF</filename></listitem>
+ </itemizedlist>
+ </para>
+ <para>
+ Place your jar files in <filename>/jsf-libs</filename> and place your
+ <filename>web.xml</filename> in <filename>/META-INF</filename>.
+ When your JSF Configuration is activated for a WAR, all jars in the
+ jsf-libs directory will be added to the classpath.
+ </para>
+ <para>
+ The elements in your special <filename>META-INF/web.xml</filename> file will
+ also be added to your WAR. This can help you configure the JSF
+ implementation and component libraries. However, note that only a
+ few web.xml elements are allowed in this file. These elements are
+ <emphasis>servlet, servlet-mapping, filter, filter-mapping, listener,
+ and context-param</emphasis>. All other web.xml elements are
+ currently ignored, but we may support more in the future.
+ </para>
+ </section>
+ <section id="activating.jsf.config">
+ <title>Activating a New JSF Configuration</title>
+ <para>
+ To allow the JSF Deployer to recognize your JSF Configuration, you
+ will need to edit
+ <filename>deployers/jsf.deployer/META-INF/jsf-integration-deployer-jboss-beans.xml</filename>:
+ <programlisting><![CDATA[<property name="jsfConfigurations">
+ <map keyClass="java.lang.String" valueClass="java.lang.String">
+ <entry>
+ <key>Mojarra-1.2</key>
+ <value>${jboss.server.home.url}deployers/jsf.deployer/Mojarra-1.2</value>
+ </entry>
+ <entry>
+ <key>Mojarra-2.0</key>
+ <value>${jboss.server.home.url}deployers/jsf.deployer/Mojarra-2.0</value>
+ </entry>
+
+ <entry>
+ <key>MyJSFConfig</key>
+ <value>${jboss.server.home.url}deployers/jsf.deployer/MyJSFConfig</value>
+ </entry>
+ </map>
+</property>]]>
+ </programlisting>
+ <programlisting><![CDATA[<bean name="JSFUrlIntegrationDeployer-MyJSFConfig">
+ <property name="JSFImplName">
+ <value>MyJSFConfig</value>
+ </property>
+ <property name="JSFImplManagementDeployer">
+ <inject bean="JSFImplManagementDeployer"/>
+ </property>
+</bean>]]>
+ </programlisting>
+ </para>
+
+ </section>
+ </chapter>
\ No newline at end of file
Added: projects/docs/community/6/JSF_Guide/en-US/JSF_Guide.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/JSF_Guide.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/en-US/JSF_Guide.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,25 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
+<book>
+
+<xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+
+<part id="Introduction">
+ <title>Introduction and Quick Start</title>
+ <xi:include href="JSF_Guide_Introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="JSF_Quick_Start.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</part>
+
+<part id="JSF_Config">
+ <title>Configuration</title>
+ <xi:include href="JSF_Deployment.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+ <xi:include href="JSF_and_Serialization.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</part>
+
+<part id="JSF_Reference">
+ <title>Reference</title>
+ <xi:include href="JSF_Guide_Reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
+</part>
+
+</book>
Added: projects/docs/community/6/JSF_Guide/en-US/JSF_Guide_Introduction.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/JSF_Guide_Introduction.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/en-US/JSF_Guide_Introduction.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
+
+ <chapter id="jsf-intro.chapt">
+ <title>Introduction</title>
+
+ <para>
+ In the past, using a JEE application server meant using the JSF implementation that ships with it.
+ However, there are subtle differences between JSF implementations. Applications written for Mojarra
+ don't always run well on MyFaces. There are sometimes backward compatibility issues between JSF
+ specification levels. An application written for JSF 1.2 won't always run on JSF 2.0.
+ </para>
+
+ <para>
+ JBoss AS6 is designed for maximum flexibility in JSF deployments. With JBoss AS6, you can use the
+ default JSF implementation, use a secondary JSF implementation, or bundle
+ your own JSF implementation with the WAR. You can have different applications in the same server instance
+ that use different implementations. Also, you can create your own JSF Configurations that include
+ a JSF implementation, extra libraries, and configuration parameters. Then assign the configuration
+ to one or more applications.
+ </para>
+
+ <para>
+ In this guide, we'll step through a simple JSF example. Then we will go through all the powerful deployment
+ options for JSF applications.
+ </para>
+
+ </chapter>
+
Added: projects/docs/community/6/JSF_Guide/en-US/JSF_Guide_Reference.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/JSF_Guide_Reference.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/en-US/JSF_Guide_Reference.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,515 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
+
+ <chapter id="jsf.reference">
+ <title>Reference</title>
+
+ <section id="standard.config.params">
+ <title>JSF Standard Context Params</title>
+ <table>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="col1" colwidth="6*"/>
+ <colspec colnum="2" colname="col2" colwidth="1*"/>
+ <colspec colnum="3" colname="col3" colwidth="4*"/>
+ <colspec colnum="4" colname="col4" colwidth="2*"/>
+
+ <thead>
+ <row>
+ <entry>Context Param</entry>
+ <entry>JSF Spec</entry>
+ <entry>Description</entry>
+ <entry>Default Value</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>javax.faces.CONFIG_FILES</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Comma-delimited list of faces config files.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>javax.faces.DEFAULT_SUFFIX</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Change the default suffix for JSP views.</entry>
+ <entry>.jsp</entry>
+ </row>
+ <row>
+ <entry>javax.faces.LIFECYCLE_ID</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>ID for alternate Lifecycle implementations.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>javax.faces.STATE_SAVING_METHOD</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>"server" or "client"</entry>
+ <entry>server</entry>
+ </row>
+ <row>
+ <entry>javax.faces.DATETIMECONVERTER _DEFAULT_TIMEZONE_IS _SYSTEM_TIMEZONE</entry>
+ <entry>2.0</entry>
+ <entry>Controls if DateTimeConverter instances use the system timezone (if true) or GMT (if false).</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>javax.faces.DATETIMECONVERTER _DEFAULT_TIMEZONE_IS _SYSTEM_TIMEZONE</entry>
+ <entry>2.0</entry>
+ <entry>Controls if DateTimeConverter instances use the system timezone (if true) or GMT (if false).</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>javax.faces.DISABLE_FACELET _JSF_VIEWHANDLER</entry>
+ <entry>2.0</entry>
+ <entry>Disables the built-in Facelet ViewHandler. Useful for applications that use legacy Facelets implementation.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>javax.faces.FACELETS_LIBRARIES</entry>
+ <entry>2.0</entry>
+ <entry>Semicolon-separated list of paths to Facelet tag libraries.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>facelets.LIBRARIES</entry>
+ <entry>2.0</entry>
+ <entry>Semicolon-separated list of paths to Facelet tag libraries. Used for backward-compatibility with legacy Facelets implementation.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>javax.faces.FACELETS_BUFFER_SIZE</entry>
+ <entry>2.0</entry>
+ <entry>The buffer size set on the response.</entry>
+ <entry>-1 (no assigned buffer size)</entry>
+ </row>
+ <row>
+ <entry>facelets.BUFFER_SIZE</entry>
+ <entry>2.0</entry>
+ <entry>The buffer size set on the response. Used for backward-compatibility with legacy Facelets implementation.</entry>
+ <entry>-1 (no assigned buffer size)</entry>
+ </row>
+ <row>
+ <entry>javax.faces.DECORATORS</entry>
+ <entry>2.0</entry>
+ <entry>Semicolon-delimited list of TagDecorator implementations. See javadoc for javax.faces.view .facelets.TagDecorator.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>facelets.DECORATORS</entry>
+ <entry>2.0</entry>
+ <entry>Semicolon-delimited list of TagDecorator implementations. Used for backward-compatibility with legacy Facelets implementation.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>javax.faces.FACELETS _REFRESH_PERIOD</entry>
+ <entry>2.0</entry>
+ <entry>Time in seconds that facelets should be checked for changes since last request. A value of -1 disables refresh checking.</entry>
+ <entry>implementation-specific</entry>
+ </row>
+ <row>
+ <entry>facelets.REFRESH_PERIOD</entry>
+ <entry>2.0</entry>
+ <entry>Time in seconds that facelets should be checked for changes since last request. A value of -1 disables refresh checking. Used for backward-compatibility with legacy Facelets implementation.</entry>
+ <entry>implementation-specific</entry>
+ </row>
+ <row>
+ <entry>javax.faces.FACELETS _RESOURCE_RESOLVER</entry>
+ <entry>2.0</entry>
+ <entry>An implementation of javax.faces .view.facelets .ResourceResolver. See javadoc for details.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>facelets.RESOURCE_RESOLVER</entry>
+ <entry>2.0</entry>
+ <entry>An implementation of javax.faces .view.facelets .ResourceResolver. See javadoc for details. Used for backward-compatibility with legacy Facelets implementation.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>javax.faces.FACELETS_SKIP _COMMENTS</entry>
+ <entry>2.0</entry>
+ <entry>If true, strip XML comments out of Facelets before delivering to the client.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>facelets.SKIP_COMMENTS</entry>
+ <entry>2.0</entry>
+ <entry>If true, strip XML comments out of Facelets before delivering to the client. Used for backward-compatibility with legacy Facelets implementation.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>javax.faces.FACELETS_SUFFIX</entry>
+ <entry>2.0</entry>
+ <entry>Set the suffix for Facelet xhtml files.</entry>
+ <entry>.xhtml</entry>
+ </row>
+ <row>
+ <entry>facelets.SUFFIX</entry>
+ <entry>2.0</entry>
+ <entry>Set the suffix for Facelet xhtml files. Used for backward-compatibility with legacy Facelets implementation.</entry>
+ <entry>.xhtml</entry>
+ </row>
+ <row>
+ <entry>javax.faces.FACELETS_VIEW_MAPPINGS</entry>
+ <entry>2.0</entry>
+ <entry>Semicolon-separated list of Facelet files that don't use the default facelets suffix.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>facelets.VIEW_MAPPINGS</entry>
+ <entry>2.0</entry>
+ <entry>Semicolon-separated list of Facelet files that don't use the default facelets suffix. Used for backward-compatibility with legacy Facelets implementation.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>javax.faces.FULL_STATE _SAVING_VIEW_IDS</entry>
+ <entry>2.0</entry>
+ <entry>Semicolon-separated list of view IDs that must save state using the JSF 1.2-style state saving.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>javax.faces.INTERPRET_EMPTY _STRING_SUBMITTED_VALUES _AS_NULL</entry>
+ <entry>2.0</entry>
+ <entry>If true, consider empty UIInput values to be null instead of empty string.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>javax.faces.PARTIAL_STATE_SAVING</entry>
+ <entry>2.0</entry>
+ <entry>If true, use the JSF2 partial state saving for views.</entry>
+ <entry>false, if WEB-INF/faces-config.xml does not declare JSF 2.0 schema. true, otherwise</entry>
+ </row>
+ <row>
+ <entry>javax.faces.PROJECT_STAGE</entry>
+ <entry>2.0</entry>
+ <entry>Set the project stage to "Development", "UnitTest", "SystemTest", or "Production".</entry>
+ <entry>Production</entry>
+ </row>
+ <row>
+ <entry>javax.faces.VALIDATE_EMPTY_FIELDS</entry>
+ <entry>2.0</entry>
+ <entry>If "true", validate null and empty values. If "auto" validate when JSR-303 Bean Validation is enabled (in AS6 it is enabled by default).</entry>
+ <entry>auto</entry>
+ </row>
+ <row>
+ <entry>javax.faces.validator.DISABLE _DEFAULT_BEAN_VALIDATOR</entry>
+ <entry>2.0</entry>
+ <entry>If "true", disable JSR-303 Bean Validation.</entry>
+ <entry>false</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ <section id="mojarra.config.params">
+ <title>Mojarra Context Params</title>
+ <para>
+ These context params are only valid when using Mojarra JSF.
+ </para>
+ <table>
+ <tgroup cols="4">
+ <colspec colnum="1" colname="col1" colwidth="6*"/>
+ <colspec colnum="2" colname="col2" colwidth="1*"/>
+ <colspec colnum="3" colname="col3" colwidth="4*"/>
+ <colspec colnum="4" colname="col4" colwidth="3*"/>
+ <thead>
+ <row>
+ <entry>Context Param</entry>
+ <entry>Impl Ver</entry>
+ <entry>Description</entry>
+ <entry>Default Value</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>com.sun.faces. numberOfViewsInSession</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>For server state-saving, how many views, per logical view, can be stored in the session before oldest is removed?</entry>
+ <entry>15</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.numberOfLogicalViews</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>For server state-saving, how many logical views are allowed before oldest is removed?</entry>
+ <entry>15</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.preferXHTML</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Set xhtml as the content type for browsers that support it.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.compressViewState</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Compress the view after serialization but before encoding.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.disableVersionTracking</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>If true, don't allow JSF 1.1 implementations of certain interfaces.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.sendPoweredByHeader</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>If true, send a header with the JSF spec level.</entry>
+ <entry>true</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.verifyObjects</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>If true, verify all JSF artifacts (such as managed beans) can be instantiated during initialization.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.validateXml</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>If true, perform XML validation on config files.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.displayConfiguration</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>If true, log the values of all Mojarra and JSF context params.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.injectionProvider</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Replace the default InjectionProvider implementation. By default this is set by JBoss AS6.</entry>
+ <entry>org.jboss.web .jsf.integration .injection .JBossDelegatingInjectionProvider</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.injectionProvider</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Replace the default SerializationProvider implementation.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.responseBufferSize</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Buffer size for writing most generated content.</entry>
+ <entry>4096</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. clientStateWriteBufferSize</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Buffer size for writing client state.</entry>
+ <entry>8192</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.compressJavaScript</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Remove whitespace from javascript used in standard JSF components.</entry>
+ <entry>true</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.externalizeJavaScript</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Allow browsers to cache javascript used in standard JSF components.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.enableJSStyleHiding</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Hide javascript from older browser implementations.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.writeStateAtFormEnd</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Controls if view state is written after opening a form tag (false) or closing a form tag (true).</entry>
+ <entry>true</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. enableLazyBeanValidation</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>If false, examine managed beans at startup. Otherwise, validate when referenced/created.</entry>
+ <entry>true</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. enabledLoadBundle11Compatibility</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Preserve JSF 1.1 behavior of f:loadBundle.
+ <ulink url="https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=577">See issue here.</ulink></entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.clientStateTimeout</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Time in seconds that client state is considered valid. If a request is received after timeout expired, ViewExpiredException is thrown.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.serializeServerState</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>If true, serialize server-side component state.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. enableViewStateIdRendering</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>If false, don't render id attribute on javax.faces.ViewState hidden field.
+ <ulink url="https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=433">See issue here.</ulink></entry>
+ <entry>true</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. enableScriptsInAttributeValues</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>If false, don't allow attribute values with "javascirpt:" or "script:".</entry>
+ <entry>true</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.disableUnicodeEscaping</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>"false", "true", or "auto". If "auto", escaping depends on response encoding.
+ <ulink url="https://javaserverfaces.dev.java.net/issues/show_bug.cgi?id=751">See issue here.</ulink></entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.developmentMode</entry>
+ <entry>1.2</entry>
+ <entry>If true, reload Groovy and faces-config files when edited.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. enableMultiThreadedStartup</entry>
+ <entry>1.2</entry>
+ <entry>If false, don't create worker threads at startup.</entry>
+ <entry>true</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.enableThreading</entry>
+ <entry>2.0</entry>
+ <entry>If false, don't create worker threads at startup.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.resourceBufferSize</entry>
+ <entry>2.0</entry>
+ <entry>Read buffer size, in bytes, used by the default ResourceHandler implementation.</entry>
+ <entry>2048</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.defaultResourceMaxAge</entry>
+ <entry>2.0</entry>
+ <entry>Time in milliseconds that a resource from the ResourceHandler will be cached via an "Expires" response header. No caching if ProjectStage is "Development".</entry>
+ <entry>604800</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. resourceUpdateCheckPeriod</entry>
+ <entry>2.0</entry>
+ <entry>Frequency in minutes to check for changes to webapp artifacts that contain resources.
+ 0 means never check for changes.
+ -1 means always perform a new lookup when finding resources.</entry>
+ <entry>5</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.compressableMimeTypes</entry>
+ <entry>2.0</entry>
+ <entry>Comma-seperated list of compressable mime types. No compression if ProjectStage is "Development"</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.expressionFactory</entry>
+ <entry>2.0</entry>
+ <entry>Expression factory implementation class.</entry>
+ <entry>com.sun.el .ExpressionFactoryImpl</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.duplicateJARPattern</entry>
+ <entry>1.2 and 2.0</entry>
+ <entry>Regular expression to determine if two URLs point to the same jar. Set by JBoss JSF Deployer.</entry>
+ <entry>^tmp\d+(\S*\.jar)</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.faceletFactory</entry>
+ <entry>2.0</entry>
+ <entry>Set the FaceletFactory impl class.</entry>
+ <entry>null</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.enableHtmlTagLibValidator</entry>
+ <entry>2.0</entry>
+ <entry>Enable validation of standard Html TagLibs.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.enableCoreTagLibValidator</entry>
+ <entry>2.0</entry>
+ <entry>Enable validation of standard Core TagLibs.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. registerConverterPropertyEditors</entry>
+ <entry>2.0</entry>
+ <entry>If true, allow EL Coercion to use JSF Custom converters.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.enableGroovyScripting</entry>
+ <entry>2.0</entry>
+ <entry>If true, allow Groovy.</entry>
+ <entry>false</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. generateUniqueServerStateIds</entry>
+ <entry>2.0</entry>
+ <entry>If true, generate random server state Ids. If false, create Ids sequentially.</entry>
+ <entry>true</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces. autoCompleteOffOnViewState</entry>
+ <entry>2.0</entry>
+ <entry>If false, don't use autocomplete="off" when saving view state.</entry>
+ <entry>true</entry>
+ </row>
+ <row>
+ <entry>com.sun.faces.allowTextChildren</entry>
+ <entry>2.0</entry>
+ <entry>If true, allow children of h:inputText and h:outputText to be rendered.
+ In 1.2, they would always be rendered before the value of tag.
+ In 2.0, they will not be rendered at all unless this flag is set.</entry>
+ <entry>false</entry>
+ </row>
+
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+
+ <section id="jboss.jsf.config.params">
+ <title>JBoss JSF Context Params</title>
+ <para>
+ These context params are explained more in Chapter 3.
+ </para>
+ <table>
+ <tgroup cols="3">
+ <colspec colnum="1" colname="col1" colwidth="8*"/>
+ <colspec colnum="2" colname="col2" colwidth="4*"/>
+ <colspec colnum="3" colname="col3" colwidth="2*"/>
+ <thead>
+ <row>
+ <entry>Context Param</entry>
+ <entry>Description</entry>
+ <entry>Default Value</entry>
+ </row>
+ </thead>
+ <tbody>
+ <row>
+ <entry>org.jboss.jbossfaces.JSF_CONFIG_NAME</entry>
+ <entry>The name of the JSF Configuration to use for this WAR.</entry>
+ <entry>Mojarra-2.0</entry>
+ </row>
+ <row>
+ <entry>org.jboss.jbossfaces.WAR_BUNDLES_JSF_IMPL</entry>
+ <entry>If true, allow WAR to use the JSF implementation found in WEB-INF/lib.</entry>
+ <entry>false</entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+ </section>
+ </chapter>
+
Added: projects/docs/community/6/JSF_Guide/en-US/JSF_Quick_Start.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/JSF_Quick_Start.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/en-US/JSF_Quick_Start.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,100 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN" "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd">
+
+ <chapter id="quickstart.chapt">
+ <title>Quick Start</title>
+
+ <para>
+ In this chapter, we demonstrate the world's simplest JSF "Hello World" application.
+ </para>
+
+ <section id="dir-structure">
+ <title>Create your WAR structure</title>
+ <para>
+ Go to your <filename>JBOSS_HOME/server/default/deploy</filename> directory and create these two subdirectories:
+ </para>
+
+ <itemizedlist>
+ <listitem><filename>hellojsf.war</filename></listitem>
+ <listitem><filename>hellojsf.war/WEB-INF</filename></listitem>
+ </itemizedlist>
+
+ </section>
+ <section id="web-xml">
+ <title>Create a minimal web.xml</title>
+ <para>
+ This <filename>web.xml</filename> only needs the minimum
+ declarations shown below. Place the file in <filename>/WEB-INF</filename>.
+ </para>
+
+ <programlisting><![CDATA[<?xml version="1.0"?>
+<web-app>
+</web-app>]]>
+ </programlisting>
+ <note>
+ 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>
+ <para>
+ Create an empty <filename>faces-config.xml</filename> file and place it in <filename>/WEB-INF</filename>.
+ </para>
+ <para>
+ The faces-config.xml file can be completely empty. It 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>
+ </section>
+
+ <section id="jsf-markup">
+ <title>Create Your JSF Markup</title>
+ <para>
+ We will use a single facelet. Create the file <filename>index.xhtml</filename>
+ and put it in your <filename>deploy/hellojsf.war</filename> directory.
+ </para>
+ <para>
+ We use a little JSF2/EL 2.2 trick to avoid the need for a backing bean. We can
+ grab the input value directly from the request object using a parameterized EL
+ expression.
+ </para>
+ <programlisting><![CDATA[<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml"
+ xmlns:h="http://java.sun.com/jsf/html"
+ xmlns:f="http://java.sun.com/jsf/core">
+
+ <f:view>
+ <h:form id="form1">
+ <h:outputText value="Enter Your Name:"/>
+ <h:inputText id="name"/>
+ <h:commandButton value="Submit" />
+ </h:form>
+ <h:outputText rendered="#{not empty request.getParameter('form1:name')}"
+ value=" Hello #{request.getParameter('form1:name')}"/>
+ </f:view>
+
+</html>]]>
+ </programlisting>
+ </section>
+
+ <section id="run-the-app">
+ <title>Run the application</title>
+ <para>
+ Now we're done! We only needed three files and two of those were
+ just placeholders.
+ </para>
+ <para>
+ Start JBoss AS6 and put any of the following URLs into your browswer:
+ </para>
+ <itemizedlist>
+ <listitem><ulink url="http://localhost:8080/hellojsf/index.jsf">http://localhost:8080/hellojsf/index.jsf</ulink></listitem>
+ <listitem><ulink url="http://localhost:8080/hellojsf/index.faces">http://localhost:8080/hellojsf/index.faces</ulink></listitem>
+ <listitem><ulink url="http://localhost:8080/hellojsf/faces/index.xhtml">http://localhost:8080/hellojsf/faces/index.xhtml</ulink></listitem>
+ </itemizedlist>
+ </section>
+ </chapter>
+
Added: projects/docs/community/6/JSF_Guide/en-US/Legal_Notice.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/en-US/Legal_Notice.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/en-US/Legal_Notice.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,17 @@
+<?xml version='1.0'?>
+<!DOCTYPE legalnotice PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
+]>
+
+<legalnotice id="Book-Legal_Notice">
+ <title>Legal Notice</title>
+ <para>
+ <address>
+ <street>1801 Varsity Drive</street>
+ <city>Raleigh</city>, <state>NC</state><postcode>27606-2072</postcode><country>USA</country><phone>Phone: +1 919 754 3700</phone>
+ <phone>Phone: 888 733 4281</phone>
+ <fax>Fax: +1 919 754 3701</fax>
+ <pob>PO Box 13588</pob><city>Research Triangle Park</city>, <state>NC</state><postcode>27709</postcode><country>USA</country>
+ </address>
+ </para>
+</legalnotice>
+
Added: projects/docs/community/6/JSF_Guide/pom.xml
===================================================================
--- projects/docs/community/6/JSF_Guide/pom.xml (rev 0)
+++ projects/docs/community/6/JSF_Guide/pom.xml 2010-08-26 23:47:34 UTC (rev 107821)
@@ -0,0 +1,107 @@
+<project xmlns="http://maven.apache.org/POM/4.0.0"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
+ xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
+
+ <modelVersion>4.0.0</modelVersion>
+
+ <groupId>org.jboss.jbossas</groupId>
+ <artifactId>jsf-guide-${translation}</artifactId>
+ <version>1.0-SNAPSHOT</version>
+ <packaging>jdocbook</packaging>
+ <name>JSF Guide (${translation})</name>
+
+ <build>
+ <plugins>
+ <plugin>
+ <groupId>org.jboss.maven.plugins</groupId>
+ <artifactId>maven-jdocbook-plugin</artifactId>
+ <version>2.1.2</version>
+ <extensions>true</extensions>
+ <dependencies>
+ <dependency>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-docbook-xslt</artifactId>
+ <version>1.1.0</version>
+ </dependency>
+ <dependency>
+ <groupId>org.jboss</groupId>
+ <artifactId>jbossorg-jdocbook-style</artifactId>
+ <version>1.0.0</version>
+ <type>jdocbook-style</type>
+ </dependency>
+ </dependencies>
+ <configuration>
+ <!--minmemory>1024m</minmemory>
+ <maxmemory>1024m</maxmemory -->
+ <sourceDocumentName>JSF_Guide.xml</sourceDocumentName>
+ <sourceDirectory>en-US</sourceDirectory>
+ <imageResource>
+ <directory>en-US</directory>
+ <includes>
+ <include>images/*</include>
+ </includes>
+ </imageResource>
+ <!-- <cssResource>
+ <directory>src/main/css</directory>
+ </cssResource> -->
+ <!--put back css -->
+
+ <formats>
+ <format>
+ <formatName>pdf</formatName>
+ <!--<stylesheetResource>classpath:/xslt/org/jboss/main-pdf.xsl</stylesheetResource>-->
+ <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource>
+ <finalName>JSF_Guide.pdf</finalName>
+ </format>
+ <format>
+ <formatName>html</formatName>
+ <!--<stylesheetResource>classpath:/xslt/org/jboss/main-html.xsl</stylesheetResource>-->
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+
+ <format>
+ <formatName>html_single</formatName>
+ <!--<stylesheetResource>classpath:/xslt/org/jboss/nochunk-html.xsl</stylesheetResource>-->
+ <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>
+
+ <!--<format>
+ <formatName>eclipse</formatName>
+ <stylesheetResource>classpath:/xslt/main-eclipse.xsl</stylesheetResource>
+ <finalName>index.html</finalName>
+ </format>-->
+ </formats>
+ <options>
+ <xincludeSupported>true</xincludeSupported>
+ <!-- <xmlTransformerType>saxon</xmlTransformerType>-->
+ <!-- needed for uri-resolvers; can be ommitted if using 'current' uri scheme -->
+ <!-- could also locate the docbook dependency and inspect its version... -->
+ <!--docbookVersion>1.72.0</docbookVersion -->
+ <!--
+ <docbookVersion>1.72.0</docbookVersion>
+ <transformerParameters>
+ <property>
+ <name>javax.xml.parsers.DocumentBuilderFactory</name>
+ <value>org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</value>
+ </property>
+ <property>
+ <name>javax.xml.parsers.SAXParserFactory</name>
+ <value>org.apache.xerces.jaxp.SAXParserFactoryImpl</value>
+ </property>
+ -->
+ <!--<javax.xml.parsers.DocumentBuilderFactory>org.apache.xerces.jaxp.DocumentBuilderFactoryImpl</javax.xml.parsers.DocumentBuilderFactory>
+ <javax.xml.parsers.SAXParserFactory>org.apache.xerces.jaxp.SAXParserFactoryImpl</javax.xml.parsers.SAXParserFactory>
+ <javax.xml.validation.SchemaFactory:http\://www.w3.org/2001/XMLSchema>org.apache.xerces.jaxp.validation.XMLSchemaFactory</javax.xml.validation.SchemaFactory:http\://www.w3.org/2001/XMLSchema>-->
+ <!-- </transformerParameters> -->
+ </options>
+ </configuration>
+ </plugin>
+</plugins>
+</build>
+
+<properties>
+ <translation>en-US</translation>
+</properties>
+</project>
More information about the jboss-cvs-commits
mailing list