[jbosstools-commits] JBoss Tools SVN: r32980 - in branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide: en-US and 2 other directories.

Author: irooskov(a)redhat.com Date: 2011-07-17 22:19:56 -0400 (Sun, 17 Jul 2011) New Revision: 32980 Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Book_Info.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Feedback.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/JSF_Tools_Reference_Guide.ent branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/JSF_Tools_Reference_Guide.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Preface.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Revision_History.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/creation_and_registration.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_10.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_11.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_12.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_14.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_15.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_16.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_17.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_18.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_19.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_2.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_20.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_20_1.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_20_2.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_21.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_22.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_23.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24a.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24b.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24c.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24d.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26a.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26b.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26c.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26d.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_27.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_28.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_29.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_3.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_30.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_31.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_32.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_34.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_35.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_36.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_37.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_38.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_39.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_4.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_40.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_42.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_43.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_44.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_45.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_46.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_47.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_48.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_49.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_5.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_50.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_51.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_52.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_53.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_54.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_55.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_56.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_57.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_58.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_59.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_1.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_2.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_3.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_4.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_5.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_6.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_7.png branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/introduction.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_config_file.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_project_verification.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_support.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/managed_beans.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/master.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/projects.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/webxml_editor.xml branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/pom.xml Log: updated for GA Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Book_Info.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Book_Info.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Book_Info.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -5,9 +5,9 @@ <title>JSF Tools Reference Guide</title> <subtitle>Provides information relating to the JSF Tools module.</subtitle> <productname>JBoss Developer Studio</productname> - <productnumber>4.0</productnumber> - <edition>4.0.0</edition> - <pubsnumber>4</pubsnumber> + <productnumber>4.1</productnumber> + <edition>4.1.0</edition> + <pubsnumber>1</pubsnumber> <abstract> <para>The JSF Tools Reference Guide explains how to use the JSF Tools module to develop JSF applications.</para> </abstract> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Feedback.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Feedback.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Feedback.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -1,20 +1,92 @@ <?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +<!ENTITY % BOOK_ENTITIES SYSTEM "../Document_Conventions.ent"> +%BOOK_ENTITIES; +]> +<appendix id="sect_JBoss-Getting_Help_and_Giving_Feedback" lang="en-US"> + <title>Getting Help and Giving Feedback</title> + <section id="sect_JBoss-Do_You_Need_Help"> + <title>Do You Need Help?</title> + <indexterm> + <primary>help</primary> + <secondary>getting help</secondary> -<section id="sect-Beginners_Guide-We_Need_Feedback" lang="en-US"> - <title>We Need Feedback!</title> - <indexterm> - <primary>feedback</primary> - <secondary>contact information for this manual</secondary> - </indexterm> - <para> - If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in JIRA against JBoss Developer Studio: <ulink url="https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=1231050... - </para> - <para> - When submitting a bug report, be sure to mention the manual's name and to select the "documentation" component. - </para> - <para> - If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, please include the section number and some of the surrounding text so we can find it easily. - </para> -</section> + </indexterm> + <para> + If you experience difficulty with a procedure described in this documentation, visit the Red Hat Customer Portal at <ulink url="http://access.redhat.com" />. Through the customer portal, you can: + </para> + <itemizedlist> + <listitem> + <para> + search or browse through a knowledgebase of technical support articles about Red Hat products. + </para> + </listitem> + <listitem> + <para> + submit a support case to Red Hat Global Support Services (GSS). + </para> + </listitem> + <listitem> + <para> + access other product documentation. + </para> + + </listitem> + + </itemizedlist> + <para> + Red Hat also hosts a large number of electronic mailing lists for discussion of Red Hat software and technology. You can find a list of publicly available mailing lists at <ulink url="https://www.redhat.com/mailman/listinfo" />. Click on the name of any mailing list to subscribe to that list or to access the list archives. + </para> + + </section> + + <section id="jboss-feedback"> + <title>Give us Feedback</title> + <!-- NOTE: You will need the following entities defined in your .ent file. + You will need to replace _YOUR_PRODUCT_HERE_, _YOUR_COMPONENT_ + and _YOUR_SUMMARY_ - entities are not replaced in URLs. + <!ENTITY PRODUCT "JBoss Product Name"> + <!ENTITY BZCOMPONENT "doc-triage"> + <!ENTITY BZURL "<ulink url='https://bugzilla.example.com/enter_bug.cgi?product=_YOUR_PRODUCT... + + These entities should not affect translated documents, since Bugzilla is not localised. + --> <indexterm> + <primary>feedback</primary> + <secondary>contact information for this manual</secondary> + + </indexterm> + <para> + If you find a typographical error, or know how this guide can be improved, we would love to hear from you. Submit a report in Bugzilla against the product <literal>&BZPRODUCT;</literal> and the component <literal>&BZCOMPONENT;</literal>. The following link will take you to a pre-filled bug report for this product: &BZURL;. + </para> + <para> + Fill out the following template in Bugzilla's <literal>Description</literal> field. Be as specific as possible when describing the issue; this will help ensure that we can fix it quickly. + </para> + +<screen>Document URL: + + +Section Number and Name: + + +Describe the issue: + + +Suggestions for improvement: + + +Additional information: + + +</screen> + <para> + Be sure to give us your name so that you can receive full credit for reporting the issue. + </para> + + </section> + + +</appendix> + + Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/JSF_Tools_Reference_Guide.ent =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/JSF_Tools_Reference_Guide.ent 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/JSF_Tools_Reference_Guide.ent 2011-07-18 02:19:56 UTC (rev 32980) @@ -1,4 +1,7 @@ <!ENTITY PRODUCT "JBoss"> <!ENTITY BOOKID "JSF_Tools_Reference_Guide"> -<!ENTITY YEAR "2010"> +<!ENTITY YEAR "2011"> <!ENTITY HOLDER "Red Hat"> +<!ENTITY BZPRODUCT "JBoss Developer Studio"> +<!ENTITY BZCOMPONENT "JSF Tools Reference Guide"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&perc... Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/JSF_Tools_Reference_Guide.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/JSF_Tools_Reference_Guide.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/JSF_Tools_Reference_Guide.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -12,5 +12,6 @@ <xi:include href="managed_beans.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="creation_and_registration.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="jsf_project_verification.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +<xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> </book> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Preface.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Preface.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Preface.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -8,9 +8,5 @@ <para> This manual uses several conventions to highlight certain words and phrases and draw attention to specific pieces of information. To get more information on these conventions please refer to the <guilabel>Document Conventions</guilabel> manual, which can be found on the <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/index.... Hat Documentation</ulink> website under the <guilabel>JBoss Developer Studio</guilabel> section. </para> - <!--<xi:include href="Common_Content/Conventions.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - <xi:include href="Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude"><xi:fallback xmlns:xi="http://www.w3.org/2001/XInclude"><xi:include href="Common_Content/Feedback.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> - </xi:fallback> - </xi:include>--> </preface> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Revision_History.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Revision_History.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/Revision_History.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -2,31 +2,51 @@ <!DOCTYPE Book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ ]> <appendix> - <title>Revision History</title> - <simpara> - <revhistory> - <revision> - <revnumber>1</revnumber><date>Wed Jun 09 2010</date> - <author> - <firstname>JBoss Tools</firstname><surname>Documentation Team&lt;/surname&gt;&lt;email&gt;irooskov(a)redhat.com&lt;/email&gt; - </author> - <revdescription> - <simplelist> - <member>General updates</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>0</revnumber><date>Fri Nov 20 2009</date> - <author> - <firstname&gt;Isaac&lt;/firstname&gt;&lt;surname&gt;Rooskov&lt;/surname&gt;&lt;email&gt;irooskov(a)redhat.com&lt;/email&gt; - </author> - <revdescription> - <simplelist> - <member>Initial creation of book by publican</member> - </simplelist> - </revdescription> - </revision> - </revhistory> - </simpara> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>1-1</revnumber> + <date>Tue Mar 15 2011</date> + <author> + <firstname>Matthew</firstname> + <surname>Casperson</surname> + <email&gt;mcaspers(a)redhat.com&lt;/email&gt; + </author> + <revdescription> + <simplelist> + <member>Screenshot refresh</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>1-0</revnumber> + <date>Wed Jun 09 2010</date> + <author> + <firstname>JBoss Tools</firstname> + <surname>Documentation Team</surname> + <email&gt;irooskov(a)redhat.com&lt;/email&gt; + </author> + <revdescription> + <simplelist> + <member>General updates</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>0-0</revnumber> + <date>Fri Nov 20 2009</date> + <author> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + <email&gt;irooskov(a)redhat.com&lt;/email&gt; + </author> + <revdescription> + <simplelist> + <member>Initial creation of book by publican</member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </simpara> </appendix> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/creation_and_registration.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/creation_and_registration.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/creation_and_registration.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -1,364 +1,272 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="creation_and_registration"> - <?dbhtml filename="creation_and_registration.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Developer Studio</keyword> - <keyword>Eclipse</keyword> - <keyword>JSF Tools</keyword> - <keyword>Java</keyword> - <keyword>JBoss</keyword> - </keywordset> - </chapterinfo> - <title>Creation and Registration</title> - - <section id="CreateAndRegisterACustomConverter94230"> - - <title>Create and Register a Custom Converter</title> - - <para>It&apos;s also possible to create a - custom Converter in order to specify your own converting rules. Let&apos;s look at how you can do this.</para> - - <para>To create and register a custom converter it&apos;s necessary to - go through the following steps:</para> - - <itemizedlist> - <listitem> - <para>In the Project Explorer view open <emphasis> - <property>faces-config.xml</property> - </emphasis> and select <emphasis> - <property>Tree</property> - </emphasis> tab.</para> - </listitem> - </itemizedlist> - <figure> - <title>Converters</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_44.png" scale="80" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>Select <emphasis> - <property>Converters</property> - </emphasis> and click on<emphasis> - <property> Add</property> - </emphasis> button.</para> - </listitem> - <listitem> - <para>On the form type the name of your converter in the <emphasis> - <property>Converter-id</property> - </emphasis> field and name of the class for - converters. After clicking <emphasis> - <property>Finish</property> - </emphasis> button your custom converter is - registered under the entered name.</para> - </listitem> - </itemizedlist> - <figure> - <title>Add Converter Form</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_45.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>Now you can create <emphasis role="italic"> - <property>&quot;converter&quot;</property> - </emphasis> class. In the Converter section you - should see your <emphasis> - <property>Converter-id</property> - </emphasis> and - <emphasis><property>Converter-class</property>.</emphasis> - Click on <emphasis> - <property>Converter-class</property> - </emphasis> to generate the source code.</para> - </listitem> - </itemizedlist> - <figure> - <title>Generation of Source Code for Converter Class</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_46.png" scale="80" - /> - </imageobject> - </mediaobject> - </figure> - - <itemizedlist> - <listitem> - <para>A usual wizard for creating a Java class will appear. - All needed fields here will be adjusted - automatically. Just leave everything without changes - and click <emphasis> - <property>Finish</property>. - </emphasis></para> - </listitem> - </itemizedlist> - <figure> - <title>New Java Class Form</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_47.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>To open a converter class click again on <emphasis> - <property>Converter-class</property> - </emphasis> link in the Converter section.</para> - </listitem> - </itemizedlist> - <figure> - <title>Converter Class</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_48.png" - /> - </imageobject> - </mediaobject> - </figure> - <para>Now you - are able to add a business logic of converter in the - Java editor.</para> - </section> - - <section id="CreateAndRegisterACustomValidator5632"> - - <title>Create and Register a Custom Validator</title> - - <para>It&apos;s also quite easy to develop your - own custom Validators. You should perform the actions similar to the - previous one. Go through the following steps:</para> - <itemizedlist> - <listitem> - <para>In the Project Explorer view open<emphasis> - <property> faces-config.xml</property> - </emphasis> and select <emphasis> - <property>Tree </property> - </emphasis>tab.</para> - </listitem> - </itemizedlist> - <figure> - <title>Validator in Faces Config Editor</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_49.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>Select <emphasis> - <property>Validators</property> - </emphasis> and click on <emphasis> - <property>Add </property> - </emphasis>button.</para> - </listitem> - <listitem> - <para>Type the name of your validator in the <emphasis> - <property>Validator-id</property> - </emphasis> field and name of the class for - validators. After clicking <emphasis> - <property>Finish</property> - </emphasis> button your custom validator is - registered under the entered name.</para> - </listitem> - </itemizedlist> - <figure> - <title>Adding Validator</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_50.png" - /> - </imageobject> - </mediaobject> - </figure> - - <para>Now you can create the &quot;validator&quot; class. </para> - <itemizedlist> - <listitem> - <para>In the Validator section you can see your <emphasis> - <property>Validator-id</property> - </emphasis> and <emphasis> - <property>Validator-class</property></emphasis>. To generate the source code click on <emphasis> - <property>Validator-class</property>. - </emphasis></para> - </listitem> - </itemizedlist> - <figure> - <title>Creating Validator Class</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_51.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>Java class will be created automatically. Leave - everything without changes and click <emphasis> - <property>Finish</property>. - </emphasis></para> - </listitem> - </itemizedlist> - <figure> - <title>New Java Class Form</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_52.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>To open validator class click again on <emphasis> - <property>Validator-Class</property> - </emphasis> link in the Validator section. Now you - are able to write a business logic of validator in - the Java editor.</para> - </listitem> - </itemizedlist> - <figure> - <title>Converter Class Editing</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_53.png" - /> - </imageobject> - </mediaobject> - </figure> - </section> - - <section id="referenced_beans"> - <title>Create and Register Referenced Beans</title> - - <para>Creation of Referenced Beans is similar to creation of Custom - Validator as well. To perform this, let&apos;s walk through the necessary steps.</para> - - <itemizedlist> - <listitem> - <para>In the Project Explorer view open<emphasis> - <property> faces-config.xml</property> - </emphasis> and select <emphasis> - <property>Tree </property> - </emphasis>tab.</para> - </listitem> - </itemizedlist> - <figure> - <title>Referenced Beans in Faces Config Editor</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_54.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>Select <emphasis> - <property>Referenced Beans</property> - </emphasis> and click on <emphasis> - <property>Add</property> - </emphasis> button.</para> - </listitem> - <listitem> - <para>Type in the name of your Referenced Bean and type in - or select <emphasis> - <property>Referenced-Bean-Class</property> - </emphasis> by using <emphasis> - <property>Browse</property> - </emphasis> button.</para> - </listitem> - </itemizedlist> - <figure> - <title>Add Referenced Bean</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_55.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>In the Referenced Bean section you should see your <emphasis> - <property>Referenced-Bean-Name</property> - </emphasis> and - <emphasis><property>Referenced-Bean-Class</property>.</emphasis> - Click on the link to open the Java creation - wizard.</para> - </listitem> - </itemizedlist> - <figure> - <title>Create Referenced Bean Class</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_56.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>Java class will be created automatically. Leave - everything without changes and click <emphasis> - <property>Finish</property>. - </emphasis></para> - </listitem> - </itemizedlist> - <figure> - <title>New Java Class Form</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_57.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>To open Referenced Bean class click again on <emphasis> - <property>Referenced-Bean-Class</property> - </emphasis> in the Referenced Bean section. Now you - are able to write business logic of Referenced Bean - in the Java editor.</para> - </listitem> - </itemizedlist> - <figure> - <title>Referenced Bean Class Editing</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_58.png" - /> - </imageobject> - </mediaobject> - </figure> - </section> + <?dbhtml filename="creation_and_registration.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>JSF Tools</keyword> + <keyword>Java</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> + <title>Creation and Registration</title> + + <section id="CreateAndRegisterACustomConverter94230"> + + <title>Create and Register a Custom Converter</title> + + <para> + It&apos;s also possible to create a custom Converter in order to specify your own converting rules. Let&apos;s look at how you can do this. + </para> + + <para>To create and register a custom converter it is necessary perform the following steps:</para> + + <itemizedlist> + <listitem> + <para>In the Project Explorer view open the <filename>faces-config.xml</filename> file and select <guilabel>Tree</guilabel> tab.</para> + </listitem> + </itemizedlist> + <figure> + <title>Converters</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_44.png" scale="80" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>Select <guilabel>Converters</guilabel> and click the <guibutton>Add</guibutton> button.</para> + </listitem> + <listitem> + <para> + On the form type the name of your converter in the <emphasis><property>Converter-id</property></emphasis> field and name of the class for converters. After clicking <guibutton>Finish</guibutton> button your custom converter is registered under the entered name. + </para> + </listitem> + </itemizedlist> + <figure> + <title>Add Converter Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_45.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para> + Now you can create a <emphasis role="italic"><property>&quot;converter&quot;</property></emphasis> class. In the Converter section you should see your <guilabel>Converter-id</guilabel> and <guilabel>Converter-class</guilabel>. Click on the <guilabel>Converter-Class</guilabel> link to generate the source code. + </para> + </listitem> + </itemizedlist> + <figure> + <title>Generation of Source Code for Converter Class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_46.png" scale="80" /> + </imageobject> + </mediaobject> + </figure> + + <itemizedlist> + <listitem> + <para> + A usual wizard for creating a Java class will appear. All needed fields here will be adjusted automatically. Just leave everything without changes and click the <guibutton>Finish</guibutton> button. + </para> + </listitem> + </itemizedlist> + <figure> + <title>New Java Class Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_47.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>To open a converter class click again on the <guilabel>Converter-Class</guilabel> link in the Converter section.</para> + </listitem> + </itemizedlist> + <figure> + <title>Converter Class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_48.png" /> + </imageobject> + </mediaobject> + </figure> + <para>Now you are able to add a business logic of converter in the Java editor.</para> + </section> + + <section id="CreateAndRegisterACustomValidator5632"> + + <title>Create and Register a Custom Validator</title> + + <para> + It is also quite easy to develop your own custom Validators. The required steps are similar to those shown previously: + </para> + <itemizedlist> + <listitem> + <para>In the Project Explorer view open the <filename>faces-config.xml</filename> and select the <guilabel>Tree</guilabel> tab.</para> + </listitem> + </itemizedlist> + <figure> + <title>Validator in Faces Config Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_49.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>Select the <guilabel>Validators</guilabel> option and click the <guibutton>Add</guibutton>button.</para> + </listitem> + <listitem> + <para> + Type the name of your validator in the <guibutton>Validator-id</guibutton> field and name of the class for validators. After clicking the <guibutton>Finish</guibutton> button your custom validator is registered under the entered name. + </para> + </listitem> + </itemizedlist> + <figure> + <title>Adding Validator</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_50.png" /> + </imageobject> + </mediaobject> + </figure> + + <para>Now you can create the &quot;validator&quot; class. </para> + <itemizedlist> + <listitem> + <para> + In the Validator section you can see your <guilabel>Validator-id</guilabel> and <guilabel>Validator-class</guilabel>. To generate the source code click on <guilabel>Validator-class</guilabel>. + </para> + </listitem> + </itemizedlist> + <figure> + <title>Creating Validator Class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_51.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>Java class will be created automatically. Leave everything without changes and click the <guibutton>Finish</guibutton>.</para> + </listitem> + </itemizedlist> + <figure> + <title>New Java Class Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_52.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para> + To open the validator class click on the <guilabel>Validator-Class</guilabel> link in the Validator section. Now you are able to write a business logic of validator in the Java editor. + </para> + </listitem> + </itemizedlist> + <figure> + <title>Converter Class Editing</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_53.png" /> + </imageobject> + </mediaobject> + </figure> + </section> + + <section id="referenced_beans"> + <title>Create and Register Referenced Beans</title> + + <para> + The creation of Referenced Beans is similar to the creation of Custom Validators. The steps below show you the steps required to create Referenced Beans. + </para> + + <itemizedlist> + <listitem> + <para>In the Project Explorer view open the <filename>faces-config.xml</filename> and select the <guilabel>Tree</guilabel> tab.</para> + </listitem> + </itemizedlist> + <figure> + <title>Referenced Beans in Faces Config Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_54.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para>Select the <guilabel>Referenced Beans</guilabel> option and click on the <guibutton>Add</guibutton> button.</para> + </listitem> + <listitem> + <para> + Type in the name of your Referenced Bean and type in or select the <guilabel>Referenced-Bean-Class</guilabel> value by clicking the <guibutton>Browse</guibutton> button. + </para> + </listitem> + </itemizedlist> + <figure> + <title>Add Referenced Bean</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_55.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para> + In the Referenced Bean section you should see your <guilabel>Referenced-Bean-Name</guilabel> and <guilabel>Referenced-Bean-Class</guilabel>. Click on the link to open the Java creation wizard. + </para> + </listitem> + </itemizedlist> + <figure> + <title>Create Referenced Bean Class</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_56.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para> + The Java class will be created automatically. Leave everything with their default values and click the <guibutton>Finish</guibutton> button. + </para> + </listitem> + </itemizedlist> + <figure> + <title>New Java Class Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_57.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para> + To open a Referenced Bean class click the <guilabel>Referenced-Bean-Class</guilabel> in the Referenced Bean section. Now you are able to write business logic of Referenced Bean in the Java editor. + </para> + </listitem> + </itemizedlist> + <figure> + <title>Referenced Bean Class Editing</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_58.png" /> + </imageobject> + </mediaobject> + </figure> + </section> </chapter> \ No newline at end of file Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_10.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_11.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_12.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_14.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_15.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_16.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_17.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_18.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_19.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_20.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_20_1.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_20_2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_21.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_22.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_23.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24b.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24c.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_24d.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26b.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26c.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_26d.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_27.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_28.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_29.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_3.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_30.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_31.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_32.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_34.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_35.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_36.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_37.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_38.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_39.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_4.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_40.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_42.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_43.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_44.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_45.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_46.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_47.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_48.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_49.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_5.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_50.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_51.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_52.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_53.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_54.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_55.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_56.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_57.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_58.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/jsf_support/jsf_support_59.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_1.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_3.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_4.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_5.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_6.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/images/verif_valid/verif_valid_7.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/introduction.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/introduction.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/introduction.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -14,18 +14,18 @@ <title>Introduction</title> - <para>JSF Tools are especially designed for supporting JSF and JSF-related technologies. JSF - Tools provide extensible and exemplary tools for building JSF-based applications as well as - adding JSF capabilities to existing web projects, importing JSF projects and choosing any - JSF implementation while developing JSF application.</para> + <para> + JSF Tools are especially designed to support JSF and JSF-related technologies. JSF Tools provide extensible tools for building JSF-based applications as well as adding JSF capabilities to existing web projects, importing JSF projects and choosing any JSF implementation while developing JSF application. + </para> - <para>In this guide we provide you with the information on JSF tooling which allows you to - develop JSF applications much faster and with far fewer errors so sparing your time.</para> + <para> + This guide provides the information on JSF tooling you need to allow you to quickly develop JSF applications with far fewer errors. + </para> <section id="jsf_key_features"> <title>Key Features of JSF Tools</title> - <para>Here, we provide you with a key functionality which is integrated in JSF tooling.</para> + <para>The table below lists the functionality provided by the JSF Tools.</para> <table> <title>Key Functionality for JSF Tools</title> @@ -46,14 +46,15 @@ <row> <entry>JSF and Facelets support</entry> - <entry>Step-by-step wizards for creating new JSF and Facelets projects with a number of predefined templates, importing existing ones and adding JSF capabilities to non-jsf web projects.</entry> + <entry> + Step-by-step wizards for creating new JSF and Facelets projects with a number of predefined templates, importing existing ones and adding JSF capabilities to non-JSF web projects. + </entry> <entry><xref linkend="jsf_support"/></entry> </row> <row> <entry>Flexible and customizable project template management</entry> - <entry>Jump-start development with out-of-the-box templates or easily - customized templates for re-use.</entry> + <entry>Jump-start development with the supplied templates or easily create customized templates for re-use.</entry> <entry> <xref linkend="projects"/> </entry> @@ -61,18 +62,17 @@ <row> <entry>Support for JSF Configuration File</entry> - <entry>Working on file using three modes: diagram, tree and source. - Synchronization between the modes and full control over the code. Easy - moving around the diagram using the Diagram Navigator.</entry> <entry> + Work on a file using three modes: diagram, tree and source. Automatic synchronization between the modes and full control over the code. Easily move around the diagram using the Diagram Navigator. + </entry> + <entry> <xref linkend="jsf_config_file"/> </entry> </row> <row> <entry>Support for Managed Beans</entry> - <entry>Adding new managed beans, generating code for attributes, properties - and getter/setter methods.</entry> + <entry>Adding new managed beans, generating code for attributes, properties and getter/setter methods.</entry> <entry> <xref linkend="managed_beans"/> </entry> @@ -80,8 +80,7 @@ <row> <entry>Support for Custom Converters and Validators</entry> - <entry>Fast creating of custom converters and validators with tree view of - faces-config.xml file.</entry> + <entry>Fast creation of custom converters and validators with a tree view of the <filename>faces-config.xml</filename> file.</entry> <entry> <xref linkend="creation_and_registration"/> </entry> @@ -89,11 +88,10 @@ <row> <entry>Verification and Validation</entry> - <entry>All occuring errors will be immediately reported by verification - feature, no matter in what view you are working. Constant validation and - errors checking allows to catch many of the errors during development - process that significantly reduces development time.</entry> <entry> + All errors will be immediately reported by verification feature, no matter in what view you are working. Constant validation and error checking allows you to catch many of the errors during development process that significantly reduces development time. + </entry> + <entry> <xref linkend="jsf_project_verification"/> </entry> @@ -104,7 +102,7 @@ </section> <section> <title>Other relevant resources on the topic</title> - <para>All JBoss Developer Studio/JBoss Tools release documentation you can find at<ulink url="http://docs.jboss.org/tools/">http://docs.jboss.org/too... in the corresponding release directory.</para> - <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">htt... + <para>All JBoss Developer Studio and JBoss Tools release documentation can be found on the <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/index.... Documentation</ulink> website. </para> + <para>Nightly documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">htt... </section> </chapter> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_config_file.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_config_file.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_config_file.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -1,431 +1,399 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="jsf_config_file" role="updated"> - <?dbhtml filename="jsf_config_file.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Developer Studio</keyword> - <keyword>Eclipse</keyword> - <keyword>JSF Tools</keyword> - <keyword>Java</keyword> - <keyword>JBoss</keyword> - </keywordset> - </chapterinfo> + <?dbhtml filename="jsf_config_file.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>JSF Tools</keyword> + <keyword>Java</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> - <title>JSF Configuration File Editor</title> + <title>JSF Configuration File Editor</title> - <para>First, we should mention that JSF configuration file (<emphasis> - <property>faces-config.xml</property> - </emphasis>) is intended for registering JSF application resources such as Converters, - Validators, Managed Beans and page-to-page navigation rules.</para> - <para>Now, let&apos;s look at how you can easily configure this file by means of a special - graphical editor for JSF configuration file. The editor has three main views:</para> + <para> + First, we should mention that JSF configuration file (<filename>faces-config.xml</filename>) is intended for registering JSF application resources such as Converters, Validators, Managed Beans and page-to-page navigation rules. + </para> + <para> + Now, let&apos;s look at how you can easily configure this file by means of a special graphical editor for the JSF configuration file. The editor has three main views: + </para> - <itemizedlist> - <listitem> - <para>Diagram</para> - </listitem> - <listitem> - <para>Tree</para> - </listitem> - <listitem> - <para>Source</para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para>Diagram</para> + </listitem> + <listitem> + <para>Tree</para> + </listitem> + <listitem> + <para>Source</para> + </listitem> + </itemizedlist> - <para>They can be selected via the tabs at the bottom of the editor.</para> + <para>They can be selected via the tabs at the bottom of the editor.</para> - <section id="Diagram9553"> + <section id="Diagram9553"> - <title>Diagram view</title> + <title>Diagram view</title> - <para>Here, we will show you how to work with JSF configuration file through the Diagram - view of the editor.</para> - <para>As you can see on the figure below, the Diagram view displays the navigation rules in - the faces-config.xml:</para> - <figure> - <title>Diagram View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_21.png"/> - </imageobject> - </mediaobject> - </figure> + <para>Here, we will show you how to work with JSF configuration file through the Diagram view of the editor.</para> + <para>As you can see on the figure below, the Diagram view displays the navigation rules container in the <filename>faces-config.xml</filename> file:</para> + <figure> + <title>Diagram View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_21.png"/> + </imageobject> + </mediaobject> + </figure> - <para>If your diagram is large, make use of the Outline view. Within it you can switch to a <emphasis> - <property>Diagram Navigator</property> - </emphasis> mode by selecting the middle icon at the top of the view window. It allows - you to easily move around the diagram. Just move the blue area in any direction, and the - diagram on the left will also move:</para> - <figure> - <title>Outline View for Diagram</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_32.png" scale="50"/> - </imageobject> - </mediaobject> - </figure> + <para> + If you have a large diagram, make use of the Outline view. Within it you can switch to a <guilabel>Diagram Navigator</guilabel> mode by selecting the middle icon at the top of the view window. This allows you to easily move around the diagram. Just move the blue area in any direction, and the diagram on the left will also move: + </para> + <figure> + <title>Outline View for Diagram</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_32.png" scale="50"/> + </imageobject> + </mediaobject> + </figure> - <para>To create a new page here, you should click the page icon (View Template) on the - toolbar from the left and then click anywhere on the diagram. A New Page Wizard will - appear.</para> + <para> + To create a new page here, you should click the page icon (View Template) on the toolbar from the left and then click anywhere on the diagram. A New Page Wizard will appear. + </para> - <para>To create a transition for connecting pages:</para> + <para>To create a transition for connecting pages:</para> - <itemizedlist> - <listitem> - <para>Select the transition icon from the toolbar (New Connection).</para> - </listitem> - <listitem> - <para>Click the source page.</para> - </listitem> - <listitem> - <para>Click the target page.</para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para>Select the transition icon from the toolbar (New Connection).</para> + </listitem> + <listitem> + <para>Click the source page.</para> + </listitem> + <listitem> + <para>Click the target page.</para> + </listitem> + </itemizedlist> - <para>A transition will appear between the two pages:</para> - <figure> - <title>Transition between JSP Pages</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_22.png"/> - </imageobject> - </mediaobject> - </figure> + <para>A transition will appear between the two pages:</para> + <figure> + <title>Transition between JSP Pages</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_22.png"/> + </imageobject> + </mediaobject> + </figure> - <para>It is also possible to create a new page with context menu by right-clicking anywhere - on the diagram and selecting <emphasis> - <property>Rule...</property></emphasis></para> - <figure> - <title>Creating a New View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_23.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + It is also possible to create a new page with context menu by right-clicking anywhere on the diagram and selecting the <guimenuitem>New View...</guimenuitem> option. + </para> + <figure> + <title>Creating a New View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_23.png"/> + </imageobject> + </mediaobject> + </figure> - <para>To edit an existing transition, first select the transition line. Then, place the - mouse cursor over the last black dot (on the target page). The mouse cursor will change - to a big +. At this point, drag the line to a new target page:</para> - <figure> - <title>Editing Transition between Views</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_24.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section id="TreeView11123" role="updated"> + <para> + To edit an existing transition, first select the transition line. Then, place the mouse cursor over the last black dot (on the target page). The mouse cursor will change to a big +. At this point, drag the line to a new target page: + </para> + <figure> + <title>Editing Transition between Views</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_24.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="TreeView11123" role="updated"> - <title>Tree View</title> + <title>Tree View</title> - <para>You can find it more convenient to edit your JSF Configuration file in the Tree view of - the <property>VPE</property>.</para> + <para>You can find it more convenient to edit your JSF Configuration file in the Tree view of the <guilabel>VPE</guilabel>.</para> - <para>The view displays all JSF application artifacts referenced in the configuration file - in a tree format. By selecting any node on the left, you can see and edit its properties - which will appear in the right-hand area. Let&apos;s look at the structure of this - tree more closely.</para> + <para> + The view displays all JSF application artifacts referenced in the configuration file in a tree format. By selecting any node on the left, you can view and edit its properties which will appear in the right-hand area. Let&apos;s look at the structure of this tree more closely. + </para> - <itemizedlist> - <listitem> - <para>Under the <emphasis> - <property>Application</property> - </emphasis> node you can adjust JSF application specific settings such as - internationalization, possibility to set extensions, add property and variable - resolvers, etc.</para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para> + Under the <guilabel>Application</guilabel> node you can adjust JSF application specific settings such as internationalization, extensions, adding property and variable resolvers, etc. + </para> + </listitem> + </itemizedlist> - <figure> - <title>JSF Application Specific Settings</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_24a.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>JSF Application Specific Settings</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_24a.png"/> + </imageobject> + </mediaobject> + </figure> - <itemizedlist> - <listitem> - <para>The <emphasis> - <property>Components</property> - </emphasis> node is for registering custom JSF components. Right-click and - choose <emphasis> - <property>New > Component</property> - </emphasis> or just press the <emphasis> - <property>Add</property> - </emphasis> button in the right-hand area to add a new component to the JSF - Configuration file.</para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para> + The <guilabel>Components</guilabel> node is for registering custom JSF components. Right-click and select <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>Component</guimenuitem></menuchoice> or just click the <guibutton>Add</guibutton> button in the right-hand area to add a new component to the JSF Configuration file. + </para> + </listitem> + </itemizedlist> - <figure> - <title>Registering a New JSF Component</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_24b.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Registering a New JSF Component</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_24b.png"/> + </imageobject> + </mediaobject> + </figure> - <para>In the <property>Add Component wizard</property> you should set a component - type and point to a component class by using the <emphasis> - <property>Browse</property> - </emphasis> button or create a new class for this component by using the <emphasis> - <property>Component-Class</property> - </emphasis> link.</para> + <para> + In the <guilabel>Add Component</guilabel> wizard you should set a component type and point to a component class by using the <guibutton>Browse</guibutton> button or create a new class for this component by using the <guilabel>Component-Class</guilabel> link. + </para> - <figure> - <title>Adding a New JSF Component to the JSF Configuration File</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_24c.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Adding a New JSF Component to the JSF Configuration File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_24c.png"/> + </imageobject> + </mediaobject> + </figure> - <itemizedlist> - <listitem> - <para>Use the <emphasis> - <property>Render Kit</property> - </emphasis> node to create and register a set of related renderers for custom - JSF components.</para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para>Use the <guilabel>Render Kit</guilabel> node to create and register a set of related renderers for custom JSF components.</para> + </listitem> + </itemizedlist> - <figure> - <title>Adding a New JSF Renderer Kit to the JSF Configuration File</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_24d.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Adding a New JSF Renderer Kit to the JSF Configuration File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_24d.png"/> + </imageobject> + </mediaobject> + </figure> - <itemizedlist> - <listitem> - <para>Under the <emphasis> - <property>Converters</property> - </emphasis> node you can create a converter class for your JSF application - either with id or for a proper class. How to do that see the <xref linkend="CreateAndRegisterACustomConverter94230"/> section.</para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para> + Under the <guilabel>Converters</guilabel> node you can create a converter class for your JSF application either with an id or for a proper class. For more information on this procedure see <xref linkend="CreateAndRegisterACustomConverter94230"/>. + </para> + </listitem> + </itemizedlist> - <figure> - <title>Creating a New Custom Converter</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_59.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Creating a New Custom Converter</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_59.png"/> + </imageobject> + </mediaobject> + </figure> - <itemizedlist> - <listitem> - <para>The <emphasis> - <property>Managed Bean</property> - </emphasis> node is meant for creating and registering Bean classes in your JSF - application. Read more on the topic in the <xref linkend="managed_beans"/> chapter.</para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para> + The <guilabel>Managed Bean</guilabel> node allows you to create and register Bean classes in your JSF application. Read more on the topic in <xref linkend="managed_beans"/>. + </para> + </listitem> + </itemizedlist> - <figure> - <title>Managed Beans</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_26.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Managed Beans</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_26.png"/> + </imageobject> + </mediaobject> + </figure> - <itemizedlist> - <listitem> - <para>Use the <emphasis> - <property>Navigation Rules</property> - </emphasis> node to configure a navigation between the pages in your - application: create a new navigation rule and adjust necessary properties for it - in the right-hand area.</para> - </listitem> - </itemizedlist> - <note> - <title>Tip:</title> - <para>The same you can do in the <xref linkend="Diagram9553"/> of the - JSF Configuration file editor.</para> - </note> + <itemizedlist> + <listitem> + <para> + Use the <guilabel>Navigation Rules</guilabel> node to configure a navigation between the pages in your application. Here you can create a new navigation rule and adjust necessary properties for it in the right-hand area. + </para> + </listitem> + </itemizedlist> + <note> + <title>Tip:</title> + <para>The same you can do in the Diagram view of the JSF Configuration file editor (see <xref linkend="Diagram9553"/>).</para> + </note> - <figure> - <title>Configuring Navigation Rules</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_26a.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Configuring Navigation Rules</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_26a.png"/> + </imageobject> + </mediaobject> + </figure> - <itemizedlist> - <listitem> - <para>Under the <emphasis> - <property>Referenced Beans</property> - </emphasis> node you can add a new Referenced Bean and configure various - properties for it. To learn more on this refer to the <xref - linkend="referenced_beans"/> - section.</para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para> + Under the <guilabel>Referenced Beans</guilabel> node you can add a new Referenced Bean and configure various properties for it. To learn more on this refer to <xref linkend="referenced_beans"/>. + </para> + </listitem> + </itemizedlist> - <figure> - <title>Referenced Beans</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_26b.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Referenced Beans</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_26b.png"/> + </imageobject> + </mediaobject> + </figure> - <itemizedlist> - <listitem> - <para>The <emphasis> - <property>Validators</property> - </emphasis> node is needed to create validator classes for organizing the - validation of your application data. You can read more on the topic in the <xref - linkend="CreateAndRegisterACustomValidator5632"/> section.</para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para> + The <guilabel>Validators</guilabel> node is needed to create validator classes for organizing the validation of your application data. You can read more on the topic in <xref linkend="CreateAndRegisterACustomValidator5632"/>. + </para> + </listitem> + </itemizedlist> - <figure> - <title>Validators</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_26c.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Validators</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_26c.png"/> + </imageobject> + </mediaobject> + </figure> - <itemizedlist> - <listitem> - <para>The <emphasis> - <property>Extensions</property> - </emphasis> node is for setting extensions for your <emphasis> - <property>faces-config.xml</property>.</emphasis></para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para>The <guilabel>Extensions</guilabel> node is for setting extensions in your <filename>faces-config.xml</filename> file. + </para> + </listitem> + </itemizedlist> - <figure> - <title>Adding Extensions</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_26d.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Adding Extensions</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_26d.png"/> + </imageobject> + </mediaobject> + </figure> - <para>In the <property>Tree view</property> you can also edit the properties of the selected - element with the help of the <property>Properties view</property> as shown below:</para> + <para> + In the <guilabel>Tree view</guilabel> you can also edit the properties of the selected element with the help of the <guilabel>Properties view</guilabel> as shown below: + </para> - <figure> - <title>Properties View </title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_33.png" scale="75"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Properties View </title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_33.png" scale="75"/> + </imageobject> + </mediaobject> + </figure> - </section> - <section id="SourceView4643"> + </section> + <section id="SourceView4643"> - <title>Source View</title> + <title>Source View</title> - <para>Here, we&apos;ll discuss how you can configure your faces-config.xml with the help - of Source View.</para> - <para>The Source view for the editor displays a text content of the JSF configuration file. - It is always synchronized with other two views, so any changes made in one of the views - will immediately appear in the other:</para> - <figure> - <title>Source View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_27.png" scale="75"/> - </imageobject> - </mediaobject> - </figure> + <para> + Here, we&apos;ll discuss how you can configure your <filename>faces-config.xml</filename> file with the help of the <guilabel>Source</guilabel> View. + </para> + <para> + The <guilabel>Source</guilabel> View for the editor displays the text content of the JSF configuration file. It is always synchronized with other two views, so any changes made in one of the views will immediately appear in the other: + </para> + <figure> + <title>Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_27.png" scale="75"/> + </imageobject> + </mediaobject> + </figure> - <para>You can also work in the Source view with the help of the <emphasis> - <property>Outline view</property>.</emphasis> The Outline view shows a tree - structure of the JSF configuration file. Simply select any element in the Outline view, - and it will jump to the same place in the Source editor, so you can navigate through the - source code with Outline view.</para> - <figure> - <title>Outline View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_31.png" scale="50"/> - </imageobject> - </mediaobject> - </figure> + <para> + You can also work in the <guilabel>Source</guilabel> View with the help of the <guilabel>Outline</guilabel> View. The <guilabel>Outline view</guilabel> shows a tree structure of the JSF configuration file. Simply select any element in the <guilabel>Outline</guilabel> View, and it will jump to the same place in the Source editor, so you can navigate through the source code with <guilabel>Outline</guilabel> View. + </para> + <figure> + <title>Outline View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_31.png" scale="50"/> + </imageobject> + </mediaobject> + </figure> - </section> + </section> - <section id="jsf_editor_features"> - <title>Editor Features</title> - <para>Here we&apos;ll discuss a very important features that JSF configuration file - editor provides for work with JSF resources.</para> + <section id="jsf_editor_features"> + <title>Editor Features</title> + <para>Here we&apos;ll discuss a very important features that JSF configuration file editor provides when working with JSF resources.</para> - <section id="jsf_openOn"> - <title>Open On</title> - <para>The JSF configuration file editor comes with a very useful OpenOn navigating - feature. More fully you can read about it in our Visual Web Tools - Guide.</para> - </section> + <section id="jsf_openOn"> + <title>Open On</title> + <para> + The JSF configuration file editor comes with the very useful OpenOn navigation feature. You can find more information on this feature in the Visual Web Tools Guide. + </para> + </section> - <section id="ContentAssist976"> + <section id="ContentAssist976"> - <title>Code Assist</title> - <para>Code Assist provides pop-up tip to help you complete your code statements. It - allows you to write your code faster and with more accuracy.</para> - <para>Code assist is always available in the Source mode:</para> - <figure> - <title>Code Assist in Source View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_28.png" scale="65"/> - </imageobject> - </mediaobject> - </figure> + <title>Code Assist</title> + <para> + Code Assist provides a pop-up tip to help you complete your code statements. It allows you to write your code faster and with more accuracy. + </para> + <para>Code assist is always available in the Source mode:</para> + <figure> + <title>Code Assist in Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_28.png" scale="65"/> + </imageobject> + </mediaobject> + </figure> - </section> + </section> - <section id="ErrorReporting3324"> + <section id="ErrorReporting3324"> - <title>Error Reporting</title> - <para>When you are developing your project, error checking is constantly provided. This - greatly reduces your development time as it allows you to catch many of the errors - during development.</para> - <para>Errors will be reported by <xref linkend="jsf_project_verification"/> facility:</para> - <figure> - <title>Error Reporting in Source View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_29.png" scale="75"/> - </imageobject> - </mediaobject> - </figure> + <title>Error Reporting</title> + <para> + Constant error checking is provided while you are developing your project. This greatly reduces your development time as it allows you to catch many errors during the development process. + </para> + <para>Errors will be reported by <xref linkend="jsf_project_verification"/> facility:</para> + <figure> + <title>Error Reporting in Source View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_29.png" scale="75"/> + </imageobject> + </mediaobject> + </figure> - <para>Other errors are also reported.</para> - <figure> - <title>Other Errors Reporting</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_30.png" scale="75"/> - </imageobject> - </mediaobject> - </figure> + <para>Other errors are also reported.</para> + <figure> + <title>Other Errors Reporting</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_30.png" scale="75"/> + </imageobject> + </mediaobject> + </figure> - </section> - </section> + </section> + </section> </chapter> \ No newline at end of file Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_project_verification.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_project_verification.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_project_verification.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -17,11 +17,9 @@ <para>In this chapter we&apos;ll discuss a possible verification that you can take advantage of.</para> <!-- JBoss Developer Studio checks for many different rules for a JSF project --> - <para>Many different rules are checked for a JSF project that can be configured by selecting <emphasis> - <property>Window > Preferences</property> - </emphasis> from the menu bar, selecting <emphasis> - <property>JBoss Tools > Web > Verification</property> - </emphasis> from the Preferences dialog box and then expanding the JSF Rules node.</para> + <para> + Many different rules are checked for a JSF project that can be configured by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem></menuchoice> from the menu bar, selecting <menuchoice><guimenuitem>JBoss Tools</guimenuitem><guimenuitem>Web</guimenuitem><guimenuitem>Verification</guimenuitem></menuchoice> from the Preferences dialog box and then expanding the JSF Rules node. + </para> <figure> <title>JSF Rules</title> <mediaobject> @@ -40,9 +38,9 @@ </mediaobject> </figure> <para>While typing a class name, you might make a minor typo (like <emphasis role="italic"> - <property>&quot;jsfHello.PersonBean9&quot;</property> + <property>&quot;demo.Person9&quot;</property> </emphasis> instead of <emphasis role="italic"> - <property>&quot;jsfHello.PersonBean&quot;</property> + <property>&quot;demo.Person&quot;</property> </emphasis>). After saving the file, verification checks to make sure everything is correct and finds the error below:</para> <figure> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_support.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_support.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/jsf_support.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -1,169 +1,148 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="jsf_support"> - <?dbhtml filename="jsf_support.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Developer Studio</keyword> - <keyword>Eclipse</keyword> - <keyword>JSF Tools</keyword> - <keyword>Java</keyword> - <keyword>JBoss</keyword> - </keywordset> - </chapterinfo> + <?dbhtml filename="jsf_support.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>JSF Tools</keyword> + <keyword>Java</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> - <title>JavaServer Faces Support</title> + <title>JavaServer Faces Support</title> - <para>We don&apos;t lock you into any one <property>JavaServer - Faces</property> implementation. You can always select the one which is - necessary for you while <xref linkend="new_jsf_project"/>, <xref linkend="add_jsf_capability"/> to - any existing Eclipse project or <xref linkend="ImportingExsJSFProjWithAnyStr74447"/> as well.</para> - <para>At this point the special wizard will prompt you to specify a proper JSF environment. - It may be JSF 1.1.02 RI or JSF 1.2 which integrates a number of new features and - changes. The wizard also lets you select JSF implementation with a component - orientation such as JSF 1.2 with Facelets or MyFaces 1.1.4.</para> + <para> + JSF Tools does not lock you into any one <property>JavaServer Faces</property> implementation. You can always specify the desired <property>JavaServer Faces</property> implementation while creating a new JSF project (see <xref linkend="new_jsf_project"/>), adding JSF capability to any existing Eclipse project (see <xref linkend="add_jsf_capability"/>), or importing existing JSF projects (see <xref linkend="ImportingExsJSFProjWithAnyStr74447"/>). + </para> + <para> + At this point the special wizard will prompt you to specify an appropriate JSF environment. It may be <property>JSF 1.1.02 RI</property>, or <property>JSF 1.2</property> which integrates a number of new features and changes. The wizard also lets you select JSF implementation with a component orientation such as <property>JSF 1.2</property> with <property>Facelets</property> or <property>MyFaces 1.1.4</property>. + </para> - <figure> - <title>Choosing JSF Environment</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_11.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Choosing JSF Environment</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_11.png"/> + </imageobject> + </mediaobject> + </figure> - <para>After specifying a proper JSF environment all the required libraries for the selected - version will be added to your project.</para> + <para> + After specifying an appropriate JSF environment, all the required libraries associated with the selected version will be added to your project. + </para> - <section id="FaceletsSupport865"> + <section id="FaceletsSupport865"> - <title>Facelets Support</title> - <para>In this section we will focus more on all concepts that are integrated for - working with Facelets.</para> + <title>Facelets Support</title> + <para>In this section we will focus all the concepts that relate to working with Facelets.</para> - <para>The Facelets extends JavaServer Faces by providing a lightweight framework - that radically simplifies the design of presentation pages for JSF. Facelets can be used in a variety of ways that we - will consider further in this section.</para> + <para> + Facelets extend JavaServer Faces by providing a lightweight framework that radically simplifies the design of JSF presentation pages. Facelets can be used in a variety of ways that we will consider further in this section. + </para> - <section> - <title>Facelets templates</title> - <para>If you want to build an application using Facelets, just create a - project with Facelets based on version 1.2 of the JSF Reference - Implementation, i. e. select the <emphasis> - <property>JSF 1.2 with Facelets</property> - </emphasis> in the JSF Environment section of the New JSF Project - wizard.</para> + <section> + <title>Facelets templates</title> + <para> + If you want to build an application using Facelets, create a project with Facelets based on version 1.2 of the JSF Reference Implementation, i. e. select the <guilabel>JSF 1.2 with Facelets</guilabel> option in the <guilabel>JSF Environment</guilabel> section of the <guilabel>New JSF Project</guilabel> wizard. + </para> - <figure> - <title>Choosing Facelets Environment</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_2.png" - /> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Choosing Facelets Environment</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_2.png"/> + </imageobject> + </mediaobject> + </figure> - <para>Once you&apos;ve selected the environment, it&apos;s possible - to specify the one of three available templates:</para> - <figure> - <title>Choosing Facelets Template</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_3.png" - /> - </imageobject> - </mediaobject> - </figure> - <para>The following table lists possible templates with Facelets for any JSF - project and gives a proper description for each one.</para> - <table> - <title>Facelets Templates</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="2*"/> - <colspec colnum="2" colwidth="3*"/> + <para>Once you have selected the environment, it is possible to specify one of three available templates:</para> + <figure> + <title>Choosing Facelets Template</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_3.png" /> + </imageobject> + </mediaobject> + </figure> + <para>The following table lists the templates that can be used with Facelets for any JSF project, and gives a detailed description for each one.</para> + <table> + <title>Facelets Templates</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="3*"/> - <thead> - <row> - <entry align="center"> - <para>Template</para> - </entry> + <thead> + <row> + <entry align="center"> + <para>Template</para> + </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> - <tbody> + <tbody> - <row> - <entry> - <para> - <emphasis> - <property>FaceletsBlankWithoutLibs</property> - </emphasis> - </para> - </entry> + <row> + <entry> + <para> + <emphasis> + <property>FaceletsBlankWithoutLibs</property> + </emphasis> + </para> + </entry> - <entry> - <para>Some servers already provide - jsf libs and you take risk - of getting conflicting - libraries while deploying - your project. To avoid such - conflicts, use a template - without libs if you have a - server with its own jsf - libraries</para> - </entry> - </row> + <entry> + <para> + Some servers already provide JSF libs and you risk library conflicts while deploying your project. To avoid such conflicts, use a template without libs if you have a server with its own JSF libraries. + </para> + </entry> + </row> - <row> - <entry> - <para> - <emphasis> - <property>FaceletsKickStartWithRILibs</property> - </emphasis> - </para> - </entry> + <row> + <entry> + <para> + <emphasis> + <property>FaceletsKickStartWithRILibs</property> + </emphasis> + </para> + </entry> - <entry> - <para>A sample application with - Facelets that is ready to - run</para> - </entry> - </row> + <entry> + <para> + A sample application with Facelets that is ready to run.</para> + </entry> + </row> - <row> - <entry> - <para> - <emphasis> - <property>FaceletsKickStartWithoutLibs</property> - </emphasis> - </para> - </entry> + <row> + <entry> + <para> + <emphasis> + <property>FaceletsKickStartWithoutLibs</property> + </emphasis> + </para> + </entry> - <entry> - <para>A sample application without - libraries</para> - </entry> - </row> + <entry> + <para>A sample application without libraries.</para> + </entry> + </row> - </tbody> - </tgroup> - </table> - </section> - <section> - <title>Facelets components</title> + </tbody> + </tgroup> + </table> + </section> + <section> + <title>Facelets components</title> - <para>The JBoss Tools - Palette comes with the Facelets components ready to - use. A useful tip appears when you hover the mouse cursor over the - tag, the tip includes a detailed description of the tag component, - the syntax and available attributes.</para> + <para> + The JBoss Tools Palette comes with the Facelets components ready to use. A useful tip appears when you hover the mouse cursor over the tag; this tip includes a detailed description of the tag component, the syntax and available attributes. + </para> <!-- JBoss Developer Studio does not provide templates for MyFaces right out of the box, but you can easily do it yourself with the &quot;Save As Template&quot; feature (available on the File submenu). Just create a small project @@ -172,106 +151,81 @@ How can I add Facelets support to an existing project?</para> <para>A: Right-click on the folder of existing project and select <emphasis>JBoss Tools &gt; Add Custom Capabilities.. &gt; Facelets</emphasis>. </para> --> - <figure> - <title>Facelets Components</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_4.png" - scale="65"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section> - <title>Code assist for Facelets</title> + <figure> + <title>Facelets Components</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_4.png" scale="65"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Code assist for Facelets</title> - <para>One more feature which comes with Facelets support is code assist - (Ctrl + Space). It is available for <property>Facelets - tags</property> while editing <emphasis> - <property>.xhtml</property> - </emphasis> files.</para> + <para> + JSF Tools provides Facelets code assistance, which can be accessed by pressing <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo>. It is available for <property>Facelets tags</property> while editing <filename>.xhtml</filename> files. + </para> - <figure> - <title>XHTML File Code Assist</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_5.png" - scale="60"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>XHTML File Code Assist</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_5.png" scale="60"/> + </imageobject> + </mediaobject> + </figure> - <para>What&apos;s more, code assist is also available for <emphasis - role="italic"> - <property>&quot;jsfc&quot;</property> - </emphasis> attribute in any HTML tag.</para> + <para> + Code assist is also available for <code>jsfc</code> attributes in any HTML tag. + </para> - <figure> - <title>Code Assist for JSFC Attribute</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_6.png" - scale="70"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Code Assist for JSFC Attribute</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_6.png" scale="70"/> + </imageobject> + </mediaobject> + </figure> - <para>After selecting <emphasis role="italic"> - <property>&quot;jsfc&quot;</property> - </emphasis> you get the code assist for JSF components available on - a page.</para> + <para>After selecting an <code>jsfc</code> attribute, the code assist feature will list the JSF components available on a page.</para> - <figure> - <title>Code Assist for JSF Components</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_7.png" - scale="80"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Code Assist for JSF Components</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_7.png" scale="80"/> + </imageobject> + </mediaobject> + </figure> - <para>When a component is chosen you will see all available attributes for - it.</para> + <para>When a component is selected you will see all available attributes for it.</para> - <figure> - <title>Available Attributes for the Component</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_8.png" - scale="80"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section> - <title>Open On feature</title> - <para>Finally, Eclipse&apos;s <emphasis> - <property>OpenOn</property> - </emphasis> feature for editing Facelets files is supported. Using this feature, - you can easily navigate between the <property>Facelets - templates</property> and other parts of your projects. Just by - holding down the Control key while hovering the mouse cursor over a - reference to a template, the reference becomes a hyperlink to open - that template.</para> + <figure> + <title>Available Attributes for the Component</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_8.png" scale="80"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Open On feature</title> + <para> + Finally, JSF Tools supports Eclipse&apos;s <productname>OpenOn</productname> feature while editing Facelets files. Using this feature, you can easily navigate between the <property>Facelets templates</property> and other parts of your projects. By holding down the <keycap>Ctrl</keycap> key while hovering the mouse cursor over a reference to a template, the reference becomes a hyperlink to navigate to that template. + </para> + <figure> + <title>Template Hyperlink</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_9.png" scale="75"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Template Hyperlink</title> - <mediaobject> - <imageobject> - <imagedata - fileref="images/jsf_support/jsf_support_9.png" - scale="75"/> - </imageobject> - </mediaobject> - </figure> - <!-- <para>Additionally, when hovering the mouse cursor over <emphasis role="italic"><property>&quot;Facelets tag&quot;</property></emphasis> attributes, JBoss Developer Studio provides a pop-up help tip:</para> <figure> <title>Pop-up Help Tip for Facelets Tag Attributes</title> @@ -286,7 +240,7 @@ <!-- <para>See <link linkend="faq_facelets">FAQ</link> concerning Facelets support.</para> --> - </section> + </section> <!--section> <title>Relevant Resources Links</title> @@ -294,7 +248,7 @@ url="https://facelets.dev.java.net/" </section--> - </section> + </section> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/managed_beans.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/managed_beans.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/managed_beans.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -1,208 +1,173 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="managed_beans"> - <?dbhtml filename="managed_beans.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Developer Studio</keyword> - <keyword>Eclipse</keyword> - <keyword>JSF Tools</keyword> - <keyword>Java</keyword> - <keyword>JBoss</keyword> - </keywordset> - </chapterinfo> + <?dbhtml filename="managed_beans.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>JSF Tools</keyword> + <keyword>Java</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> - <title>Managed Beans</title> + <title>Managed Beans</title> - <para>There is lots of power to work with <property>managed beans</property>.</para> - <itemizedlist> - <listitem> - <para>Add and generate code for new managed beans</para> - <itemizedlist> - <listitem> - <para>Generate code for attributes and getter/setter methods</para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para>Add existing managed beans to JSF configuration file</para> - </listitem> - </itemizedlist> + <para>JSF Tools provides a number of useful features when working with <property>managed beans</property>, such as:</para> + <itemizedlist> + <listitem> + <para>Adding and generating code for new managed beans</para> + <itemizedlist> + <listitem> + <para>Generating code for attributes and getter/setter methods</para> + </listitem> + </itemizedlist> + </listitem> + <listitem> + <para>Adding existing managed beans to a JSF configuration file</para> + </listitem> + </itemizedlist> - <para>Thus, in this section we will guides you through all this possibilities.</para> + <para>This guide will look at each of these features in more detail.</para> - <section id="CodeGenerationForManagedBeans421"> + <section id="CodeGenerationForManagedBeans421"> - <title>Code Generation for Managed Beans</title> + <title>Code Generation for Managed Beans</title> - <para>To start, create a new managed bean in JSF configuration file editor, in the Tree - view.</para> - <figure> - <title>Creation of New Managed Bean</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_34.png"/> - </imageobject> - </mediaobject> - </figure> - <note> - <title>Note:</title> - <para>When you define a new managed bean, make sure that <emphasis> - <property>Generate Source Code</property> - </emphasis> is checked as shown in the figure below.</para> - </note> - <figure> - <title>New Managed Bean</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_35.png" scale="75"/> - </imageobject> - </mediaobject> - </figure> - <para>After the <emphasis role="italic"> - <property>&quot;Java&quot;</property> - </emphasis> class has been generated you can open it for additional editing. There are - two ways to open the <emphasis role="italic"> - <property>&quot;Java&quot;</property> - </emphasis> class:</para> + <para>To begin, create a new managed bean in JSF configuration file editor using the <guilabel>Tree view</guilabel>.</para> + <figure> + <title>Creation of New Managed Bean</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_34.png"/> + </imageobject> + </mediaobject> + </figure> + <note> + <title>Note:</title> + <para> + When you define a new managed bean, make sure that <guilabel>Generate Source Code</guilabel> option is checked as shown in the figure below. + </para> + </note> + <figure> + <title>New Managed Bean</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_35.png" scale="75"/> + </imageobject> + </mediaobject> + </figure> + <para>After the Java class has been generated you can open it for additional editing. There are two ways to open a Java class:</para> - <itemizedlist> - <listitem> - <para>click on <emphasis> - <property>Managed-Bean-Class</property> - </emphasis> link in the editor</para> - </listitem> - </itemizedlist> - <para>or</para> - <itemizedlist> - <listitem> - <para>right click the <emphasis> - <property>managed bean</property> - </emphasis> and select <emphasis> - <property>Open Source</property> - </emphasis></para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para>Click on the <guilabel>Managed-Bean-Class</guilabel> link in the editor.</para> + </listitem> + </itemizedlist> + <itemizedlist> + <listitem> + <para>Right click the <emphasis><property>managed bean</property> </emphasis> and select the <guimenuitem>Open Declaration</guimenuitem> option. + </para> + </listitem> + </itemizedlist> - <figure> - <title>Opening of Created Managed Bean</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_36.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Opening of Created Managed Bean</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_36.png"/> + </imageobject> + </mediaobject> + </figure> - <para>The generated Java source should look as follows:</para> + <para>The generated Java source should look as follows:</para> - <figure> - <title>Java Source Code</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_37.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Java Source Code</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_37.png"/> + </imageobject> + </mediaobject> + </figure> - <para>You can also generate source code for properties, also includes <emphasis - role="italic"> - <property>&quot;getter&quot;</property> - </emphasis> and <emphasis role="italic"> - <property>&quot;setter&quot;</property> - </emphasis> methods. Right click on the bean and select <emphasis> - <property>New &gt; Property</property> - </emphasis>. You will see <property>Add Property</property> dialog.</para> - <figure> - <title>Generation of Source Code for Properties</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_38.png"/> - </imageobject> - </mediaobject> - </figure> - <para>When the form is open make sure that all the check boxes are selected:</para> - <itemizedlist> - <listitem> - <para>Add Java property</para> - </listitem> - <listitem> - <para>Generate Getter</para> - </listitem> - <listitem> - <para>Generate Setter</para> - </listitem> - </itemizedlist> - <para/> - <figure> - <title>&quot;Add Property&quot; Form</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_39.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Once the generation is complete, you can open the file and see the added property with - <emphasis role="italic"> - <property>&quot;get&quot;</property> - </emphasis> and <emphasis role="italic"> - <property>&quot;set&quot;</property> - </emphasis> methods:</para> - <figure> - <title>Generated Java Source Code for Property</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_40.png" scale="75"/> - </imageobject> - </mediaobject> - </figure> - <para>Thus, we&apos;ve discussed everything which comes to creating a new Managed Bean. - The next section will show you how to add an existing Bean into a JSF configuration - file.</para> - </section> - <section id="AddExistingJavaBeansToAJSFConfigurationFile74332"> + <para>You can also generate source code for properties, also includes getter and setter methods. Right click on the bean and select <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>Property</guimenuitem></menuchoice>. You will then see the <guilabel>Add Property</guilabel> dialog.</para> + <figure> + <title>Generation of Source Code for Properties</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_38.png"/> + </imageobject> + </mediaobject> + </figure> + <para>When the form is open make sure that all the check boxes are selected:</para> + <itemizedlist> + <listitem> + <para>Add Java property</para> + </listitem> + <listitem> + <para>Generate Getter</para> + </listitem> + <listitem> + <para>Generate Setter</para> + </listitem> + </itemizedlist> + <para/> + <figure> + <title>&quot;Add Property&quot; Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_39.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + Once the generation is complete, you can open the file and see the newly added property with accompanying &quot;get&quot; and &quot;set&quot; methods: + </para> + <figure> + <title>Generated Java Source Code for Property</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_40.png" scale="75"/> + </imageobject> + </mediaobject> + </figure> + <para> + This covers the options available when creating a new Managed Bean. The next section will show you how to add an existing Bean into a JSF configuration file. + </para> + </section> + <section id="AddExistingJavaBeansToAJSFConfigurationFile74332"> - <title>Add Existing Java Beans to a JSF Configuration File</title> - <para>If you already have a Java bean you can easily add it to a <property>JSF configuration - file</property>.</para> - <para>You should start the same way you create a new managed bean. Use the <emphasis> - <property>Browse...</property> - </emphasis> button to add your existing Java class.</para> - <figure> - <title>New Managed Bean Form</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_42.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Once the class is set, its <emphasis> - <property>Name</property> - </emphasis> will be set as well. But you can easily substitute it for the other one. - Notice that <emphasis> - <property>Generate Source Code</property> - </emphasis> option is not available as the <emphasis role="italic"> - <property>&quot;Java&quot;</property> - </emphasis> class already exists. </para> - <para>After adding your class <emphasis> - <property>Next</property> - </emphasis> button will be activated. Pressing it you&apos;ll get <emphasis> - <property>Managed Properties</property> - </emphasis> dialog where all corresponding properties are displayed. Check the necessary - ones to add them into your <property>JSF Configuration File</property>.</para> + <title>Add Existing Java Beans to a JSF Configuration File</title> + <para>If you already have a Java bean you can easily add it to a <property>JSF configuration file</property>.</para> + <para>You should start the same way you create a new managed bean. Use the <guibutton>Browse...</guibutton> button to add your existing Java class.</para> + <figure> + <title>New Managed Bean Form</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_42.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + Once the class is set, its <guilabel>Name</guilabel> will be set as well. But you can easily substitute it for the other one. Notice that <guilabel>Generate Source Code</guilabel> option is not available as the Java class already exists. + </para> + <para> + After adding your class the <guibutton>Next</guibutton> button will be activated. When you click it you will be presented with the <guilabel>Managed Properties</guilabel> dialog where all corresponding properties are displayed. Checking the appropriate ones will add them into your <property>JSF Configuration File</property>. + </para> - <figure> - <title>Selection of Bean&apos;s Properties.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_43.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Selection of Bean&apos;s Properties.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_43.png"/> + </imageobject> + </mediaobject> + </figure> - <para>If you don&apos;t want to add any, just click <emphasis> - <property>Finish</property>. </emphasis></para> - <para>Above-listed steps have demonstrated how you can specify an existing Bean in the JSF - configuration file, i.e. <emphasis> - <property>faces-config.xml</property>. </emphasis> In the next chapter - you&apos;ll know how to organize and register another kind of artifacts.</para> - </section> + <para>If you don&apos;t want to add any, just click the <guibutton>Finish</guibutton> button.</para> + <para> + The steps above have demonstrated how you can add an existing Bean to the JSF configuration file, i.e. <filename>faces-config.xml</filename>. The next chapter will demonstrate how to organize and register other kinds of artifacts. + </para> + </section> </chapter> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/master.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/master.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/master.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -49,18 +49,19 @@ <year>2008</year> <year>2009</year> <year>2010</year> + <year>2011</year> <holder>JBoss by Red Hat</holder> </copyright> <releaseinfo> Version: 3.1.1.GA </releaseinfo> -<abstract> +<!--<abstract> <title/> <para> <ulink url="http://download.jboss.org/jbosstools/nightly-docs/en/jsf_tools_... version</ulink> </para> -</abstract> +</abstract>--> </bookinfo> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/projects.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/projects.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/projects.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -1,75 +1,68 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="projects"> - <?dbhtml filename="projects.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Developer Studio</keyword> - <keyword>Eclipse</keyword> - <keyword>JSF Tools</keyword> - <keyword>Java</keyword> - <keyword>JBoss</keyword> - </keywordset> - </chapterinfo> + <?dbhtml filename="projects.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>JSF Tools</keyword> + <keyword>Java</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> - <title>Projects</title> - <para>To take an advantage of JSF firstly you should perform one of the next steps:</para> + <title>Projects</title> + <para>To take an advantage of JSF you will need to perform one of the next steps:</para> - <itemizedlist> - <listitem> - <para>Create new JSF projects</para> - </listitem> - <listitem> - <para>Import (open) existing JSF projects</para> - </listitem> - <listitem> - <para>Add JSF capability to any existing Eclipse project</para> - </listitem> - <listitem> - <para>Import and add JSF capability to any existing project created outside - Eclipse.</para> - </listitem> - </itemizedlist> - <para>In this section we&apos;re going to stop on each of them in detail.</para> + <itemizedlist> + <listitem> + <para>Create new JSF projects</para> + </listitem> + <listitem> + <para>Import (open) existing JSF projects</para> + </listitem> + <listitem> + <para>Add JSF capability to any existing Eclipse project</para> + </listitem> + <listitem> + <para>Import and add JSF capability to any existing project created outside Eclipse.</para> + </listitem> + </itemizedlist> + <para>This section will go into more detail for each step.</para> - <section id="new_jsf_project"> + <section id="new_jsf_project"> - <title>Creating a New JSF Project</title> + <title>Creating a New JSF Project</title> - <para>If you want your project to already contain all JSF libraries, tag libraries - and JSF configuration file, just organize a new brand JSF project. It is - possible to do this easily with the help of the special wizard. To get it, select<emphasis> - <property> File &gt; New &gt; Project &gt; JBoos Tools - Web &gt; JSF &gt; JSF Project</property> - </emphasis> and click <emphasis> - <property>Next</property>.</emphasis></para> + <para> + It is easy to create a new project that contains all the JSF libraries, tag libraries and JSF configuration file with the aid of a special wizard. To get it, select <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>JBoos Tools Web</guimenuitem><guimenuitem>JSF</guimenuitem><guimenuitem>JSF Project</guimenuitem></menuchoice> and click the <guibutton>Next</guibutton> button. + </para> - <figure> - <title>Choosing a JSF Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_10.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Choosing a JSF Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_10.png"/> + </imageobject> + </mediaobject> + </figure> - <para>On the next form you&apos;ll be prompted to enter <property>Project - Name</property> and select a location for the project or just leave - a default path.</para> - <para>Here, JSF Version also allows you to select which JSF implementation to - use.</para> - <figure> - <title>Creating a New JSF Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_11.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + On the next page you will be prompted to enter the <guilabel>Project Name</guilabel> and select a location for the project (or just leave a default path). + </para> + <para>The <guilabel>JSF Version</guilabel> option also allows you to specify the JSF implementation to use.</para> + <figure> + <title>Creating a New JSF Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_11.png"/> + </imageobject> + </mediaobject> + </figure> - <para>There is a number of predefined project templates that are flexible and easily - customizable. Thus you can pick a different template on which the projects - Importing Existing should be based on. Almost all templates come in two - variations: with jsf libraries and without ones.</para> + <para> + There are a number of predefined project templates that are both flexible and easily customizable. You can pick a different template on which the projects Importing Existing should be based on. Almost all templates come in two variations: with and without JSF libraries. + </para> <figure> <title>Choosing JSF Templates</title> <mediaobject> @@ -77,82 +70,77 @@ <imagedata fileref="images/jsf_support/jsf_support_12.png"/> </imageobject> </mediaobject> - </figure> + </figure> - <para>The table below provides description for each possible JSF template.</para> - <table> - <title>JSF Project Templates</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> + <para>The table below provides description for each possible JSF template.</para> + <table> + <title>JSF Project Templates</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> - <thead> - <row> - <entry align="center"> - <para>Template</para> - </entry> + <thead> + <row> + <entry align="center"> + <para>Template</para> + </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> - <tbody> + <tbody> - <row> - <entry> - <para> - <emphasis> - <property>JSFBlankWithLibs</property> - </emphasis> - </para> - </entry> + <row> + <entry> + <para> + <emphasis> + <property>JSFBlankWithLibs</property> + </emphasis> + </para> + </entry> - <entry> - <para>This template will create a standard Web - project structure with all JSF capabilities</para> - </entry> - </row> + <entry> + <para>This template will create a standard Web project structure with all the JSF capabilities</para> + </entry> + </row> - <row> - <entry> - <para> - <emphasis> - <property>JSFKickStartWithLibs</property> - </emphasis> - </para> - </entry> + <row> + <entry> + <para> + <emphasis> + <property>JSFKickStartWithLibs</property> + </emphasis> + </para> + </entry> - <entry> - <para>This template will create a standard Web - project structure but will also include a sample - application that is ready to run</para> - </entry> - </row> + <entry> + <para>This template will create a standard Web project structure, and also include a sample application that is ready to run</para> + </entry> + </row> - <row> - <entry> - <para> - <emphasis> - <property>JSFKickStartWithoutLibs</property> - </emphasis> - </para> - </entry> + <row> + <entry> + <para> + <emphasis> + <property>JSFKickStartWithoutLibs</property> + </emphasis> + </para> + </entry> - <entry> - <para>Some servers already provide jsf libs and - you take risk of getting conflicting libraries - while deploying your project. To avoid such - conflicts, use a template without libs if you have - a server with its own jsf libraries</para> - </entry> - </row> + <entry> + <para> + Some servers already provide JSF libs, and you risk library conflicts while deploying your project. To avoid such conflicts, use a template without libs if you have a server with its own JSF libraries. + </para> + </entry> + </row> - </tbody> - </tgroup> - </table> + </tbody> + </tgroup> + </table> <!-- <para>You can of course create your own custom templates. More information @@ -160,243 +148,197 @@ linkend="CreatingCustomJSPTemplates">Chapter 5</link>.</para> --> - <para>On the next screen select what <emphasis> - <property>Servlet version</property> - </emphasis> to use and whether to register this application with JBoss AS - (or other server) for running and testing your application.</para> + <para> + On the next page you need to select which <guilabel>Servlet version</guilabel> to use, and specify whether or not to register this application with JBoss AS (or other server) in order to run and test your application. + </para> - <para>The <emphasis> - <property>Context Path</property> - </emphasis> is the name under which the application will be deployed.</para> + <para>The <guilabel>Context Path</guilabel> option defines the name under which the application will be deployed.</para> - <para>The <emphasis> - <property>Runtime</property> - </emphasis> value tells Eclipse where to find Web libraries in order to - build (compile) the project. It is not possible to finish project creation - without selecting Runtime. If you don&apos;t have any values, select <emphasis> - <property>New...</property> - </emphasis> to add new Runtime.</para> + <para> + The <guilabel>Runtime</guilabel> value tells Eclipse where to find the Web libraries necessary to build (compile) the project. It is not possible to finish the project creation without selecting a Runtime. If you do not have any values, click the <guibutton>New...</guibutton> button to add new Runtime. + </para> - <para>The <emphasis> - <property>Target Server</property> - </emphasis> allows you specifying whether to deploy the application. The - Target Server corresponds to the Runtime value selected above. If you - don&apos;t want to deploy the application, uncheck this value.</para> - <figure> - <title>Registering the Project on Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_14.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + The <guilabel>Target Server</guilabel> option allows you specifying whether or not to deploy the application. The Target Server corresponds to the Runtime value selected above. If you do not want to deploy the application, uncheck this option. + </para> + <figure> + <title>Registering the Project on Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_14.png"/> + </imageobject> + </mediaobject> + </figure> - <para>When you are all done, you should have the project that has been appeared in - the Package Explorer view:</para> - <figure> - <title>A New Project in the Package Explorer</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_15.png"/> - </imageobject> - </mediaobject> - </figure> + <para>When you are all done, you should see that the project has appeared in the Package Explorer view:</para> + <figure> + <title>A New Project in the Package Explorer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_15.png"/> + </imageobject> + </mediaobject> + </figure> - <para>At this point you can open <emphasis> - <property>faces-config.xml</property> - </emphasis> and start working on your application. There are a lot of - features to develop JSF applications. We will describe the features - further.</para> - </section> + <para> + At this point you can open the <filename>faces-config.xml</filename> file and start working on your application. There are a lot of features available when developing JSF applications. These features will be discussed in more detail later in this document.</para> + </section> - <section id="ImportingExsJSFProjWithAnyStr74447"> + <section id="ImportingExsJSFProjWithAnyStr74447"> - <title>Importing Existing JSF Projects with Any Structure</title> + <title>Importing Existing JSF Projects with Any Structure</title> - <para>For detailed information on migration of JSF projects into a workspace see the Migration - Guide.</para> + <para>For detailed information on migration of JSF projects into a workspace see the Migration Guide.</para> - </section> - <section id="add_jsf_capability"> + </section> + <section id="add_jsf_capability"> - <title>Adding JSF Capability to Any Existing Eclipse Project</title> + <title>Adding JSF Capability to Any Existing Eclipse Project</title> - <para>It&apos;s also possible to add <property>JSF capability</property> (JSF - libraries, tag libraries) to any existing Eclipse project in your workspace. - After that you&apos;ll be able to make use of such editors as JSF - configuration editor, JBoss Tools JSP editor and any others.</para> - <para>Right click the project and select <emphasis> - <property>JBoss Tools > Add JSF Capabilities</property>. </emphasis> - This will start the process of adding all necessary libraries, files to make - this a Web JSF project.</para> - <figure> - <title>Adding JSF Capabilities</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_16.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The wizard will first ask you to show the <emphasis> - <property>web.xml</property> - </emphasis> file location and the project name.</para> - <figure> - <title>Project Location</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_17.png"/> - </imageobject> - </mediaobject> - </figure> - <para>On the last form you can set the different folders for your project as well as - register this application with a servlet container.</para> + <para> + It is also possible to add <productname>JSF</productname> capabilities (JSF libraries, tag libraries) to any existing Eclipse project in your workspace. After that you will be able to make use of features such as the JSF configuration editor, JBoss Tools JSP editor and any others. + </para> + <para> + Right click the project and select <menuchoice><guimenuitem>JBoss Tools</guimenuitem><guimenuitem>Add JSF Capabilities</guimenuitem></menuchoice> from the context menu. This will start the process of adding the necessary libraries and files to convert the project into a Web JSF project. + </para> + <figure> + <title>Adding JSF Capabilities</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_16.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The wizard will first ask you to define location of the <filename>web.xml</filename> file and the project name.</para> + <figure> + <title>Project Location</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_17.png"/> + </imageobject> + </mediaobject> + </figure> + <para>On the last page you can specify the different folders for your project as well as register this application with a servlet container.</para> - <para>Make sure to select <emphasis> - <property>Add Libraries</property> - </emphasis> to add all required JSF related libraries to this - project.</para> + <para>Make sure to select the <guilabel>Add Libraries</guilabel> option to add all required JSF related libraries into your project.</para> - <para>The <emphasis> - <property>Context Path</property> - </emphasis> is the name under which the application will be deployed.</para> + <para>The <guilabel>Context Path</guilabel> option defines the name under which the application will be deployed.</para> - <para>The <emphasis> - <property>Runtime</property> - </emphasis> value tells Eclipse where to find Web libraries in order to - build (compile) the project. It is not possible to finish project import - without selecting Runtime. If you don&apos;t have any values, select <emphasis> - <property>New...</property> - </emphasis> to add new Runtime.</para> + <para> + The <guilabel>Runtime</guilabel> value tells Eclipse where to find Web libraries necessary to build (compile) the project. It is not possible to finish project import without selecting the Runtime. If you don not have any values, click the <guibutton>New...</guibutton> button to add a new Runtime. + </para> - <para>The <emphasis> - <property>Target Server</property> - </emphasis> allows you to specify whether to deploy the application. The - Target Server corresponds to the Runtime value selected above. If you - don&apos;t want to deploy the application, uncheck this value.</para> - <figure> - <title>Project Folders</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_18.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Once your project is imported you can see that JSF related libraries have been - added to your project: <emphasis> - <property>jsf-api.jar</property> - </emphasis> and <emphasis> - <property>jsf-impl.jar</property> - </emphasis>.</para> - <note> - <title>Note:</title> - <para>Some application servers provide their own jsf implementation - libraries. Thus, to avoid conflicts you should not add jsf libraries - while adding jsf capabilities.</para> - </note> - <para>You are now ready to work with JSF by creating a new JSF configuration - file:</para> + <para> + The <guilabel>Target Server</guilabel> option allows you to specify whether or not to deploy the application. The Target Server corresponds to the Runtime value selected above. If you do not want to deploy the application, uncheck this value. + </para> + <figure> + <title>Project Folders</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_18.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + Once your project is imported you can see that JSF related libraries <filename>jsf-api.jar</filename> and <filename>jsf-impl.jar</filename> have been added to your project. + </para> + <note> + <title>Note:</title> + <para> + Some application servers provide their own JSF implementation libraries. To avoid conflicts you should not add JSF libraries while adding JSF capabilities. + </para> + </note> + <para>You are now ready to work with JSF by creating a new JSF configuration file:</para> + <figure> + <title>Creating a New JSF Configuration File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_19.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Creating a New JSF Configuration File</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_19.png"/> - </imageobject> - </mediaobject> - </figure> + <para>Once the file has been created, it should be opened in a special editor (see <xref linkend="jsf_config_file"/>).</para> + </section> + <section id="AddingYourOwnProjectTemplates853"> - <para>Once the file has been created, it should be opened in a special <xref linkend="jsf_config_file"/>.</para> - </section> - <section id="AddingYourOwnProjectTemplates853"> + <title>Adding Your Own Project Templates</title> + <para> + A template is a set of files that is provided as a basis when creating a new project. Project templates provide content and structure for a project. + </para> + <para> + JSF Tools provides powerful template capabilities which allow you to create new templates and import existing Struts and JSF projects. This templating facility has a variety of aspects to consider. Let&apos;s start with the most straightforward case and consider the process of creating a template from your existing JSF project. + </para> - <title>Adding Your Own Project Templates</title> - <para>Template is a set of files that is served as a basis to facilitate the - creation of a new project. Project templates provide content and structure - for a project.</para> - <para>There is a powerful templating capability for creating new and importing - existing Struts and JSF projects. This templating facility has a variety of - aspects to consider. But, let&apos;s start with the most straightforward - case and consider the process of creating a template from your existing JSF - project.</para> + <para> + Let&apos;s say you have a project that you want to use as the basis for a new <property>template</property>. The following steps will show you how to achieve this: + </para> + <itemizedlist> + <listitem> + <para> + In the Web Projects view, right-click the project and select <menuchoice><guimenuitem>JBoss Tools JS</guimenuitem><guimenuitem>Save As Template</guimenuitem></menuchoice> + </para> + </listitem> + </itemizedlist> + <figure> + <title>Saving Your Project as Template</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_20.png"/> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para> + In the first dialog box, you can specify a name for the template (it will default to the project name) and confirm what run-time implementation of the project technology will be used. + </para> + </listitem> - <para>Let&apos;s say you have a project that you want to use as the basis for a - new <property>template</property>. Follow these steps to make a template out - of it:</para> - <itemizedlist> - <listitem> - <para>In the Web Projects view, right-click the project and select <emphasis> - <property>JBoss Tools JSF > Save As - Template</property> - </emphasis></para> - </listitem> - </itemizedlist> - <figure> - <title>Saving Your Project as Template</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_20.png"/> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>In the first dialog box, you can choose a name for the - template (defaults to the project name) and confirm what - run-time implementation of the project technology will be - used</para> - </listitem> + </itemizedlist> + <figure> + <title>Define Template Properties</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_20_1.png" /> + </imageobject> + </mediaobject> + </figure> - </itemizedlist> - <figure> - <title>Define Template Properties</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_20_1.png" - /> - </imageobject> - </mediaobject> - </figure> + <itemizedlist> + <listitem> + <para> + When you click the <guibutton>Next</guibutton> button a dialog box will be presented with your project structure displayed, along with a number of check boxes. Here you can select only those parts and files in your project directory that should be part of the template. + </para> + </listitem> + </itemizedlist> + <figure> + <title>Define Template Properties</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_20_2.png" /> + </imageobject> + </mediaobject> + </figure> + <itemizedlist> + <listitem> + <para> + At this point, unless you want to designate some extra files as having Velocity template coding inside them, you should click the <guibutton>Finish</guibutton> button. + </para> + </listitem> + </itemizedlist> + <para> + That&apos;s it. This template can be used with any new or imported project that uses the same run-time implementation as the project you turned into a template. + </para> + <para>At this point you have a fully configured project. Now you can add some additional logic to it starting with the JSF configuration file.</para> + </section> + <section> + <title>Relevant Resources Links</title> - <itemizedlist> - <listitem> - <para>Select <emphasis> - <property>Next</property> - </emphasis> and you will be sent to a dialog box with your - project structure displayed with check boxes. Here you can - check only those parts and files in your project directory - that should be part of the template</para> - </listitem> - </itemizedlist> - <figure> - <title>Define Template Properties</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_20_2.png" - /> - </imageobject> - </mediaobject> - </figure> - <itemizedlist> - <listitem> - <para>At this point, unless you want to designate some extra files - as having Velocity template coding inside them, you should - click <emphasis> - <property>Finish</property> - </emphasis>.</para> - </listitem> - </itemizedlist> - <para>That&apos;s it. Now, you can use this template with any new or imported - project that uses the same run-time implementation as the project you turned - into a template.</para> - <para>At this point, you have a fully configured project and now you can bring some - new logic to it starting from JSF configuration file.</para> - </section> - <section> - <title>Relevant Resources Links</title> - - <para>You can find more in-depth explanation on how to work with special wizards, editors and views that can - be used in various scenarios while developing JSF applications in our Visual Web Tools Guide.</para> - </section> + <para> + You can find a more in-depth explanation on how to work with the special wizards, editors and views that can be used while developing JSF applications in our Visual Web Tools Guide. + </para> + </section> </chapter> Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/webxml_editor.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/webxml_editor.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/en-US/webxml_editor.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -10,12 +10,11 @@ <title>Web.xml Editor</title> - <para>The <emphasis> - <property>web.xml</property></emphasis> file inside the <emphasis> - <property>WEB-INF</property></emphasis> folder is a deployment descriptor file for a Web Application. It - describes the servlets and other components and deployment properties that make up your application.</para> + <para> + The <filename>web.xml</filename> file inside the <filename>WEB-INF</filename> folder is a deployment descriptor file for a Web Application. It describes the servlets and other components and deployment properties that make up your application. + </para> - <para><property>JBoss Tools</property> add the <emphasis> - <property>web.xml</property></emphasis> file to created JSF project automatically and provides a special editor for its editing. - See the Visual Web Tools guide that gives a descriptive information on the <filename>web.xml editor</filename>.</para> + <para> + <property>JBoss Tools</property> add the <filename>web.xml</filename> file to created JSF project automatically and provides a special editor for its editing. See the Visual Web Tools guide for more information on the <filename>web.xml</filename> editor. + </para> </chapter> \ No newline at end of file Modified: branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/pom.xml =================================================================== --- branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/pom.xml 2011-07-18 02:11:21 UTC (rev 32979) +++ branches/jbosstools-3.2.x/jsf/docs/jsf_tools_ref_guide/pom.xml 2011-07-18 02:19:56 UTC (rev 32980) @@ -1,7 +1,5 @@ <?xml version="1.0" encoding="utf-8"?> -<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"> +<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.tools</groupId> @@ -10,229 +8,232 @@ <packaging>jdocbook</packaging> <name>${bookname}-(${translation})</name> - <properties> - <translation>en-US</translation> - <docname>JSF_Tools_Reference_Guide</docname> - <bookname>JSF Tools Reference Guide</bookname> - </properties> - - <profiles> + <properties> + <translation>en-US</translation> + <docname>JSF_Tools_Reference_Guide</docname> + <bookname>JSF Tools Reference Guide</bookname> + </properties> + <profiles> + <!-- mvn compile --> - <profile> - <id>all</id> - <activation> - <activeByDefault>true</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.3.3</version> - <extensions>true</extensions> - <configuration> - <formats> - <format> - <formatName>pdf</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource> - <finalName>${docname}.pdf</finalName> - </format> - <format> - <formatName>html</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - <format> - <formatName>html_single</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - <format> - <formatName>eclipse</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - </formats> - </configuration> - </plugin> + <profile> + <id>all</id> + <activation> + <activeByDefault>true</activeByDefault> + </activation> + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>2.3.4</version> + <extensions>true</extensions> + <configuration> + <formats> + <format> + <formatName>pdf</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource> + <finalName>${docname}.pdf</finalName> + </format> + <format> + <formatName>html</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + <format> + <formatName>html_single</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + <format> + <formatName>eclipse</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + </formats> + <options> + <useRelativeImageUris>true</useRelativeImageUris> + </options> + </configuration> + </plugin> </plugins> </build> </profile> <!-- mvn compile -Phtml --> - <profile> - <id>html</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.3.3</version> - <extensions>true</extensions> - <configuration> - <formats> - <format> - <formatName>html</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - </formats> - </configuration> - </plugin> + <profile> + <id>html</id> + <activation> + <activeByDefault>false</activeByDefault> + </activation> + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>2.3.3</version> + <extensions>true</extensions> + <configuration> + <formats> + <format> + <formatName>html</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + </formats> + </configuration> + </plugin> </plugins> </build> </profile> <!-- mvn compile -Phtml-single --> - <profile> - <id>html-single</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.3.3</version> - <extensions>true</extensions> - </plugin> + <profile> + <id>html-single</id> + <activation> + <activeByDefault>false</activeByDefault> + </activation> + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>2.3.3</version> + <extensions>true</extensions> + </plugin> </plugins> </build> </profile> <!-- mvn compile -Ppdf --> - <profile> - <id>pdf</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.3.3</version> - <extensions>true</extensions> - <configuration> - <formats> - <format> - <formatName>pdf</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource> - <finalName>${docname}.pdf</finalName> - </format> - </formats> - </configuration> - </plugin> + <profile> + <id>pdf</id> + <activation> + <activeByDefault>false</activeByDefault> + </activation> + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>2.3.3</version> + <extensions>true</extensions> + <configuration> + <formats> + <format> + <formatName>pdf</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource> + <finalName>${docname}.pdf</finalName> + </format> + </formats> + </configuration> + </plugin> </plugins> </build> </profile> <!-- mvn compile -Peclipse --> - <profile> - <id>eclipse</id> - <activation> - <activeByDefault>false</activeByDefault> - </activation> - <build> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.3.3</version> - <extensions>true</extensions> - <configuration> - <formats> - <format> - <formatName>eclipse</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - </formats> - </configuration> - </plugin> - </plugins> - </build> - </profile> + <profile> + <id>eclipse</id> + <activation> + <activeByDefault>false</activeByDefault> + </activation> + <build> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>2.3.3</version> + <extensions>true</extensions> + <configuration> + <formats> + <format> + <formatName>eclipse</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + </formats> + </configuration> + </plugin> + </plugins> + </build> + </profile> - </profiles> - <build> - <pluginManagement> - <plugins> - <plugin> - <groupId>org.jboss.maven.plugins</groupId> - <artifactId>maven-jdocbook-plugin</artifactId> - <version>2.3.3</version> - <extensions>true</extensions> - <dependencies> - <dependency> - <groupId>org.jboss.pressgang</groupId> - <artifactId>pressgang-xslt</artifactId> - <version>1.2.0</version> - </dependency> - <dependency> - <groupId>org.jboss</groupId> - <artifactId>jbossorg-jdocbook-style</artifactId> - <version>1.1.1</version> - <type>jdocbook-style</type> - </dependency> - </dependencies> - <configuration> - <sourceDirectory>${project.basedir}</sourceDirectory> + </profiles> + <build> + <pluginManagement> + <plugins> + <plugin> + <groupId>org.jboss.maven.plugins</groupId> + <artifactId>maven-jdocbook-plugin</artifactId> + <version>2.3.3</version> + <extensions>true</extensions> + <dependencies> + <dependency> + <groupId>org.jboss.pressgang</groupId> + <artifactId>pressgang-xslt</artifactId> + <version>1.2.0</version> + </dependency> + <dependency> + <groupId>org.jboss</groupId> + <artifactId>jbossorg-jdocbook-style</artifactId> + <version>1.1.1</version> + <type>jdocbook-style</type> + </dependency> + </dependencies> + <configuration> + <sourceDirectory>${project.basedir}</sourceDirectory> <!-- <sourceDocumentName>${docname}.xml</sourceDocumentName> --> - <sourceDocumentName>master.xml</sourceDocumentName> - <masterTranslation>en-US</masterTranslation> - <imageResource> - <directory>${project.basedir}/en-US</directory> - <includes> - <include>images/**/*</include> - </includes> - </imageResource> - <formats> - <format> - <formatName>pdf</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource> - <finalName>${pdf.name}</finalName> - </format> - <format> - <formatName>html</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - <format> - <formatName>html_single</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - <format> - <formatName>eclipse</formatName> - <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource> - <finalName>index.html</finalName> - </format> - </formats> - <options> - <xincludeSupported>true</xincludeSupported> - <xmlTransformerType>saxon</xmlTransformerType> - <docbookVersion>1.72.0</docbookVersion> - <localeSeparator>-</localeSeparator> - <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> - </transformerParameters> - </options> - </configuration> - </plugin> - </plugins> - </pluginManagement> - </build> + <sourceDocumentName>master.xml</sourceDocumentName> + <masterTranslation>en-US</masterTranslation> + <imageResource> + <directory>${project.basedir}/en-US</directory> + <includes> + <include>images/**/*</include> + </includes> + </imageResource> + <formats> + <format> + <formatName>pdf</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/pdf.xsl</stylesheetResource> + <finalName>${pdf.name}</finalName> + </format> + <format> + <formatName>html</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + <format> + <formatName>html_single</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/xhtml-single.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + <format> + <formatName>eclipse</formatName> + <stylesheetResource>classpath:/xslt/org/jboss/eclipse.xsl</stylesheetResource> + <finalName>index.html</finalName> + </format> + </formats> + <options> + <xincludeSupported>true</xincludeSupported> + <xmlTransformerType>saxon</xmlTransformerType> + <docbookVersion>1.72.0</docbookVersion> + <localeSeparator>-</localeSeparator> + <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> + </transformerParameters> + </options> + </configuration> + </plugin> + </plugins> + </pluginManagement> + </build> </project>