July 2011 - jbosstools-commits - Jboss List Archives

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

by jbosstools-commits＠lists.jboss.org

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=12310500&issu...">https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...</ulink> - </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> +  <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&percnt;20Develope...'>http://bugzilla.redhat.com/</ulink>"> 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.html">Red Hat Documentation</ulink> website under the <guilabel>JBoss Developer Studio</guilabel> section. </para> -  </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</surname><email>irooskov(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>General updates</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>0</revnumber><date>Fri Nov 20 2009</date> - <author> - <firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email> - </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>mcaspers(a)redhat.com</email> + </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>irooskov(a)redhat.com</email> + </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>irooskov(a)redhat.com</email> + </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's also possible to create a - custom Converter in order to specify your own converting rules. Let's look at how you can do this.</para> - - <para>To create and register a custom converter it'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>"converter"</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'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 "validator" 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'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's also possible to create a custom Converter in order to specify your own converting rules. Let'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>"converter"</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 "validator" 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/tools</ulink> in the corresponding release directory.</para> - <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.</para> + <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.html">RedHat Documentation</ulink> website. </para> + <para>Nightly documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.</para> </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'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'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'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'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'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'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'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'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'll discuss a possible verification that you can take advantage of.</para>  - <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>"jsfHello.PersonBean9"</property> + <property>"demo.Person9"</property> </emphasis> instead of <emphasis role="italic"> - <property>"jsfHello.PersonBean"</property> + <property>"demo.Person"</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'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've selected the environment, it'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>  - <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's more, code assist is also available for <emphasis - role="italic"> - <property>"jsfc"</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>"jsfc"</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'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'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> -  - </section> + </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>"Java"</property> - </emphasis> class has been generated you can open it for additional editing. There are - two ways to open the <emphasis role="italic"> - <property>"Java"</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>"getter"</property> - </emphasis> and <emphasis role="italic"> - <property>"setter"</property> - </emphasis> methods. Right click on the bean and select <emphasis> - <property>New > 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>"Add Property" 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>"get"</property> - </emphasis> and <emphasis role="italic"> - <property>"set"</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'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>"Add Property" 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 "get" and "set" 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>"Java"</property> - </emphasis> class already exists. </para> - <para>After adding your class <emphasis> - <property>Next</property> - </emphasis> button will be activated. Pressing it you'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's Properties.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_support/jsf_support_43.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Selection of Bean's Properties.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_support/jsf_support_43.png"/> + </imageobject> + </mediaobject> + </figure> - <para>If you don'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'll know how to organize and register another kind of artifacts.</para> - </section> + <para>If you don'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> + </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'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 > New > Project > JBoos Tools - Web > JSF > 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'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>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'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'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's also possible to add <property>JSF capability</property> (JSF - libraries, tag libraries) to any existing Eclipse project in your workspace. - After that you'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'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'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'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's start with the most straightforward - case and consider the process of creating a template from your existing JSF - project.</para> + <para> + Let'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'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'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'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> +  - <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>  - <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>  - <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>  - <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>  - <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>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>

14 years, 9 months

1
0
0 / 0

JBoss Tools SVN: r32979 - in branches/jbosstools-3.2.x/jmx/docs/reference: en-US and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2011-07-17 22:11:21 -0400 (Sun, 17 Jul 2011) New Revision: 32979 Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Book_Info.xml branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Feedback.xml branches/jbosstools-3.2.x/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.ent branches/jbosstools-3.2.x/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.xml branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Preface.xml branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Revision_History.xml branches/jbosstools-3.2.x/jmx/docs/reference/en-US/images/eclipse-jmx_0.2.png branches/jbosstools-3.2.x/jmx/docs/reference/en-US/images/invokemethod.png branches/jbosstools-3.2.x/jmx/docs/reference/en-US/images/mbeans.png branches/jbosstools-3.2.x/jmx/docs/reference/en-US/images/new_connection_icon.png branches/jbosstools-3.2.x/jmx/docs/reference/en-US/introduction.xml branches/jbosstools-3.2.x/jmx/docs/reference/en-US/master.xml branches/jbosstools-3.2.x/jmx/docs/reference/en-US/references.xml branches/jbosstools-3.2.x/jmx/docs/reference/en-US/summary.xml branches/jbosstools-3.2.x/jmx/docs/reference/en-US/tasks.xml branches/jbosstools-3.2.x/jmx/docs/reference/pom.xml Log: updated for GA Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Book_Info.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Book_Info.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Book_Info.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -5,9 +5,9 @@ <title>JMX Tools Reference Guide</title> <subtitle>Provides information relating to the JMX 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 JMX Tools Reference Guide explains how to use the JMX Tools module to setup multiple JMX connections and explore the JMX tree and execute operations.</para> </abstract> Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Feedback.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Feedback.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Feedback.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -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=12310500&issu...">https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...</ulink> - </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> +  <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/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.ent =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.ent 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.ent 2011-07-18 02:11:21 UTC (rev 32979) @@ -1,4 +1,7 @@ <!ENTITY PRODUCT "JBoss"> <!ENTITY BOOKID "JMX_Tools_Reference_Guide"> -<!ENTITY YEAR "2010"> +<!ENTITY YEAR "2011"> <!ENTITY HOLDER "Red Hat"> +<!ENTITY BZPRODUCT "JBoss Developer Studio"> +<!ENTITY BZCOMPONENT "JMX Tools Reference Guide"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Develope...'>http://bugzilla.redhat.com/</ulink>"> Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/JMX_Tools_Reference_Guide.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -15,5 +15,6 @@ <xi:include href="mbean_explorer.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="mbean_editor.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/jmx/docs/reference/en-US/Preface.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Preface.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Preface.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -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.html">Red Hat Documentation</ulink> website under the <guilabel>JBoss Developer Studio</guilabel> section. </para> -  </preface> Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Revision_History.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Revision_History.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/Revision_History.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -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</surname><email>irooskov(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>Two new sections added and general updates</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>0</revnumber><date>Fri Nov 20 2009</date> - <author> - <firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>Initial creation of book by publican</member> - </simplelist> - </revdescription> - </revision> - </revhistory> - </simpara> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>2</revnumber> + <date>Thu Jan 20 2011</date> + <author> + <firstname>JBoss Tools</firstname> + <surname>Documentation Team</surname> + <email>mcaspers(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>General updates</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>1</revnumber> + <date>Wed Jun 09 2010</date> + <author> + <firstname>JBoss Tools</firstname> + <surname>Documentation Team</surname> + <email>irooskov(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>Two new sections added and general updates</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>0</revnumber> + <date>Fri Nov 20 2009</date> + <author> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + <email>irooskov(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>Initial creation of book by publican</member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </simpara> </appendix> Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/images/eclipse-jmx_0.2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/images/invokemethod.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/images/mbeans.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/images/new_connection_icon.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/introduction.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/introduction.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/introduction.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -1,135 +1,140 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="intruduction"> - <?dbhtml filename="introduction.html"?> + <?dbhtml filename="introduction.html"?> - <title>Introduction</title> - <para><property>JBoss Tools</property>' JMX project is a fork of <ulink - url="http://code.google.com/p/eclipse-jmx/">eclipse-jmx</ulink>, a project by Jeff Mesnil. + <title>Introduction</title> + <para> + <property>JBoss Tools</property>' JMX project is a fork of <ulink url="http://code.google.com/p/eclipse-jmx/">eclipse-jmx</ulink>, a project by Jeff Mesnil. It was forked with permission. </para> - - <section> - <title>What is JMX?</title> - <para> -The Java Management Extensions (JMX) technology is a standard part of the Java Platform, Standard Edition (Java SE platform). The JMX technology was added to the platform in the Java 2 Platform, Standard Edition (J2SE) 5.0 release. -</para> - <para> -The JMX technology provides a simple, standard way of managing resources such as applications, devices, and services. Because the JMX technology is dynamic, you can use it to monitor and manage resources as they are created, installed and implemented. You can also use the JMX technology to monitor and manage the Java Virtual Machine (Java VM). -</para> - <para> -The JMX specification defines the architecture, design patterns, APIs, and services in the Java programming language for management and monitoring of applications and networks. -</para> - <para> -Using the JMX technology, a given resource is instrumented by one or more Java objects known as Managed Beans, or MBeans. These MBeans are registered in a core-managed object server, known as an MBean server. The MBean server acts as a management agent and can run on most devices that have been enabled for the Java programming language. -</para> - - <para> -The specifications define JMX agents that you use to manage any resources that have been correctly configured for management. A JMX agent consists of an MBean server, in which MBeans are registered, and a set of services for handling the MBeans. In this way, JMX agents directly control resources and make them available to remote management applications. -</para> - <para> -The way in which resources are instrumented is completely independent from the management infrastructure. Resources can therefore be rendered manageable regardless of how their management applications are implemented. -</para> - <para> -The JMX technology defines standard connectors (known as JMX connectors) that enable you to access JMX agents from remote management applications. JMX connectors using different protocols provide the same management interface. Consequently, a management application can manage resources transparently, regardless of the communication protocol used. JMX agents can also be used by systems or applications that are not compliant with the JMX specification, as long as those systems or applications support JMX agents. -</para> -<para> -<ulink - url="http://java.sun.com/docs/books/tutorial/jmx/overview/index.html">Read more about JMX</ulink>. -</para> - </section> - - <section> - <title>What is JMX Tools?</title> - <para><property>JBoss JMX Tools</property> allow to setup multiple JMX connections and provide view - for exploring the JMX tree and execute operations directly from Eclipse.</para> - <para>This chapter covers the basics of working with <property>JMX plugin</property>, which is - used to manage Java applications (with Managed Beans) through JMX and its RMI Connector.</para> + <section> + <title>What is JMX?</title> + <para> + The Java Management Extensions (JMX) technology is a standard part of the Java Platform, Standard Edition (Java SE platform). The JMX technology was added to the platform in the Java 2 Platform, Standard Edition (J2SE) 5.0 release. + </para> + <para> + The JMX technology provides a simple, standard way of managing resources such as applications, devices, and services. Because the JMX technology is dynamic, you can use it to monitor and manage resources as they are created, installed and implemented. You can also use the JMX technology to monitor and manage the Java Virtual Machine (Java VM). + </para> + <para> + The JMX specification defines the architecture, design patterns, APIs, and services in the Java programming language for management and monitoring of applications and networks. + </para> + <para> + Using the JMX technology, a given resource is instrumented by one or more Java objects known as Managed Beans, or MBeans. These MBeans are registered in a core-managed object server, known as an MBean server. The MBean server acts as a management agent and can run on most devices that have been enabled for the Java programming language. + </para> - <figure> - <title>JMX Tools</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/eclipse-jmx_0.2.png"/> - </imageobject> - </mediaobject> - </figure> - </section> + <para> + The specifications define JMX agents that you use to manage any resources that have been correctly configured for management. A JMX agent consists of an MBean server, in which MBeans are registered, and a set of services for handling the MBeans. In this way, JMX agents directly control resources and make them available to remote management applications. + </para> + <para> + The way in which resources are instrumented is completely independent from the management infrastructure. Resources can therefore be rendered manageable regardless of how their management applications are implemented. + </para> + <para> + The JMX technology defines standard connectors (known as JMX connectors) that enable you to access JMX agents from remote management applications. JMX connectors using different protocols provide the same management interface. Consequently, a management application can manage resources transparently, regardless of the communication protocol used. JMX agents can also be used by systems or applications that are not compliant with the JMX specification, as long as those systems or applications support JMX agents. + </para> + <para> + <ulink url="http://java.sun.com/docs/books/tutorial/jmx/overview/index.html">Read more about JMX</ulink>. + </para> + </section> - <section><title>Key Features of JMX Tools</title> - <para>For a start, we propose you to look through the table of main features of JBoss JMX Tools:</para> - <table> - - <title>Key Functionality for JBoss JMX Tools</title> - <tgroup cols="3"> - - <colspec colnum="1" align="left" colwidth="2*"/> - <colspec colnum="2" colwidth="4*"/> - <colspec colnum="3" align="left" colwidth="2*"/> - - <thead> - <row> - <entry>Feature</entry> - <entry>Benefit</entry> - <entry>Chapter</entry> - </row> - </thead> - - <tbody> - - <row> - <entry><para>MBean Explorer</para></entry> - <entry><para>MBean Explorer is a useful view with a text filter that displays domains, mbeans, attributes, and operations inside a connection.</para></entry> - <entry> - <xref linkend="mbean_explorer"/> - </entry> - </row> - - <row> - <entry><para>MBean Editor</para></entry> - <entry><para>MBean Editor is a multi-page editor to manage MBeans.</para></entry> - <entry> - <xref linkend="mbean_editor"/> - </entry> - </row> - </tbody> - </tgroup> - </table> - </section> - - <section> - <title>Requirements and Installation</title> - <section> - <title> Requirements</title> - <para>Requirements to use <property>JBoss JMX Tools</property> are the following:</para> - - <itemizedlist> - <listitem> - <para><property>JBoss JMX Tools</property> is developed on Eclipse 3.4.x milestones</para> - </listitem> - <listitem> - <para><property>JBoss JMX Tools</property> requires that Eclipse is run on a JDK 1.5.0 or above - (due to dependencies on JMX packages which were introduced in Java 1.5.0)</para> - </listitem> - </itemizedlist> - </section> - <section> - <title>Installation</title> - <para>Here, we are going to explain how to install the <property>JMX plugin</property> into - Eclipse.</para> + <section> + <title>What is JMX Tools?</title> + <para> + <productname>JBoss JMX Tools</productname> allows you to setup multiple JMX connections, and provides a view for exploring the JMX tree and execute operations directly from within Eclipse. + </para> - <para><property>JBoss JMX Tools</property> is one module of the <property>JBoss Tools</property> - project. <property> JBoss JMX Tools</property> has no dependency on any other part of <property>JBoss - Tools</property>, and can be downloaded as a standalone Eclipse plugin. Even though the <property>JMX - Tools</property> have no dependencies on other plugins, such as <property>AS Tools</property>, - <property>JBoss JMX Tools</property> do depend on the JMX Tooling and even extend it. </para> + <para> + This chapter covers the basics of working with <productname>JMX plugin</productname>, which is used to manage Java applications (with Managed Beans) through JMX and its RMI Connector. + </para> - <para>You can find the <property>JBoss JBoss Tools</property> plugins over at the <ulink - url="http://labs.jboss.com/tools/download.html">download pages</ulink>. The only - package you'll need to get is the JBoss JMX Tooling, however the <property>AS - Tools</property> would give you a wider experience and more options when using JMX with JBoss Servers. - You can find further download and installation instructions on the JBoss Wiki in the <ulink - url="http://www.jboss.org/tools/download/installation">InstallingJBossTools</ulink> - section.</para> - </section> - </section> + <figure> + <title>JMX Tools</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/eclipse-jmx_0.2.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + + <section> + <title>Key Features of JMX Tools</title> + <para>The table below lists the main features of JBoss JMX Tools:</para> + <table> + + <title>Key Functionality for JBoss JMX Tools</title> + <tgroup cols="3"> + + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="4*"/> + <colspec colnum="3" align="left" colwidth="2*"/> + + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + <entry>Chapter</entry> + </row> + </thead> + + <tbody> + + <row> + <entry> + <para>MBean Explorer</para> + </entry> + <entry> + <para>MBean Explorer is a useful view with a text filter that displays domains, mbeans, attributes, and operations inside a connection.</para> + </entry> + <entry> + <xref linkend="mbean_explorer"/> + </entry> + </row> + + <row> + <entry> + <para>MBean Editor</para> + </entry> + <entry> + <para>MBean Editor is a multi-page editor to manage MBeans.</para> + </entry> + <entry> + <xref linkend="mbean_editor"/> + </entry> + </row> + </tbody> + </tgroup> + </table> + </section> + + <section> + <title>Requirements and Installation</title> + <section> + <title> Requirements</title> + <para>Requirements to use <productname>JBoss JMX Tools</productname> are the following:</para> + + <itemizedlist> + <listitem> + <para> + <productname>JBoss JMX Tools</productname> is developed on Eclipse 3.4.x milestones</para> + </listitem> + <listitem> + <para> + <productname>JBoss JMX Tools</productname> requires that Eclipse is run on a JDK 1.5.0 or above (due to dependencies on JMX packages which were introduced in Java 1.5.0) + </para> + </listitem> + </itemizedlist> + </section> + <section> + <title>Installation</title> + <para>Here, we are going to explain how to install the <productname>JMX plugin</productname> into Eclipse.</para> + + <para> + <productname>JBoss JMX Tools</productname> is one module of the <productname>JBoss Tools</productname> project. <productname> JBoss JMX Tools</productname> has no dependency on any other part of <productname>JBoss Tools</productname>, and can be downloaded as a stand alone Eclipse plugin. Even though the <productname>JMX Tools</productname> have no dependencies on other plugins, such as <productname>AS Tools</productname>, <productname>JBoss JMX Tools</productname> do depend on the JMX Tooling and even extend it. + </para> + + <para> + You can find the <productname>JBoss Tools</productname> plugins over at the <ulink url="http://labs.jboss.com/tools/download.html">download pages</ulink>. The only package you will need to get is the JBoss JMX Tooling, however the <productname>AS Tools</productname> would give you a wider experience and more options when using JMX with JBoss Servers. You can find further download and installation instructions on the JBoss Wiki in the <ulink url="http://www.jboss.org/tools/download/installation">InstallingJBossTools</ulink> section. + </para> + </section> + </section> </chapter> \ No newline at end of file Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/master.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/master.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/master.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -52,12 +52,12 @@ <releaseinfo> Version: 1.1.1.GA </releaseinfo> -<abstract> + </bookinfo> <toc/> Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/references.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/references.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/references.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -1,170 +1,133 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="references"> - <?dbhtml filename="references.html"?> - <title>References</title> - - <section id="mbean_explorer" xreflabel="mbean_explorer"> - <?dbhtml filename="mbean_explorer.html"?> + <?dbhtml filename="references.html"?> + <title>References</title> + + <section id="mbean_explorer" xreflabel="mbean_explorer"> + <?dbhtml filename="mbean_explorer.html"?> + + <title>MBean Explorer</title> + <para> + The <guilabel>MBean Explorer</guilabel> displays the MBean features (both attributes and operations) in its hierarchy. Double-clicking on a feature will open an <property>MBean Editor</property>, displaying the page corresponding to the feature type and select the feature. + </para> + + <figure> + <title>MBean Explorer Features</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/mbean-explorer-features.png"/> + </imageobject> + </mediaobject> + </figure> + + <para> + Since it is possible to have many MBean Editors opened at the same time, the <guilabel>MBean Explorer</guilabel> has the <guibutton>Link With Editor</guibutton> button <inlinemediaobject> <imageobject> <imagedata fileref="images/link-with-editor_0.2.0.png"/></imageobject></inlinemediaobject> to synchronize selections between the active <guilabel>MBean Editor</guilabel> and the <guilabel>MBean Explorer</guilabel> (and vice versa). + </para> + + <para> + The <guilabel>MBean Explorer</guilabel> has also a filter that can be used to filter the available MBeans to show those that interest you. + </para> + + <para> + For example, if you are only interested by MBeans related to memory, typing "memo" will show any node (domain, mbean, attribute, or operation) that matches that text, as well as that node's parents and children. So if an MBean matches, all attributes and operations from that bean will be displayed. If, however, an attribute or operation name (a leaf node) matches, only that node and its parents in the tree will be displayed. + </para> + + <figure> + <title>Query Filter</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/mbean-explorer-query.png"/> + </imageobject> + </mediaobject> + </figure> - <title>MBean Explorer</title> - <para>The <property>MBean Explorer</property> displays the MBean features (both attributes and operations) in its - hierarchy. Double-clicking on a feature will open a <property>MBean Editor</property>, display the page - corresponding to the feature type and select the feature.</para> - - <figure> - <title>MBean Explorer Features</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/mbean-explorer-features.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Since it's possible to have many MBean Editors opened at the same time, the <property>MBean Explorer</property> - has the Link With Editor button - - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/link-with-editor_0.2.0.png"/> - </imageobject> - </inlinemediaobject> - - to synchronize selections between the active <property>MBean Editor</property> and - the <property>MBean Explorer</property> (and vice versa).</para> - - <para>The <property>MBean Explorer</property> has also a filter text that can be used to filter among all the MBeans - the few ones, which interest you.</para> - - <para>For example, if you are only interested by MBeans related to memory, typing memo will show - any node (domain, mbean, attribute, or operation) that matches that text, as well as - that node's parents and children. So if an MBean matches, all attributes and operations from - that bean will show. If, however, an attribute or operation name (a leaf node) matches, - only that node and its parents in the tree will show.</para> - - <figure> - <title>Query Filter</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/mbean-explorer-query.png"/> - </imageobject> - </mediaobject> - </figure> - - - <para>The <emphasis> - <property>Collapse All</property></emphasis> button - - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/collaps_all.png"/> - </imageobject> - </inlinemediaobject> - - on the <property>MBean Explorer</property> toolbar is used to collapse all the MBeans and - display only the domains. It is also possible to double click on a node to expand/collapse it. </para> - - </section> - <section id="mbean_editor" xreflabel="mbean_editor"> - <?dbhtml filename="mbean_editor.html"?> - - <title>MBean Editor</title> - - <figure> - <title>MBean Editor Pages</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/mbean-editor_0.2.0.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>The <property>MBean Editor</property> is composed of several pages:</para> - - <itemizedlist> - <listitem> - <para>the <emphasis> - <property>Attributes</property></emphasis> page</para> - </listitem> - <listitem> - <para>the <emphasis> - <property>Operations</property></emphasis> page</para> - </listitem> - <listitem> - <para>the <emphasis> - <property>Notifications</property></emphasis> page </para> - </listitem> - <listitem> - <para>the <emphasis> - <property>Info</property></emphasis> page </para> - </listitem> - </itemizedlist> - - <para> The <emphasis> - <property>Attributes</property> - </emphasis> and <emphasis> - <property>Operations</property> - </emphasis> pages display a list for either the MBean attributes or operations as well as - details for the selection.</para> - - <para> It is possible to toggle the layout between the list and the details either vertically - (by default) or horizontally with the help of the special icons - - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/mbean-editor-layout-buttons_0.2.0.png"/> - </imageobject> - </inlinemediaobject> - - in the right top corner of the editor.</para> - - <figure> - <title>MBean Editor Horizontal Layout</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/mbean-editor-horizontal-layout_0.2.0.png"/> - </imageobject> - </mediaobject> - </figure> - <figure id="figu-Beginners_Guide-Visual_Web_Tools-Visual_Page_Editor"> - <title>Visual Page Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/mbean-editor-horizontal-layout_0.2.0.png" format="PNG" width="444" /> - </imageobject> - <textobject> - <phrase> - The Visual Page Editor, showing both the source and a visual preview simultaneously. - </phrase> - </textobject> - </mediaobject> - </figure> - <section> - <title>Notifications Page</title> - <para>One more page in the <property>MBean Editor</property> is the <emphasis> - <property>Notifications</property></emphasis> page, which gives the possibility to - subscribe (resp. unsubscribe) to a MBean to receive its notifications by checking (resp. - unchecking) the <emphasis> - <property>Subscribe</property></emphasis> button in the right top corner. </para> - <para>The list of notifications is refreshed every time a new notification is - received:</para> - - <figure> - <title>MBean Editor Notifications Page</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/notifications.png"/> - </imageobject> - </mediaobject> - </figure> - - <note> - <title>Note</title> - <para>It is only possible to subscribe to MBean, which emits notifications (they must be - NotificationBroadcaster).</para> - </note> - - </section> - - </section> - - </chapter> + + <para> + The <guibutton>Collapse All</guibutton> button <inlinemediaobject><imageobject><imagedata fileref="images/collaps_all.png"/></imageobject></inlinemediaobject> on the <property>MBean Explorer</property> toolbar is used to collapse all the MBeans and display only the domains. It is also possible to double click on a node to expand or collapse it. + </para> + + </section> + <section id="mbean_editor" xreflabel="mbean_editor"> + <?dbhtml filename="mbean_editor.html"?> + + <title>MBean Editor</title> + + <figure> + <title>MBean Editor Pages</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/mbean-editor_0.2.0.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>The <property>MBean Editor</property> is composed of several pages:</para> + + <itemizedlist> + <listitem> + <para>the <guilabel>Attributes</guilabel> page</para> + </listitem> + <listitem> + <para>the <guilabel>Operations</guilabel> page</para> + </listitem> + <listitem> + <para>the <guilabel>Notifications</guilabel> page </para> + </listitem> + <listitem> + <para>the <guilabel>Info</guilabel> page </para> + </listitem> + </itemizedlist> + + <para> + The <guilabel>Attributes</guilabel> and <guilabel>Operations</guilabel> pages display a list for either the MBean attributes or operations, as well as details about the selection. + </para> + + <para> + It is possible to toggle the layout between the list and the details either vertically (by default) or horizontally with the help of the special icons <inlinemediaobject><imageobject><imagedata fileref="images/mbean-editor-layout-buttons_0.2.0.png"/></imageobject></inlinemediaobject> in the right top corner of the editor. + </para> + + <figure> + <title>MBean Editor Horizontal Layout</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/mbean-editor-horizontal-layout_0.2.0.png"/> + </imageobject> + </mediaobject> + </figure> + <figure id="figu-Beginners_Guide-Visual_Web_Tools-Visual_Page_Editor"> + <title>Visual Page Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/mbean-editor-horizontal-layout_0.2.0.png" format="PNG" width="444" /> + </imageobject> + <textobject> + <phrase>The Visual Page Editor, showing both the source and a visual preview simultaneously.</phrase> + </textobject> + </mediaobject> + </figure> + <section> + <title>Notifications Page</title> + <para> + The <guilabel>Notifications</guilabel> page provides the ability to subscribe or unsubscribe to an MBean to receive its notifications by checking or unchecking the <guibutton>Subscribe</guibutton> button in the right top corner. + </para> + <para>The list of notifications is refreshed every time a new notification is received:</para> + + <figure> + <title>MBean Editor Notifications Page</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/notifications.png"/> + </imageobject> + </mediaobject> + </figure> + + <note> + <title>Note</title> + <para>It is only possible to subscribe to an MBean that emits notifications (i.e. they must be a NotificationBroadcaster).</para> + </note> + + </section> + + </section> + +</chapter> Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/summary.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/summary.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/summary.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -1,32 +1,23 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter> - <?dbhtml filename="summary.html"?> - <title>Summary</title> - <para>In conclusion, with this document you could easily start with JXM Tools. - The chapters above walked you through the steps on how to do Tomcat,Eclipse Equinox or JBoss Instances managing and how to create new JMX connections. - The document also includes the reference of JMX Tools features. - - If you have questions or suggestions concerned both the documentation and tools behavior, - you are welcome to JBoss Tools Users forum. - Please, use Jira to report bugs and requests on documentation.</para> - - <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/tools</ulink> in the corresponding release directory. - </para> - <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs">http://download.jboss.org/jbosstools/nightly-docs</ulink>. </para> - <para>You can find a set of benefits and other extra information on:</para> - <itemizedlist> - <listitem> - <para> - <ulink url="http://www.jboss.org/community/wiki/JBossMX">JBoss Wiki</ulink> - </para> - </listitem> - <listitem><para>For more information about JMX technology please visit - <ulink url="http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/"> - JMX Technology Home Page</ulink></para> - </listitem> - </itemizedlist> - </section> + <?dbhtml filename="summary.html"?> + <title>Summary</title> + <para> + This document has provided an overview of the functionality included with JXM Tools, as well as walking you through the steps on managing Tomcat, Eclipse Equinox or JBoss Instances and how to create new JMX connections. If you have questions or suggestions concerned both the documentation and tools behavior, you are welcome to JBoss Tools Users forum. Please, use Jira to report bugs and requests on documentation. + </para> + + <section> + <title>Other relevant resources on the topic</title> + <para> + You can find the JBoss Developer Studio/JBoss Tools release documentation at <ulink url="http://docs.jboss.org/tools">http://docs.jboss.org/tools</ulink> in the corresponding release directory. + </para> + <para> + The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs">http://download.jboss.org/jbosstools/nightly-docs</ulink>. + </para> + <para>The JBoss JXM Wiki can be found at <ulink url="http://www.jboss.org/community/wiki/JBossMX">http://www.jboss.org/community/wiki/JBossMX</ulink></para> + <para> + For more information about JMX technology please visit <ulink url="http://java.sun.com/javase/technologies/core/mntr-mgmt/javamanagement/">JMX Technology Home Page</ulink> + </para> + + </section> </chapter> \ No newline at end of file Modified: branches/jbosstools-3.2.x/jmx/docs/reference/en-US/tasks.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/en-US/tasks.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/en-US/tasks.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -1,162 +1,187 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="tasks"> - <?dbhtml filename="tasks.html"?> - <title>JMX Tools Tasks</title> - <para>This chapter will give you answers on most popular questions asked by <property>JMX - plugin</property> users.</para> - <section> - <title>Quick Start</title> - - <para>To start using the <property>JMX Tools</property> it's necessary to open - <property>MBean Explorer</property>. Go to <emphasis><property>Window > Show View > Other</property></emphasis> and then select - <property>MBean Explorer</property> and click <emphasis><property>OK</property>.</emphasis></para> - - <para>The <property>MBean Explorer</property> lists all the domains, mbeans, attributes, and operations inside a - connection. When you double-click a MBean in the <emphasis><property>MBean Explorer</property>,</emphasis> it opens a multi-page - editor to manage the MBean. The <property>MBean Editor</property> is composed of these pages:</para> - - <itemizedlist> - <listitem> - <para><emphasis><property>Attributes page</property>,</emphasis> to get/set the attributes of the MBean</para> - </listitem> - <listitem> - <para><emphasis><property>Operations page</property>,</emphasis> to invoke operations on the MBean</para> - </listitem> - <listitem> - <para><emphasis><property>Notifications page</property>,</emphasis> to receive notifications from the MBean</para> - </listitem> - <listitem> - <para><emphasis><property>Info page</property>,</emphasis> which displays general information about the MBean </para> - </listitem> - </itemizedlist> - - </section> - - <section> - <title>Managing Application</title> + <?dbhtml filename="tasks.html"?> + <title>JMX Tools Tasks</title> + <para>This chapter will provide answers to common questions asked by <property>JMX plugin</property> users.</para> + <section> + <title>Quick Start</title> + <para> + To start using the <property>JMX Tools</property> it is necessary to open <guilabel>MBean Explorer</guilabel>. Select <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Other</guimenuitem></menuchoice>, select <guimenuitem>MBean Explorer</guimenuitem> and click the <guibutton>OK</guibutton> button. + </para> + <para> + The <guilabel>MBean Explorer</guilabel> lists all the domains, MBeans, attributes, and operations inside a connection. When you double-click an MBean in the <guilabel>MBean Explorer</guilabel>, it opens a multi-page editor to manage the MBean. The <guilabel>MBean Editor</guilabel> is composed of these pages: + </para> -<para>As it's been said earlier in the guide the JMX technology allows to monitor and manage Java applications. In this section we will show you how to get connected to -a sample Java application and run the <property>sayHello()</property> method remotely from inside of the <property>MBean Explorer</property>.</para> -<orderedlist> + <itemizedlist> + <listitem> + <para> + <guilabel>Attributes page</guilabel>, to get/set the attributes of the MBean</para> + </listitem> + <listitem> + <para> + <guilabel>Operations page</guilabel>, to invoke operations on the MBean</para> + </listitem> + <listitem> + <para> + <guilabel>Notifications page</guilabel>, to receive notifications from the MBean</para> + </listitem> + <listitem> + <para> + <guilabel>Info page</guilabel>, which displays general information about the MBean </para> + </listitem> + </itemizedlist> + </section> + + <section> + <title>Managing Application</title> + + <para> + As it has been said earlier in the guide, the JMX technology allows you to monitor and manage Java applications. In this section we will show you how to get connected to a sample Java application and run the <code>sayHello()</code> method remotely from inside of the <guilabel>MBean Explorer</guilabel>. + </para> + <orderedlist> +  -<listitem><para>Save the bundle of JMX API sample classes, <ulink url="http://java.sun.com/docs/books/tutorial/jmx/examples/jmx_examples.zip">jmx_examples.zip</ulink>, to your working directory</para></listitem> -<listitem><para>Unzip the bundle of sample classes.</para></listitem> -<listitem><para>Compile the example Java classes from within where you unpacked the files directory.</para> + <listitem> + <para> + Save the bundle of JMX API sample classes, <ulink url="http://java.sun.com/docs/books/tutorial/jmx/examples/jmx_examples.zip">jmx_examples.zip</ulink>, to your working directory. + </para> + </listitem> + <listitem> + <para>Unzip the bundle of sample classes.</para> + </listitem> + <listitem> + <para>Compile the example Java classes from within where you unpacked the files directory.</para> - <programlisting role="XML"><![CDATA[ - javac com/example/*.java - ]]></programlisting> + <programlisting role="XML"><![CDATA[javac com/example/*.java]]></programlisting> -</listitem> -<listitem><para>Start the <property>Main</property> application, specifying the properties that expose Main for remote management:</para> + </listitem> + <listitem> + <para>Start the <code>Main</code> application, specifying the properties that expose <code>Main</code> for remote management:</para> - <programlisting role="XML"><![CDATA[ + <programlisting role="XML"><![CDATA[ java -Dcom.sun.management.jmxremote.port=9999 \ -Dcom.sun.management.jmxremote.authenticate=false \ -Dcom.sun.management.jmxremote.ssl=false \ com.example.Main - ]]></programlisting> + ]]></programlisting> + + <para>If everything was done correctly you will see the <screen>Waiting for incoming requests...</screen> message on the screen.</para> -<para>If everything was done correctly you will see the "Waiting for incoming requests..." message on the screen.</para> + </listitem> + <listitem> + <para> + Now launch the Eclipse IDE, in Eclipse open the <guilabel>MBean Explorer</guilabel>. Go to <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Other</guimenuitem></menuchoice>, select <guimenuitem>MBean Explorer</guimenuitem>, and then click the <guibutton>OK</guibutton> button) + </para> + </listitem> + <listitem> + <para> + Click the <guibutton>New Connection</guibutton> icon <inlinemediaobject><imageobject><imagedata fileref="images/new_connection_icon.png"/></imageobject></inlinemediaobject> in the <guilabel>MBean Explorer</guilabel> menu bar. + </para> + </listitem> + <listitem> + <para> + In the <guilabel>Create JMX Connection</guilabel> dialog, click the <guibutton>Next</guibutton> button and then click the <guilabel>Advanced</guilabel> tab. + </para> + </listitem> - </listitem> - <listitem><para>Now launch the Eclipse IDE, in Eclipse open the <property>MBean Explorer</property>. Go to <emphasis><property>Window > Show View > Other</property></emphasis> and then select - <property>MBean Explorer</property> and click <emphasis><property>OK</property></emphasis>)</para></listitem> - <listitem> - <para>Click the <emphasis> - <property>New Connection</property></emphasis> icon - - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/new_connection_icon.png"/> - </imageobject> - </inlinemediaobject> - - in the <property>MBean Explorer</property> menu - bar.</para> - </listitem> - - <listitem><para>In the <property>Create JMX Connection</property> dialog, hit <property>Next</property> and then click the <property>Advanced</property> tab. </para></listitem> - - - <listitem><para>In the <property>JMX URL</property> input field enter the following URL:</para> - - <programlisting role="XML"><![CDATA[ - service:jmx:rmi:///jndi/rmi://:9999/jmxrmi - ]]></programlisting> - - <figure> - <title>JMX Connection</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/mbeans.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - - <listitem><para>Press <property>Finish</property> to esteblish the connection with the application.</para> - </listitem> - - <listitem><para>Now expand the connection you have just created, then open the <property>com.example</property> package and click <property>sayHello()</property> method. </para> - <para>Once the <property>sayHello()</property> method is clicked the <property>MBean Editor</property> is activated. </para> - - </listitem> - - <listitem><para>In the <property>MBean Editor</property> go to the <property>Operation Details</property> section and hit the <property>sayHello()</property> button.</para><para> You will get the "Operation inoked successfully" message. </para> - - <figure> - <title>Ivoking Method via JMX</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/invokemethod.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - - <listitem><para>The final step is to make sure the application worked as it was expected. Open the terminal where you launched the application in step 3. Now you see the "hello, world" message on the screen. </para> - </listitem> -</orderedlist> + <listitem> + <para>In the <guilabel>JMX URL</guilabel> input field enter the following URL:</para> + <programlisting role="XML"><![CDATA[service:jmx:rmi:///jndi/rmi://:9999/jmxrmi]]></programlisting> - </section> - <section> - <title>Tomcat Managing</title> + <figure> + <title>JMX Connection</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/mbeans.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + + <listitem> + <para>Click the <guibutton>Finish</guibutton> button to establish the connection with the application.</para> + </listitem> + + <listitem> + <para> + Now expand the connection you have just created, open the <guilabel>com.example</guilabel> package, and click the <code>sayHello()</code> method. + </para> + <para>Once the <code>sayHello()</code> method is selected the <guilabel>MBean Editor</guilabel> is activated. </para> + + </listitem> + + <listitem> + <para> + In the <guilabel>MBean Editor</guilabel> go to the <guilabel>Operation Details</guilabel> section and click the <code>sayHello()</code> button. + </para> + <para> You will get the "Operation invoked successfully" message. </para> + + <figure> + <title>Invoking Method via JMX</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/invokemethod.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + + <listitem> + <para> + The final step is to make sure the application worked as expected. Open the terminal where you launched the application in step 3. You should see output similar to the following: + </para> + + <screen>[matthew@localhost jmx_examples]$ java -Dcom.sun.management.jmxremote.port=9999 \ +> -Dcom.sun.management.jmxremote.authenticate=false \ +> -Dcom.sun.management.jmxremote.ssl=false \ +> com.example.Main +Waiting for incoming requests... +hello, world</screen> + </listitem> + </orderedlist> + + </section> + <section> + <title>Tomcat Managing</title> + + <para>It is possible to manage Tomcat using <property>JMX Tools</property>.</para> + + <para>Currently, JMX Tooling is able to connect to Tomcat without authentication or with password-based authentication.</para> + <para> + Using SSL for authentication is not supported: you need to make sure that the System property <guilabel>com.sun.management.jmxremote.ssl</guilabel> is set to false. + </para> + <para> + More information to manage Tomcat can be found in the <ulink url="http://tomcat.apache.org/tomcat-6.0-doc/">Tomcat management documentation</ulink>. + </para> + <para> + Instructions to remotely manage Tomcat are available in <ulink url="http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html">Tomcat's monitoring documentation</ulink>. + </para> - <para>It's possible to manage Tomcat using <property>JMX Tools</property>.</para> - - <para>Currently, JMX Tooling is able to connect to Tomcat without authentication or with - password-based authentication.</para> - <para>Using SSL for authentication is not supported: you need to make sure that the System - property <emphasis> - <property>com.sun.management.jmxremote.ssl</property> - </emphasis> is set to false. </para> - <para>More information to manage Tomcat can be found in <ulink url="http://tomcat.apache.org/tomcat-6.0-doc/">Tomcat management documentation</ulink>.</para> - <para>Instructions to manage remotely Tomcat are available in <ulink url="http://tomcat.apache.org/tomcat-6.0-doc/monitoring.html">Tomcat's monitoring documentation</ulink>.</para> - - - </section> - - <section> - <title>Eclipse Equinox Managing</title> - - <para>You can manage Equinox through the Equinox monitoring framework.</para> - <para>In this section we will show you how to connect to an Equinox server via JBoss JMX tools. First off, you need to make for example a simple servlet and run it on a server. This guide is not intended to teach you how to build application and run them on the server, you can read for example <ulink url="http://www.eclipse.org/equinox-portal/tutorials/server-side/"> this tutorial </ulink> to get a better idea of how to build server-based applications with Eclipse Equinox. </para> - <para>Once you have run an application on the server you can connect to it using JBoss JMX tools.</para> - - <orderedlist> - <listitem> - <para>Go to <emphasis> - <property>Window > Open Perspective > Other</property> - </emphasis> and select the <property>JMX perspective.</property></para> - </listitem> + + </section> + + <section> + <title>Eclipse Equinox Managing</title> + + <para>You can manage Equinox through the Equinox monitoring framework.</para> + <para> + In this section we will show you how to connect to an Equinox server via JBoss JMX tools. First you need to create a simple servlet and run it on a server. The process of building applications and running them on the server is beyond the scope of this documentation, however <ulink url="http://www.eclipse.org/equinox-portal/tutorials/server-side/"> this tutorial </ulink> can be used to give you a better idea of how to build server-based applications with Eclipse Equinox. + </para> + <para>Once you have an application running on the server you can connect to it using JBoss JMX tools.</para> + + <orderedlist> + <listitem> + <para> + Go to <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Open Perspective</guimenuitem><guimenuitem>Other</guimenuitem></menuchoice> and select the <guimenuitem>JMX perspective</guimenuitem>. + </para> + </listitem>  - - <listitem> - <para>Switch to the <property>MBean Explorer</property> by going to <emphasis> - <property>Window > Show View > Other</property> - </emphasis> and selecting the MBean Explorer.</para> - </listitem> - - <listitem> - <para>Click the <emphasis> - <property>New Connection</property></emphasis> icon - - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/new_connection_icon.png"/> - </imageobject> - </inlinemediaobject> - - in the <property>MBean Explorer</property> menu - bar.</para> - </listitem> - - <listitem> - <para>Select the <emphasis> - <property>Advanced tab</property></emphasis> and set the JMX URL to <emphasis> - <property>service:jmx:rmi:///jndi/rmi://:8118/jmxserver.</property> - </emphasis></para> - - <figure> - <title>Using JMX Tools to Access Equinox Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/equinox.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </orderedlist> - - <para>You now have access to the MBeans exposed by Equinox.</para> - </section> + <listitem> + <para> + Switch to the <guilabel>MBean Explorer</guilabel> by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Other</guimenuitem></menuchoice> and selecting the <guimenuitem>MBean Explorer</guimenuitem> option. + </para> + </listitem> + + <listitem> + <para>Click the <guibutton>New Connection</guibutton> icon <inlinemediaobject><imageobject><imagedata fileref="images/new_connection_icon.png"/></imageobject></inlinemediaobject> in the <property>MBean Explorer</property> menu bar.</para> + </listitem> + + <listitem> + <para> + Select the <guilabel>Advanced tab</guilabel> and set the JMX URL to <guilabel>service:jmx:rmi:///jndi/rmi://:8118/jmxserver.</guilabel> + </para> + + <figure> + <title>Using JMX Tools to Access Equinox Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/equinox.png"/> + </imageobject> + </mediaobject> + </figure> + + </listitem> + </orderedlist> + + <para>You now have access to the MBeans exposed by Equinox.</para> + </section> - - <section> - <title>Managing JBoss AS</title> - - <para>Managing JBoss instances is not supported with the <property>JMX Tools</property> - alone. You must also download and install the <property>AS Tools</property> portion of - the <property>JBoss Tools</property> distribution. Even after installing the proper - tooling, you cannot create a JBoss JMX connection yourself or through the Connection - Wizard. The first step is to create a JBoss Server. The full instructions for this can - be found in the AS Tools section, however, the short summary is: </para> - <orderedlist> - <listitem> - <para>Open the <property>Servers</property> view.</para> - </listitem> - - <listitem> - <para>Right-click in the view and select <emphasis> - <property>New > Server</property> - </emphasis>.</para> - </listitem> - - <listitem> - <para>In the <emphasis> - <property>JBoss Enterprise Middleware</property> - </emphasis> or in <emphasis> - <property>JBoss Community</property> - </emphasis> section, select a server version.</para> - </listitem> - - <listitem> - <para>If a runtime has not yet been created, you'll be prompted for the - server's home directory, JDK, and configuration.</para> - </listitem> - - <listitem> - <para>Finish the wizard and note that you have a new entry in both the - <property>Servers</property> view and the <property>MBean - Explorer</property>.</para> - </listitem> - - <listitem> - <para>Start the server by right-clicking it and selecting <emphasis> - <property>Start</property></emphasis>.</para> - </listitem> - <listitem> - <para>Note that once the server is started, the JMX connection can be - expanded.</para> - </listitem> - </orderedlist> - - <para>Now you can explore MBeans exposed by a JBoss instance.</para> - </section> + + <section> + <title>Managing JBoss AS</title> + + <para> + Managing JBoss instances is not supported with the <guilabel>JMX Tools</guilabel> alone. You must also download and install the <guilabel>AS Tools</guilabel> portion of the <guilabel>JBoss Tools</guilabel> distribution. Even after installing the proper tooling, you cannot create a JBoss JMX connection yourself or through the Connection Wizard. The first step is to create a JBoss Server. The full instructions for this can be found in the AS Tools section, however, the short summary is: + </para> + <orderedlist> + <listitem> + <para>Open the <guilabel>Servers</guilabel> view.</para> + </listitem> + + <listitem> + <para>Bring up the views context menu and select <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>Server</guimenuitem></menuchoice>.</para> + </listitem> + + <listitem> + <para>In the <guilabel>JBoss Enterprise Middleware</guilabel> or in <guilabel>JBoss Community</guilabel> section, select a server version.</para> + </listitem> + + <listitem> + <para>If a runtime has not yet been created, you will be prompted for the server's home directory, JDK, and configuration.</para> + </listitem> + + <listitem> + <para> + Finish the wizard and note that you have a new entry in both the <guilabel>Servers</guilabel> view and the <guilabel>MBean Explorer</guilabel>. + </para> + </listitem> + + <listitem> + <para>Start the server by right-clicking it and selecting the <guimenuitem>Start</guimenuitem> option.</para> + </listitem> + <listitem> + <para>Note that once the server is started, the JMX connection can be expanded.</para> + </listitem> + </orderedlist> + + <para>Now you can explore MBeans exposed by a JBoss instance.</para> + </section> - <section> - <title>Managing JBoss AS Remotely</title> - - <para>JBoss JMX Tool allow you to easily get access and mangane JBoss AS server remotely. - In order to get connected to the instance of JBoss AS remotely you need to run the server or make sure the server is lauched. + <section> + <title>Managing JBoss AS Remotely</title> + + <para> + The JBoss JMX Tools allow you to easily access and manage a JBoss AS server remotely. In order to connect to the instance of JBoss AS remotely you need to run the server or make sure the server is launched. </para> - <orderedlist> - <listitem> - <para>Go to <emphasis> - <property>Window > Open Perspective > Other</property> - </emphasis> and select the <property>JMX perspective.</property></para> - </listitem> - <listitem> - <para>Switch to the <property>MBean Explorer</property> by going to <emphasis> - <property>Window > Show View > Other</property> - </emphasis> and selecting the MBean Explorer.</para> - </listitem> - - <listitem> - <para>Click the <emphasis> - <property>New Connection</property></emphasis> icon - - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/new_connection_icon.png"/> - </imageobject> - </inlinemediaobject> - - in the <property>MBean Explorer</property> menu - bar.</para> - </listitem> - - <listitem> - <para>Select the <emphasis> - <property>Advanced tab</property></emphasis> and set the JMX URL to: </para> - <programlisting role="XML"><![CDATA[ -service:jmx:rmi://localhost/jndi/rmi://localhost:1090/jmxconnector - ]]></programlisting> - - <para>Please, note that in this example we connected to the local host. </para> - </listitem> - </orderedlist> - </section> - <section id="extensions" xreflabel="extensions"> - <title>Extension Task</title> - <para>This section will outline how to contribute your own Server type with some default - behavior.</para> + <orderedlist> + <listitem> + <para>Select <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Open Perspective</guimenuitem><guimenuitem>Other</guimenuitem></menuchoice> and select the <guimenuitem>JMX perspective</guimenuitem> option. + </para> + </listitem> + <listitem> + <para>Switch to the <guilabel>MBean Explorer</guilabel> by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Other</guimenuitem></menuchoice> and selecting the <guimenuitem>MBean Explorer</guimenuitem> option.</para> + </listitem> + + <listitem> + <para> + Click the <guibutton>New Connection</guibutton> icon <inlinemediaobject><imageobject><imagedata fileref="images/new_connection_icon.png"/></imageobject></inlinemediaobject>in the <guilabel>MBean Explorer</guilabel> menu bar. + </para> + </listitem> + + <listitem> + <para>Select the <guilabel>Advanced</guilabel> tab and set the JMX URL to:</para> + <programlisting role="XML"><![CDATA[service:jmx:rmi://localhost/jndi/rmi://localhost:1090/jmxconnector]]></programlisting> + + <para>Please note that in this example we are connected to the local host. </para> + </listitem> + </orderedlist> + </section> + <section id="extensions" xreflabel="extensions"> + <title>Extension Task</title> + <para>This section will outline how to contribute your own Server type with some default behavior.</para> + + <section> + <title>Why we should do that?</title> + + <para> + You might be asking yourself why you would need to extend this framework if JMX is a standard. Perhaps you want a connection to be automatically created after some specific action, or perhaps you want your connection wizard to do more than simply set a host and port. JBoss, for example, requires setting some credentials on the client machine, but uses JBoss classes to do it. This requires that the connection has access to the JBoss JARs. + </para> + </section> + + <section> + <title>Core Extensions</title> + + <para> + To create your own JMX Connection type, you must use the <code>org.jboss.tools.jmx.core.MBeanServerConnectionProvider</code> extension point. This point takes one child, a connectionProvider with a class that implements <code>org.jboss.tools.jmx.core.IConnectionProvider</code>. + </para> + + <para> + An <code>IConnectionProvider</code> is responsible for creation and deletion of <code>IConnectionWrapper</code> objects. It must also keep a list of listeners that it is expected to notify when a connection is added or removed from its list. + </para> + + <para> + Each <code>IConnectionWrapper</code> is expected to be able to run arbitrary JMX runnables or getting a "Root" object representing all JMX nodes. There are some utility methods the <code>IConnectionWrapper</code> can make use of. + </para> + </section> + + <section> + <title>UI Extensions</title> + <para>There are two extension points currently approved for use in the UI</para> + <itemizedlist> + <listitem> + <para> + <code>org.jboss.tools.jmx.ui.providerUI</code> - provide an icon, id, displayable name, and wizardPage class for creation of new connections + </para> + </listitem> + <listitem> + <para> + <code>org.jboss.tools.jmx.ui.attribute.controls</code> - allows you to map class types to some Control to present them in the MBean Editor + </para> + <para>We hope this guide helped you to get started with the JBoss JMX Tools. For additional information you are welcome on the <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para> + </listitem> + </itemizedlist> + </section> + + </section> + <section id="connection" xreflabel="connection"> + + <title>Connections Creation Task</title> + + <para> + The <property>MBean Explorer</property> supports several different types of connections. The tooling itself comes only with a default connection type, however other adopters can provide additional connection types that may require additional or non-spec behavior. Connections can be in either the connected state or the disconnected state. Some connection types (such as the default connection type) allow you to control the current state. Other connection types may not. + </para> + + <para> + Similarly, some connection types may be able to be created, and others may not. The default connection type, for example, can be created and deleted at will. The AS Tools connection type, which represents a JBoss server, does not allow you this level of control. A JBoss JMX connection is created when a JBoss server is created in the server's view, and deleted when said server is deleted. The JMX connection for this server is in the connected state only when the server is started. + </para> - <section> - <title>Why we should do that?</title> - - <para>You might be asking yourself why you'd need to extend this framework if JMX is - a standard. Perhaps you want a connection to be automatically created after some specific - action, or perhaps you want your connection wizard to do more than simply set a host and - port. JBoss, for example, requires setting some credentials on the client machine, but - using JBoss classes to do it. This requires that the connection have access to JBoss - jars.</para> - </section> - - <section> - <title>Core Extensions</title> - - <para>To create your own JMX Connection type, you must use the - org.jboss.tools.jmx.core.MBeanServerConnectionProvider extension point. This point takes - one child, a connectionProvider with a class that implements - org.jboss.tools.jmx.core.IConnectionProvider.</para> - - <para>An IConnectionProvider is responsible for creation and deletion of IConnectionWrapper - objects. It must also keep a list of listeners that it is expected to inform when a - connection is added or removed from its list. </para> - - <para>Each IConnectionWrapper is expected to handle running arbitrary JMX runnables or getting - a "Root" object representing all JMX nodes. There are some utility methods the - IConnectionWrapper can make use of.</para> - </section> - - <section> - <title>UI Extensions</title> - <para>There are two extension points currently approved for use in the UI</para> - <itemizedlist> - <listitem> - <para>org.jboss.tools.jmx.ui.providerUI - provide an icon, id, displayable name, and - wizardPage class for creation of new connections</para> - </listitem> - <listitem> - <para>org.jboss.tools.jmx.ui.attribute.controls - allows you to map class types to some - Control to present them in the MBean Editor</para> - <para>We hope, this guide helped you to get started with the JBoss JMX Tools. Besides, for additional information you are welcome on <ulink - url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para> - </listitem> - </itemizedlist> - </section> - - </section> - <section id="connection" xreflabel="connection"> - - <title>Connections Creation Task</title> - - <para>The <property>MBean Explorer</property> supports several different types of connections. - The tooling itself comes only with a default connection type, however other - adopters can provide additional connection types that may require additional - or non-spec behavior. Connections can be in either the connected state or - the disconnected state. Some connection types (such as the default connection type) - allow you to control the current state. Other connection types may not. </para> - - <para>Similarly, some connection types may be able to be created, and others may not. - The default connection type, for example, can be created and deleted by you - at will. The AS Tools connection type, which represents a JBoss server, does not - allow you this level of control. A JBoss JMX connection is created when a JBoss server is created - in the server's view, and deleted when said server is deleted. The JMX connection for - this server is in the connected state only when the server is started. </para> - - - <section><title>Establishing Connection</title> - - <para> There are two ways to connect to an application with remote management enabled:</para> - - <para> The first step is the same for both - to connect to a MBean Server, click the - <emphasis> - <property>New Connection</property></emphasis> icon - - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/new_connection_icon.png"/> - </imageobject> - </inlinemediaobject> - - in the <property>MBean Explorer</property> menu bar.</para> - - <para>Then to follow the simple one you just need to specify host, port (and optionally user - name and password) and click <emphasis> - <property>OK</property>.</emphasis></para> - <para>On the <property>Advanced</property> tab you can set the sever name (it will be displayed in <property>MBean Explorer</property>), a url to the remote server. - For example, to connect to JBoss AS you need to set the <property>JMX URL</property> to - </para> - <programlisting role="XML"><![CDATA[ -service:jmx:rmi://localhost/jndi/rmi://localhost:1090/jmxconnector - ]]></programlisting> - <para>If it is required you can enter user name and password for the server connection. - </para> - - - <note> - <title>Note</title> - <para>Only JMX URL based on RMI are supported.</para> - </note> - </section> - </section> + + <section> + <title>Establishing Connection</title> + + <para> There are two ways to connect to an application with remote management enabled:</para> + + <para> + The first step is the same for both methods - to connect to a MBean Server, click the <guibutton>New Connection</guibutton> icon <inlinemediaobject><imageobject><imagedata fileref="images/new_connection_icon.png"/></imageobject></inlinemediaobject> in the <guilabel>MBean Explorer</guilabel> menu bar. + </para> + + <para> + The simple method is to specify the host, port (and optionally user name and password) and click the <guibutton>OK</guibutton> button. + </para> + <para> + On the <guilabel>Advanced</guilabel> tab you can set the sever name (it will be displayed in <guilabel>MBean Explorer</guilabel>), and a URL to the remote server. For example, to connect to JBoss AS you need to set the <guilabel>JMX URL</guilabel> to + </para> + <programlisting role="XML"><![CDATA[service:jmx:rmi://localhost/jndi/rmi://localhost:1090/jmxconnector]]></programlisting> + <para>If it is required you can enter user name and password for the server connection. </para> + <note> + <title>Note</title> + <para>Only JMX URL based on RMI are supported.</para> + </note> + </section> + </section> </chapter> Modified: branches/jbosstools-3.2.x/jmx/docs/reference/pom.xml =================================================================== --- branches/jbosstools-3.2.x/jmx/docs/reference/pom.xml 2011-07-18 02:08:54 UTC (rev 32978) +++ branches/jbosstools-3.2.x/jmx/docs/reference/pom.xml 2011-07-18 02:11:21 UTC (rev 32979) @@ -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>JMX_Tools_Reference_Guide</docname> - <bookname>JMX Tools Reference Guide</bookname> - </properties> - - <profiles> + <properties> + <translation>en-US</translation> + <docname>JMX_Tools_Reference_Guide</docname> + <bookname>JMX Tools Reference Guide</bookname> + </properties> + <profiles> +  - <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>  - <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>  - <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>  - <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>  - <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>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>

14 years, 9 months

1
0
0 / 0

JBoss Tools SVN: r32978 - in branches/jbosstools-3.2.x/jbpm/docs/converter_ref: en-US and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2011-07-17 22:08:54 -0400 (Sun, 17 Jul 2011) New Revision: 32978 Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/BPMN_Convert_User_Guide.ent branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/BPMN_Convert_User_Guide.xml branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Book_Info.xml branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Feedback.xml branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Preface.xml branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/bpmn2jpdl.xml branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_1.png branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_2.png branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_3.png branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_4.png branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_5.png branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_7.png branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_8.png branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/master.xml branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/overview.xml branches/jbosstools-3.2.x/jbpm/docs/converter_ref/pom.xml Log: updated for GA Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/BPMN_Convert_User_Guide.ent =================================================================== --- branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/BPMN_Convert_User_Guide.ent 2011-07-18 02:06:02 UTC (rev 32977) +++ branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/BPMN_Convert_User_Guide.ent 2011-07-18 02:08:54 UTC (rev 32978) @@ -1,4 +1,7 @@ <!ENTITY PRODUCT "JBoss"> <!ENTITY BOOKID "BPMN_Convert_User_Guide"> -<!ENTITY YEAR "2010"> +<!ENTITY YEAR "2011"> <!ENTITY HOLDER "Red Hat"> +<!ENTITY BZPRODUCT "JBoss Developer Studio"> +<!ENTITY BZCOMPONENT "BPMN Convert User Guide"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Develope...'>http://bugzilla.redhat.com/</ulink>"> Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/BPMN_Convert_User_Guide.xml =================================================================== --- branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/BPMN_Convert_User_Guide.xml 2011-07-18 02:06:02 UTC (rev 32977) +++ branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/BPMN_Convert_User_Guide.xml 2011-07-18 02:08:54 UTC (rev 32978) @@ -6,5 +6,6 @@ <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="bpmn2jpdl.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/jbpm/docs/converter_ref/en-US/Book_Info.xml =================================================================== --- branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Book_Info.xml 2011-07-18 02:06:02 UTC (rev 32977) +++ branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Book_Info.xml 2011-07-18 02:08:54 UTC (rev 32978) @@ -5,9 +5,9 @@ <title>BPMN Convert User Guide</title> <subtitle>Provides information relating to the BPMN Convert 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 BPMN Convert User Guide explains how to use the BPMN Convert module to translate a BPMN file to a JPDL file.</para> </abstract> Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Feedback.xml =================================================================== --- branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Feedback.xml 2011-07-18 02:06:02 UTC (rev 32977) +++ branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Feedback.xml 2011-07-18 02:08:54 UTC (rev 32978) @@ -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=12310500&issu...">https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...</ulink> - </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> +  <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/jbpm/docs/converter_ref/en-US/Preface.xml =================================================================== --- branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Preface.xml 2011-07-18 02:06:02 UTC (rev 32977) +++ branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/Preface.xml 2011-07-18 02:08:54 UTC (rev 32978) @@ -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.html">Red Hat Documentation</ulink> website under the <guilabel>JBoss Developer Studio</guilabel> section. </para> -  </preface> Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/bpmn2jpdl.xml =================================================================== --- branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/bpmn2jpdl.xml 2011-07-18 02:06:02 UTC (rev 32977) +++ branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/bpmn2jpdl.xml 2011-07-18 02:08:54 UTC (rev 32978) @@ -1,137 +1,136 @@ <?xml version="1.0" encoding="ISO-8859-1"?> -<chapter id="bpmn2jpdl" > - <title>Translate a Bpmn file to a JPDL file</title> - <para>This chapter provides you with the necessary steps to translate a Bpmn file to a JPDL file.</para> - - <section id="createproject"> - <title>Creating a project</title> - <para>Before creating a Bpmn file, you should have a Project created.</para> - <para> +<chapter id="bpmn2jpdl"> + <title>Translate a BPMN file to a JPDL file</title> + <para>This chapter provides you with the necessary steps to translate a BPMN file to a JPDL file.</para> + + <section id="createproject"> + <title>Creating a project</title> + <para>Before creating a BPMN file, you should have a Project created.</para> + <para> Create a project by selecting <menuchoice> <guimenuitem>File</guimenuitem> - <guimenuitem>New</guimenuitem> - <guimenuitem>Project...</guimenuitem> - <guimenuitem>General</guimenuitem> - <guimenuitem>Project</guimenuitem> - </menuchoice>. + <guimenuitem>New</guimenuitem> + <guimenuitem>Project...</guimenuitem> + <guimenuitem>General</guimenuitem> + <guimenuitem>Project</guimenuitem> + </menuchoice>. </para> - <para>Enter <guilabel>test</guilabel> in the <guilabel>Project name</guilabel> field, and click the <guibutton>Finish</guibutton> button.</para> - <figure> - <title>Creating a Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpmnconvert_bpmn2jpdl_1.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - </section> - <section id="createbpmnfile"> - <title>Creating a BPMN file using the STP BPMN editor</title> - <para>Create a BPMN diagram file by selecting + <para>Enter <guilabel>test</guilabel> in the <guilabel>Project name</guilabel> field, and click the <guibutton>Finish</guibutton> button.</para> + <figure> + <title>Creating a Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpmnconvert_bpmn2jpdl_1.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="createbpmnfile"> + <title>Creating a BPMN file using the STP BPMN editor</title> + <para>Create a BPMN diagram file by selecting <menuchoice> <guimenuitem>File</guimenuitem> - <guimenuitem>New</guimenuitem> - <guimenuitem>Other...</guimenuitem> - <guimenuitem>Other</guimenuitem> - <guimenuitem>Bpmn Diagram</guimenuitem> - </menuchoice>. + <guimenuitem>New</guimenuitem> + <guimenuitem>Other...</guimenuitem> + <guimenuitem>Other</guimenuitem> + <guimenuitem>Bpmn Diagram</guimenuitem> + </menuchoice>. </para> - - <para>Enter <guilabel>test</guilabel> in the <guilabel>File name</guilabel> field, and click the <guibutton>Finish</guibutton> button.</para> - - <figure> - <title>Creating BPMN Diagram</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpmnconvert_bpmn2jpdl_2.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - <para>Open the <guilabel>test.bpmn_diagram</guilabel> file by double-clicking it.</para> - <para>Draw the Bpmn diagram using the STP BPMN editor. For more information on how to use the STP BPMN editor, please visit the <ulink url="http://www.eclipse.org/bpmn/">BPMN project page</ulink>.</para> - </section> - <section id="bpmntojpdl"> - <title>Exporting a Bpmn File to Jpdl files</title> - <para>A Bpmn file may include more than one pool. Every pool can be mapped to a corresponding Jpdl file.</para> - <itemizedlist> - <listitem> - <para>Select the <guilabel>test.bpmn</guilabel> file and right-click on it. Open the export wizard by selecting + + <para>Enter <guilabel>test</guilabel> in the <guilabel>File name</guilabel> field, and click the <guibutton>Finish</guibutton> button.</para> + + <figure> + <title>Creating BPMN Diagram</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpmnconvert_bpmn2jpdl_2.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>Open the <guilabel>test.bpmn_diagram</guilabel> file by double-clicking it.</para> + <para>Draw the BPMN diagram using the STP BPMN editor. For more information on how to use the STP BPMN editor, please visit the <ulink url="http://www.eclipse.org/bpmn/">BPMN project page</ulink>.</para> + </section> + <section id="bpmntojpdl"> + <title>Exporting a BPMN File to JPDL files</title> + <para>A BPMN file may include more than one pool. Every pool can be mapped to a corresponding JPDL file.</para> + <itemizedlist> + <listitem> + <para>Select the <guilabel>test.bpmn</guilabel> file and right-click on it. Open the export wizard by selecting <menuchoice> <guimenuitem>Export...</guimenuitem> - <guimenuitem>BPMN</guimenuitem> - <guimenuitem>BPMN to jPDL...</guimenuitem> - </menuchoice> + <guimenuitem>BPMN</guimenuitem> + <guimenuitem>BPMN to JPDL...</guimenuitem> + </menuchoice> from the context menu. </para> - <para>Click the <guibutton>Next</guibutton> button.</para> - <figure> - <title>BPMN Export</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpmnconvert_bpmn2jpdl_3.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - - </listitem> - <listitem> - <para>Select the BPMN file that you want to translate, and click the <guibutton>Next</guibutton> button. + <para>Click the <guibutton>Next</guibutton> button.</para> + <figure> + <title>BPMN Export</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpmnconvert_bpmn2jpdl_3.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + + </listitem> + <listitem> + <para>Select the BPMN file that you want to translate, and click the <guibutton>Next</guibutton> button. </para> - <figure> - <title>Choosing a BPMN File</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpmnconvert_bpmn2jpdl_4.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Select the BPMN Pools that you want to translate, and click the <guibutton>Next</guibutton> button. + <figure> + <title>Choosing a BPMN File</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpmnconvert_bpmn2jpdl_4.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Select the BPMN Pools that you want to translate, and click the <guibutton>Next</guibutton> button. </para> - <figure> - <title>Choosing BPMN Pools</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpmnconvert_bpmn2jpdl_5.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>On the next page, you may get error or warning messages that occurred during the conversion. If there are no messages, this page is skipped. + <figure> + <title>Choosing BPMN Pools</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpmnconvert_bpmn2jpdl_5.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>On the next page, you may get error or warning messages that occurred during the conversion. If there are no messages, this page is skipped. </para> - <para>Click on the <guibutton>Next</guibutton> button.</para> - </listitem> - <listitem> - <para>Select the target location where the generated JPDL files will be saved. If you'd like to overwrite existing resources,check this "Overwrite existing resources" checkbox. + <para>Click on the <guibutton>Next</guibutton> button.</para> + </listitem> + <listitem> + <para>Select the target location where the generated JPDL files will be saved. If you'd like to overwrite existing resources,check this "Overwrite existing resources" checkbox. </para> - <para>Click on the <guibutton>Finish</guibutton> button to generate the JPDL files in the target location.</para> - <figure> - <title>Target Location</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpmnconvert_bpmn2jpdl_7.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - + <para>Click on the <guibutton>Finish</guibutton> button to generate the JPDL files in the target location.</para> + <figure> + <title>Target Location</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpmnconvert_bpmn2jpdl_7.png"></imagedata> + </imageobject> + </mediaobject> + </figure> - <para></para> - </listitem> - </itemizedlist> - <para>The generated files look like this: </para> - <figure> - <title>The Generated JPDL Files</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/bpmnconvert_bpmn2jpdl_8.png"></imagedata> - </imageobject> - </mediaobject> - </figure> - <para>We hope this guide helped you to get started with the JBoss BPMN Convert module. For additional information and support please visit the <ulink - url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para> - </section> - + + <para></para> + </listitem> + </itemizedlist> + <para>The generated files look like this: </para> + <figure> + <title>The Generated JPDL Files</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/bpmnconvert_bpmn2jpdl_8.png"></imagedata> + </imageobject> + </mediaobject> + </figure> + <para>We hope this guide helped you to get started with the JBoss BPMN Convert module. For additional information and support please visit the <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para> + </section> + </chapter> \ No newline at end of file Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_1.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_3.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_4.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_5.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_7.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/images/bpmnconvert_bpmn2jpdl_8.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/master.xml =================================================================== --- branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/master.xml 2011-07-18 02:06:02 UTC (rev 32977) +++ branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/master.xml 2011-07-18 02:08:54 UTC (rev 32978) @@ -32,12 +32,12 @@ <releaseinfo> Version: 1.1.0.GA </releaseinfo> -<abstract> + </bookinfo> Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/overview.xml =================================================================== --- branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/overview.xml 2011-07-18 02:06:02 UTC (rev 32977) +++ branches/jbosstools-3.2.x/jbpm/docs/converter_ref/en-US/overview.xml 2011-07-18 02:08:54 UTC (rev 32978) @@ -1,15 +1,32 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="overview"> - <title>BPMN Convert Overview</title> - <para>This chapter gives you a short overview of JBoss BPMN Convert module.</para> - <para>JBoss BPMN Convert module is a tool used for a BPMN file translation.</para> - <para>As a part of JBoss tools, JBoss BPMN Convert module implements BPMN to JPDL translation. You can get a basic JPDL file from a BPMN file by using this module.</para> - <para>The BPMN file may be written by hand, or with the help of an editor. In this guide, we use the STP BPMN editor to draw a BPMN file.</para> - <para>You can download the editor, which is included with the BPMN Modeler, using Eclipse and the SOA Tools project update site. You can find the necessary links and other related information on the <ulink url="http://www.eclipse.org/bpmn">Eclipse BPMN project page</ulink>.</para> + <title>BPMN Convert Overview</title> + <para> + This chapter provides a short overview of the JBoss BPMN Convert module, which is a tool used to translate BPMN files. Specifically, the JBoss BPMN Convert module allows you to translate BPMN files to a basic JPDL. + </para> + <para>The BPMN file may be written by hand, or created with the aid of an editor. In this guide, we will use the STP BPMN editor to draw a BPMN file.</para> + <para> + You can download the editor, which is included with the BPMN Modeler, using Eclipse and the SOA Tools project update site. You can find the necessary links and other related information on the <ulink url="http://www.eclipse.org/bpmn">Eclipse BPMN project page</ulink>. + </para> + + <note> + <title>Note</title> + <para> + In order to satisfy the dependencies when installing the BPMN Modeler, you will need to add the following update sites to JBDS: + <itemizedlist> + <listitem> + <para><ulink url="http://download.eclipse.org/stp/updates/helios">http://download.eclipse.org/stp/updates/helios</ulink></para> + </listitem> + <listitem> + <para><ulink url="http://download.eclipse.org/releases/helios">http://download.eclipse.org/releases/helios</ulink></para> + </listitem> + </itemizedlist> + </para> + </note> <section> <title>Key Features of JBoss BPMN Convert module</title> - <para>To start, take a look through the table of JBoss BPMN Convert module main features:</para> + <para>The table below lists the main features of the JBoss BPMN Convert module:</para> <table> @@ -32,7 +49,7 @@ <row> <entry><para>STP BPMN Editor</para></entry> - <entry><para>JBoss BPMN Convert module contains the STP Business Process Modeling Notation (BPMN) Editor, which is a tool to express any processes in a graphical form (as simple diagrams with a set of graphical elements). These BPMN files can then be converted to jPDL.</para></entry> + <entry><para>JBoss BPMN Convert module contains the STP Business Process Modeling Notation (BPMN) Editor, which is a tool to express any processes in a graphical form (as simple diagrams with a set of graphical elements). These BPMN files can then be converted to JPDL.</para></entry> <entry> <xref linkend="createbpmnfile"/> </entry> Modified: branches/jbosstools-3.2.x/jbpm/docs/converter_ref/pom.xml =================================================================== --- branches/jbosstools-3.2.x/jbpm/docs/converter_ref/pom.xml 2011-07-18 02:06:02 UTC (rev 32977) +++ branches/jbosstools-3.2.x/jbpm/docs/converter_ref/pom.xml 2011-07-18 02:08:54 UTC (rev 32978) @@ -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>Converter_Reference_Guide</docname> - <bookname>Converter Reference Guide</bookname> - </properties> - - <profiles> + <properties> + <translation>en-US</translation> + <docname>Converter_Reference_Guide</docname> + <bookname>Converter Reference Guide</bookname> + </properties> + <profiles> +  - <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>  - <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>  - <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>  - <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>  - <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>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>

14 years, 9 months

1
0
0 / 0

JBoss Tools SVN: r32977 - in branches/jbosstools-3.2.x/as/docs/reference: en-US and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2011-07-17 22:06:02 -0400 (Sun, 17 Jul 2011) New Revision: 32977 Added: branches/jbosstools-3.2.x/as/docs/reference/en-US/images/icon.svg Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/Book_Info.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/Feedback.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/JBoss_Server_Manager_Reference_Guide.ent branches/jbosstools-3.2.x/as/docs/reference/en-US/JBoss_Server_Manager_Reference_Guide.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/Preface.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/Revision_History.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/master.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/modules.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/perspective.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/quick_start.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/runtimes_servers.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/tptp_support.xml branches/jbosstools-3.2.x/as/docs/reference/en-US/webtools.xml branches/jbosstools-3.2.x/as/docs/reference/pom.xml Log: updated for GA Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/Book_Info.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/Book_Info.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/Book_Info.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -5,9 +5,9 @@ <title>JBoss Server Manager Reference Guide</title> <subtitle>Provides information relating to the JBoss Server Manager.</subtitle> <productname>JBoss Developer Studio</productname> - <productnumber>4.0</productnumber> - <edition>4.0.0</edition> - <pubsnumber>5</pubsnumber> + <productnumber>4.1</productnumber> + <edition>4.1.0</edition> + <pubsnumber>1</pubsnumber> <abstract> <para>The JBoss Server Manager Reference Guide explains how to use the JBoss Server Manager to configure, start, stop the server, to know deployment and archiving processes.</para> </abstract> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/Feedback.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/Feedback.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/Feedback.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -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=12310500&issu...">https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...</ulink> - </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> +  <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/as/docs/reference/en-US/JBoss_Server_Manager_Reference_Guide.ent =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/JBoss_Server_Manager_Reference_Guide.ent 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/JBoss_Server_Manager_Reference_Guide.ent 2011-07-18 02:06:02 UTC (rev 32977) @@ -1,4 +1,7 @@ <!ENTITY PRODUCT "JBoss"> <!ENTITY BOOKID "JBoss_Server_Manager_Reference_Guide"> -<!ENTITY YEAR "2010"> +<!ENTITY YEAR "2011"> <!ENTITY HOLDER "Red Hat"> +<!ENTITY BZPRODUCT "JBoss Developer Studio"> +<!ENTITY BZCOMPONENT "Server Manager Reference Guide"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Develope...'>http://bugzilla.redhat.com/</ulink>"> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/JBoss_Server_Manager_Reference_Guide.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/JBoss_Server_Manager_Reference_Guide.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/JBoss_Server_Manager_Reference_Guide.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -10,5 +10,6 @@ <xi:include href="webtools.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="modules.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="tptp_support.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/as/docs/reference/en-US/Preface.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/Preface.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/Preface.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -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.html">Red Hat Documentation</ulink> website under the <guilabel>JBoss Developer Studio</guilabel> section. </para> -  </preface> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/Revision_History.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/Revision_History.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/Revision_History.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -1,4 +1,52 @@ <?xml version='1.0' encoding='utf-8' ?> <!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</surname><email></email></author><revdescription><simplelist><member>General updates</member></simplelist></revdescription></revision><revision><revnumber>0</revnumber><date>Fri Nov 20 2009</date><author><firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email></author><revdescription><simplelist><member>Initial creation of book by publican</member></simplelist></revdescription></revision></revhistory></simpara></appendix> +<appendix> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>2</revnumber> + <date>Mon Jan 31 2011</date> + <author> + <firstname>Matthew</firstname> + <surname>Casperson</surname> + <email>mcaspers(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>General updates</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>1</revnumber> + <date>Wed Jun 09 2010</date> + <author> + <firstname>JBoss Tools</firstname> + <surname>Documentation Team</surname> + <email></email> + </author> + <revdescription> + <simplelist> + <member>General updates</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>0</revnumber> + <date>Fri Nov 20 2009</date> + <author> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + <email>irooskov(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>Initial creation of book by publican</member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </simpara> +</appendix> Added: branches/jbosstools-3.2.x/as/docs/reference/en-US/images/icon.svg =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/images/icon.svg (rev 0) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/images/icon.svg 2011-07-18 02:06:02 UTC (rev 32977) @@ -0,0 +1,3936 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> + +<svg + xmlns:ns="http://ns.adobe.com/AdobeSVGViewerExtensions/3/" + xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/" + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + version="1.0" + width="32" + height="32" + id="svg3017" + sodipodi:version="0.32" + inkscape:version="0.44+devel" + sodipodi:docname="book.svg" + sodipodi:docbase="/home/andy/Desktop"> + <metadata + id="metadata489"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + </cc:Work> + </rdf:RDF> + </metadata> + <sodipodi:namedview + inkscape:window-height="480" + inkscape:window-width="858" + inkscape:pageshadow="0" + inkscape:pageopacity="0.0" + guidetolerance="10.0" + gridtolerance="10.0" + objecttolerance="10.0" + borderopacity="1.0" + bordercolor="#666666" + pagecolor="#ffffff" + id="base" + inkscape:zoom="1" + inkscape:cx="16" + inkscape:cy="15.944056" + inkscape:window-x="0" + inkscape:window-y="33" + inkscape:current-layer="svg3017" /> + <defs + id="defs3019"> + <linearGradient + id="linearGradient2381"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop2383" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="stop2385" /> + </linearGradient> + <linearGradient + x1="415.73831" + y1="11.854" + x2="418.13361" + y2="18.8104" + id="XMLID_1758_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)"> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="0" + id="stop3903" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop3905" /> + <a:midPointStop + style="stop-color:#CCCCCC" + offset="0" /> + <a:midPointStop + style="stop-color:#CCCCCC" + offset="0.5" /> + <a:midPointStop + style="stop-color:#F2F2F2" + offset="1" /> + </linearGradient> + <linearGradient + x1="500.70749" + y1="-13.2441" + x2="513.46442" + y2="-2.1547" + id="XMLID_1757_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop3890" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop3892" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <clipPath + id="XMLID_1755_"> + <use + id="use3874" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_343_" /> + </clipPath> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop3877" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop3879" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop3881" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop3883" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="471.0806" + y1="201.07761" + x2="481.91711" + y2="210.4977" + id="XMLID_1754_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#6498c1;stop-opacity:1" + offset="0.005618" + id="stop3863" /> + <stop + style="stop-color:#79a9cc;stop-opacity:1" + offset="0.2332" + id="stop3865" /> + <stop + style="stop-color:#a4cde2;stop-opacity:1" + offset="0.74049997" + id="stop3867" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="1" + id="stop3869" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="5.618000e-003" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="0.4438" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="1" /> + </linearGradient> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="XMLID_1753_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop3851" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop3853" /> + <a:midPointStop + style="stop-color:#B2B2B2" + offset="0" /> + <a:midPointStop + style="stop-color:#B2B2B2" + offset="0.5" /> + <a:midPointStop + style="stop-color:#F2F2F2" + offset="1" /> + </linearGradient> + <clipPath + id="XMLID_1751_"> + <use + id="use3837" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_338_" /> + </clipPath> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop3840" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop3842" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop3844" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop3846" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="468.2915" + y1="204.7612" + x2="479.39871" + y2="214.4166" + id="XMLID_1750_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop3830" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop3832" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop3818" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop3820" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <linearGradient + x1="501.0903" + y1="-19.2544" + x2="531.85413" + y2="0.72390002" + id="XMLID_1748_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop3803" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop3805" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop3807" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop3809" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="XMLID_2275_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop9947" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop9949" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop9951" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop9953" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <clipPath + id="XMLID_2273_"> + <use + id="use9933" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_960_" /> + </clipPath> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="XMLID_2274_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop9936" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop9938" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop9940" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop9942" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <linearGradient + x1="478.21341" + y1="-131.9297" + x2="469.85818" + y2="-140.28481" + id="XMLID_2272_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop9917" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop9919" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop9921" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop9923" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <marker + refX="0" + refY="0" + orient="auto" + style="overflow:visible" + id="TriangleInM"> + <path + d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z " + transform="scale(-0.4,-0.4)" + style="fill:#5c5c4f" + id="path3197" /> + </marker> + <linearGradient + x1="200.7363" + y1="100.4028" + x2="211.99519" + y2="89.143997" + id="XMLID_3298_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#bfbfbf;stop-opacity:1" + offset="0" + id="stop20103" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop20105" /> + <a:midPointStop + offset="0" + style="stop-color:#BFBFBF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#BFBFBF" /> + <a:midPointStop + offset="1" + style="stop-color:#F2F2F2" /> + </linearGradient> + <linearGradient + x1="200.7363" + y1="100.4028" + x2="211.99519" + y2="89.143997" + id="linearGradient36592" + xlink:href="#XMLID_3298_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="181.2925" + y1="110.8481" + x2="192.6369" + y2="99.5037" + id="XMLID_3297_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="stop20096" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop20098" /> + <a:midPointStop + offset="0" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="181.2925" + y1="110.8481" + x2="192.6369" + y2="99.5037" + id="linearGradient36595" + xlink:href="#XMLID_3297_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="211.77589" + y1="105.7749" + x2="212.6619" + y2="108.2092" + id="XMLID_3296_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#0f6124;stop-opacity:1" + offset="0" + id="stop20087" /> + <stop + style="stop-color:#219630;stop-opacity:1" + offset="1" + id="stop20089" /> + <a:midPointStop + offset="0" + style="stop-color:#0F6124" /> + <a:midPointStop + offset="0.5" + style="stop-color:#0F6124" /> + <a:midPointStop + offset="1" + style="stop-color:#219630" /> + </linearGradient> + <linearGradient + x1="211.77589" + y1="105.7749" + x2="212.6619" + y2="108.2092" + id="linearGradient36677" + xlink:href="#XMLID_3296_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="208.9834" + y1="116.8296" + x2="200.0811" + y2="96.834602" + id="XMLID_3295_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop20076" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.5" + id="stop20078" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop20080" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="208.9834" + y1="116.8296" + x2="200.0811" + y2="96.834602" + id="linearGradient36604" + xlink:href="#XMLID_3295_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="195.5264" + y1="97.911102" + x2="213.5213" + y2="115.9061" + id="XMLID_3294_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="0" + id="stop20069" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop20071" /> + <a:midPointStop + offset="0" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="0.5" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="195.5264" + y1="97.911102" + x2="213.5213" + y2="115.9061" + id="linearGradient36607" + xlink:href="#XMLID_3294_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="186.1938" + y1="109.1343" + x2="206.6881" + y2="88.639999" + id="XMLID_3293_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop20056" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.16850001" + id="stop20058" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.23029999" + id="stop20060" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.2809" + id="stop20062" /> + <stop + style="stop-color:#c2c2c2;stop-opacity:1" + offset="0.5" + id="stop20064" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.1685" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.2303" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.2809" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#C2C2C2" /> + </linearGradient> + <linearGradient + x1="186.1938" + y1="109.1343" + x2="206.6881" + y2="88.639999" + id="linearGradient36610" + xlink:href="#XMLID_3293_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="184.8569" + y1="112.2676" + x2="211.94099" + y2="89.541397" + id="XMLID_3292_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop20043" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.16850001" + id="stop20045" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.23029999" + id="stop20047" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.2809" + id="stop20049" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop20051" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.1685" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.2303" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.2809" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="184.8569" + y1="112.2676" + x2="211.94099" + y2="89.541397" + id="linearGradient36613" + xlink:href="#XMLID_3292_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <marker + refX="0" + refY="0" + orient="auto" + style="overflow:visible" + id="TriangleOutM"> + <path + d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z " + transform="scale(0.4,0.4)" + style="fill:#5c5c4f;fill-rule:evenodd;stroke-width:1pt;marker-start:none" + id="path3238" /> + </marker> + <linearGradient + x1="165.3" + y1="99.5" + x2="165.3" + y2="115.9" + id="XMLID_3457_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#999;stop-opacity:1" + offset="0" + id="stop8309" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0.30000001" + id="stop8311" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="1" + id="stop8313" /> + <a:midPointstop + offset="0" + style="stop-color:#999999" /> + <a:midPointstop + offset="0.5" + style="stop-color:#999999" /> + <a:midPointstop + offset="0.3" + style="stop-color:#B2B2B2" /> + <a:midPointstop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointstop + offset="1" + style="stop-color:#B2B2B2" /> + </linearGradient> + <linearGradient + x1="165.3" + y1="99.5" + x2="165.3" + y2="115.9" + id="lg1997" + xlink:href="#XMLID_3457_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="175" + y1="99.800003" + x2="175" + y2="112.5" + id="XMLID_3456_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="0" + id="stop8300" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="0.60000002" + id="stop8302" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="1" + id="stop8304" /> + <a:midPointstop + offset="0" + style="stop-color:#737373" /> + <a:midPointstop + offset="0.5" + style="stop-color:#737373" /> + <a:midPointstop + offset="0.6" + style="stop-color:#191919" /> + <a:midPointstop + offset="0.5" + style="stop-color:#191919" /> + <a:midPointstop + offset="1" + style="stop-color:#191919" /> + </linearGradient> + <linearGradient + x1="175" + y1="99.800003" + x2="175" + y2="112.5" + id="lg2000" + xlink:href="#XMLID_3456_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="168.8" + y1="107.1" + x2="164.5" + y2="110" + id="XMLID_3455_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#666;stop-opacity:1" + offset="0" + id="stop8291" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="0.69999999" + id="stop8293" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="1" + id="stop8295" /> + <a:midPointstop + offset="0" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.5" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.7" + style="stop-color:#191919" /> + <a:midPointstop + offset="0.5" + style="stop-color:#191919" /> + <a:midPointstop + offset="1" + style="stop-color:#191919" /> + </linearGradient> + <linearGradient + x1="168.8" + y1="107.1" + x2="164.5" + y2="110" + id="lg2003" + xlink:href="#XMLID_3455_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + id="lg63694"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop63696" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="stop63698" /> + </linearGradient> + <linearGradient + x1="458" + y1="483" + x2="465.20001" + y2="271.39999" + id="lg2006" + xlink:href="#lg63694" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(6.3e-2,0,0,6.3e-2,-1.3,-9.8)" /> + <linearGradient + x1="176.3" + y1="110.1" + x2="158.7" + y2="105" + id="XMLID_3453_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#666;stop-opacity:1" + offset="0" + id="stop8271" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="0.2" + id="stop8273" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop8275" /> + <a:midPointstop + offset="0" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.5" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.2" + style="stop-color:#737373" /> + <a:midPointstop + offset="0.5" + style="stop-color:#737373" /> + <a:midPointstop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="176.3" + y1="110.1" + x2="158.7" + y2="105" + id="lg2009" + xlink:href="#XMLID_3453_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="173.60001" + y1="118.9" + x2="172.8" + y2="128.2" + id="XMLID_3449_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8232" /> + <stop + style="stop-color:#fff95e;stop-opacity:1" + offset="0.60000002" + id="stop8234" /> + <stop + style="stop-color:#ecd600;stop-opacity:1" + offset="1" + id="stop8236" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.6" + style="stop-color:#FFF95E" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFF95E" /> + <a:midPointstop + offset="1" + style="stop-color:#ECD600" /> + </linearGradient> + <linearGradient + x1="173.60001" + y1="118.9" + x2="172.8" + y2="128.2" + id="lg2016" + xlink:href="#XMLID_3449_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <radialGradient + cx="284.60001" + cy="172.60001" + r="6.5" + fx="284.60001" + fy="172.60001" + id="XMLID_3448_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8219" /> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0.30000001" + id="stop8221" /> + <stop + style="stop-color:#c96b00;stop-opacity:1" + offset="0.89999998" + id="stop8223" /> + <stop + style="stop-color:#9a5500;stop-opacity:1" + offset="1" + id="stop8225" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.3" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.9" + style="stop-color:#C96B00" /> + <a:midPointstop + offset="0.5" + style="stop-color:#C96B00" /> + <a:midPointstop + offset="1" + style="stop-color:#9A5500" /> + </radialGradient> + <radialGradient + cx="284.60001" + cy="172.60001" + r="6.5" + fx="284.60001" + fy="172.60001" + id="rg2020" + xlink:href="#XMLID_3448_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.513992,0,0,2.347576,-689.1621,-378.5717)" /> + <linearGradient + x1="158.10001" + y1="123" + x2="164.2" + y2="126.6" + id="XMLID_3447_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecd600;stop-opacity:1" + offset="0" + id="stop8204" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.30000001" + id="stop8206" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop8208" /> + <a:midPointstop + offset="0" + style="stop-color:#ECD600" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECD600" /> + <a:midPointstop + offset="0.3" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="158.10001" + y1="123" + x2="164.2" + y2="126.6" + id="lg2026" + xlink:href="#XMLID_3447_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <radialGradient + cx="280.89999" + cy="163.7" + r="10.1" + fx="280.89999" + fy="163.7" + id="XMLID_3446_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop8197" /> + <stop + style="stop-color:#fff95e;stop-opacity:1" + offset="1" + id="stop8199" /> + <a:midPointstop + offset="0" + style="stop-color:#FFFFFF" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointstop + offset="1" + style="stop-color:#FFF95E" /> + </radialGradient> + <radialGradient + cx="280.89999" + cy="163.7" + r="10.1" + fx="280.89999" + fy="163.7" + id="rg2029" + xlink:href="#XMLID_3446_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.7,0,0,1.7,-457.5,-266.8)" /> + <linearGradient + x1="156.5" + y1="122.7" + x2="180.10001" + y2="122.7" + id="XMLID_3445_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8184" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.2" + id="stop8186" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.30000001" + id="stop8188" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.40000001" + id="stop8190" /> + <stop + style="stop-color:#d68100;stop-opacity:1" + offset="1" + id="stop8192" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.2" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.3" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.4" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="1" + style="stop-color:#D68100" /> + </linearGradient> + <linearGradient + x1="156.5" + y1="122.7" + x2="180.10001" + y2="122.7" + id="lg2032" + xlink:href="#XMLID_3445_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="156.39999" + y1="115.4" + x2="180.10001" + y2="115.4" + id="XMLID_3444_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8171" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.2" + id="stop8173" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.30000001" + id="stop8175" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.40000001" + id="stop8177" /> + <stop + style="stop-color:#d68100;stop-opacity:1" + offset="1" + id="stop8179" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.2" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.3" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.4" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="1" + style="stop-color:#D68100" /> + </linearGradient> + <linearGradient + x1="156.39999" + y1="115.4" + x2="180.10001" + y2="115.4" + id="lg2035" + xlink:href="#XMLID_3444_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="379.70001" + y1="167.89999" + x2="383.89999" + y2="172.89999" + id="lg4286_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s16159" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.1" + id="s16161" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="1" + id="s16163" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.1" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#737373" + offset="1" /> + </linearGradient> + <linearGradient + x1="379.60001" + y1="167.8" + x2="383.79999" + y2="172" + id="lg6416" + xlink:href="#lg4286_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.622156,0.623859,-0.623859,2.62182,-882.9706,-673.7921)" /> + <linearGradient + x1="384.20001" + y1="169.8" + x2="384.79999" + y2="170.39999" + id="lg4285_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="0" + id="s16152" /> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="1" + id="s16154" /> + <ns:midPointStop + style="stop-color:#737373" + offset="0" /> + <ns:midPointStop + style="stop-color:#737373" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#D9D9D9" + offset="1" /> + </linearGradient> + <linearGradient + x1="384.20001" + y1="169.8" + x2="384.79999" + y2="170.39999" + id="lg6453" + xlink:href="#lg4285_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" /> + <linearGradient + x1="380.5" + y1="172.60001" + x2="382.79999" + y2="173.7" + id="lg4284_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> + <stop + style="stop-color:gray;stop-opacity:1" + offset="0" + id="s16145" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="1" + id="s16147" /> + <ns:midPointStop + style="stop-color:#808080" + offset="0" /> + <ns:midPointStop + style="stop-color:#808080" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#E5E5E5" + offset="1" /> + </linearGradient> + <linearGradient + x1="380.5" + y1="172.60001" + x2="382.79999" + y2="173.7" + id="lg6456" + xlink:href="#lg4284_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" /> + <radialGradient + cx="347.29999" + cy="244.5" + r="5.1999998" + fx="347.29999" + fy="244.5" + id="lg4282_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> + <stop + style="stop-color:#333;stop-opacity:1" + offset="0" + id="s16135" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="s16137" /> + <ns:midPointStop + style="stop-color:#333333" + offset="0" /> + <ns:midPointStop + style="stop-color:#333333" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#999999" + offset="1" /> + </radialGradient> + <linearGradient + x1="310.39999" + y1="397.70001" + x2="310.89999" + y2="399.5" + id="lg4280_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="0" + id="s16111" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.60000002" + id="s16113" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="1" + id="s16115" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.6" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="1" /> + </linearGradient> + <linearGradient + x1="310.39999" + y1="397.70001" + x2="310.89999" + y2="399.5" + id="lg6467" + xlink:href="#lg4280_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> + <linearGradient + x1="310.89999" + y1="395.79999" + x2="313.29999" + y2="403.10001" + id="lg4279_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0" + id="s16100" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.40000001" + id="s16102" /> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="0.89999998" + id="s16104" /> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="1" + id="s16106" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.4" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0.9" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="310.89999" + y1="395.79999" + x2="313.29999" + y2="403.10001" + id="lg6465" + xlink:href="#lg4279_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> + <linearGradient + x1="307.79999" + y1="395.20001" + x2="313.79999" + y2="413.60001" + id="lg4278_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0" + id="s16091" /> + <stop + style="stop-color:#fcd72f;stop-opacity:1" + offset="0.40000001" + id="s16093" /> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="1" + id="s16095" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FCD72F" + offset="0.4" /> + <ns:midPointStop + style="stop-color:#FCD72F" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="306.5" + y1="393" + x2="309" + y2="404" + id="lg6400" + xlink:href="#lg4278_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> + <linearGradient + x1="352.10001" + y1="253.60001" + x2="348.5" + y2="237.8" + id="lg4276_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> + <stop + style="stop-color:#ffff87;stop-opacity:1" + offset="0" + id="s16077" /> + <stop + style="stop-color:#ffad00;stop-opacity:1" + offset="1" + id="s16079" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFAD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="335.60001" + y1="354.79999" + x2="337.89999" + y2="354.79999" + id="lg4275_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="s16057" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.80000001" + id="s16059" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="s16061" /> + <ns:midPointStop + style="stop-color:#D9D9D9" + offset="0" /> + <ns:midPointStop + style="stop-color:#D9D9D9" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.8" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="1" /> + </linearGradient> + <linearGradient + x1="335.60001" + y1="354.79999" + x2="337.89999" + y2="354.79999" + id="lg6463" + xlink:href="#lg4275_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> + <linearGradient + x1="337.39999" + y1="353.10001" + x2="339.39999" + y2="357.10001" + id="lg4274_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s16048" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.1" + id="s16050" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s16052" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.1" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="337.39999" + y1="353.10001" + x2="339.39999" + y2="357.10001" + id="lg6461" + xlink:href="#lg4274_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> + <linearGradient + x1="334.39999" + y1="355.5" + x2="335.5" + y2="356.79999" + id="lg4273_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s16041" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s16043" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="5.6e-003" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="334.39999" + y1="355.5" + x2="335.5" + y2="356.79999" + id="lg6381" + xlink:href="#lg4273_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> + <linearGradient + x1="348.39999" + y1="247.39999" + x2="354.10001" + y2="242" + id="lg4271_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0" + id="s16025" /> + <stop + style="stop-color:#9e9e9e;stop-opacity:1" + offset="0.40000001" + id="s16027" /> + <stop + style="stop-color:black;stop-opacity:1" + offset="1" + id="s16029" /> + <ns:midPointStop + style="stop-color:#F2F2F2" + offset="0" /> + <ns:midPointStop + style="stop-color:#F2F2F2" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#000000" + offset="1" /> + </linearGradient> + <linearGradient + x1="351.29999" + y1="257.29999" + x2="346.29999" + y2="235.5" + id="lg4270_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ffff87;stop-opacity:1" + offset="0" + id="s16007" /> + <stop + style="stop-color:#ffad00;stop-opacity:1" + offset="1" + id="s16009" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFAD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="351.29999" + y1="257.29999" + x2="346.29999" + y2="235.5" + id="lg6459" + xlink:href="#lg4270_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)" /> + <linearGradient + x1="43.799999" + y1="32.5" + x2="63.299999" + y2="66.400002" + id="XMLID_2708_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop75318" /> + <stop + style="stop-color:#fffcea;stop-opacity:1" + offset="1" + id="stop75320" /> + <a:midPointStop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointStop + style="stop-color:#FFFCEA" + offset="1" /> + </linearGradient> + <linearGradient + x1="43.799999" + y1="32.5" + x2="63.299999" + y2="66.400002" + id="lg1907" + xlink:href="#XMLID_2708_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)" /> + <linearGradient + x1="52.5" + y1="40.400002" + x2="58.200001" + y2="64" + id="XMLID_2707_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ffdea0;stop-opacity:1" + offset="0" + id="stop75305" /> + <stop + style="stop-color:#ffd89e;stop-opacity:1" + offset="0.30000001" + id="stop75307" /> + <stop + style="stop-color:#ffd79e;stop-opacity:1" + offset="0.30000001" + id="stop75309" /> + <stop + style="stop-color:#dbaf6d;stop-opacity:1" + offset="0.69999999" + id="stop75311" /> + <stop + style="stop-color:#6f4c24;stop-opacity:1" + offset="1" + id="stop75313" /> + <a:midPointStop + style="stop-color:#FFDEA0" + offset="0" /> + <a:midPointStop + style="stop-color:#FFDEA0" + offset="0.6" /> + <a:midPointStop + style="stop-color:#FFD79E" + offset="0.3" /> + <a:midPointStop + style="stop-color:#FFD79E" + offset="0.5" /> + <a:midPointStop + style="stop-color:#DBAF6D" + offset="0.7" /> + <a:midPointStop + style="stop-color:#DBAF6D" + offset="0.5" /> + <a:midPointStop + style="stop-color:#6F4C24" + offset="1" /> + </linearGradient> + <linearGradient + x1="52.5" + y1="40.400002" + x2="58.200001" + y2="64" + id="lg1910" + xlink:href="#XMLID_2707_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)" /> + <linearGradient + x1="58" + y1="73.199997" + x2="44.5" + y2="19" + id="XMLID_2704_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)"> + <stop + style="stop-color:#d4a96c;stop-opacity:1" + offset="0.5" + id="stop75284" /> + <stop + style="stop-color:#dcb273;stop-opacity:1" + offset="0.60000002" + id="stop75286" /> + <stop + style="stop-color:#f0ca87;stop-opacity:1" + offset="0.80000001" + id="stop75288" /> + <stop + style="stop-color:#ffdc96;stop-opacity:1" + offset="0.69999999" + id="stop75290" /> + <stop + style="stop-color:#c18a42;stop-opacity:1" + offset="1" + id="stop75292" /> + <a:midPointStop + style="stop-color:#D4A96C" + offset="0.5" /> + <a:midPointStop + style="stop-color:#D4A96C" + offset="0.6" /> + <a:midPointStop + style="stop-color:#FFDC96" + offset="0.7" /> + <a:midPointStop + style="stop-color:#FFDC96" + offset="0.5" /> + <a:midPointStop + style="stop-color:#C18A42" + offset="1" /> + </linearGradient> + <linearGradient + x1="53.700001" + y1="32" + x2="53.700001" + y2="64.599998" + id="XMLID_2703_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e5c9b0;stop-opacity:1" + offset="0" + id="stop75268" /> + <stop + style="stop-color:#e5c9b0;stop-opacity:1" + offset="0.40000001" + id="stop75270" /> + <stop + style="stop-color:#c0aa94;stop-opacity:1" + offset="1" + id="stop75272" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0.5" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0.4" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0.5" /> + <a:midPointStop + style="stop-color:#C0AA94" + offset="1" /> + </linearGradient> + <linearGradient + x1="53.700001" + y1="32" + x2="53.700001" + y2="64.599998" + id="lg1916" + xlink:href="#XMLID_2703_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)" /> + <linearGradient + x1="224.31" + y1="19.450001" + x2="214.33" + y2="11.46" + id="XMLID_419_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#404040;stop-opacity:1" + offset="0" + id="s1903" /> + <stop + style="stop-color:#6d6d6d;stop-opacity:1" + offset="0.33000001" + id="s1905" /> + <stop + style="stop-color:#e9e9e9;stop-opacity:1" + offset="1" + id="s1907" /> + <a:midPointStop + offset="0" + style="stop-color:#404040" /> + <a:midPointStop + offset="0.5" + style="stop-color:#404040" /> + <a:midPointStop + offset="0.33" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="0.5" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="1" + style="stop-color:#E9E9E9" /> + </linearGradient> + <linearGradient + x1="221.84" + y1="32.779999" + x2="212.2" + y2="20.27" + id="lg1988" + xlink:href="#XMLID_419_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> + <linearGradient + x1="228.35001" + y1="33.279999" + x2="215.42999" + y2="33.279999" + id="lg1900" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s1902" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="s1906" /> + <a:midPointStop + style="stop-color:#575757" + offset="0" /> + <a:midPointStop + style="stop-color:#575757" + offset="0.5" /> + <a:midPointStop + style="stop-color:#6D6D6D" + offset="0.33" /> + <a:midPointStop + style="stop-color:#6D6D6D" + offset="0.5" /> + <a:midPointStop + style="stop-color:#D3D3D3" + offset="1" /> + </linearGradient> + <linearGradient + x1="234.81" + y1="33.279999" + x2="228.27" + y2="33.279999" + id="lg1908" + xlink:href="#lg1900" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> + <linearGradient + x1="228.35001" + y1="33.279999" + x2="215.42999" + y2="33.279999" + id="XMLID_416_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#575757;stop-opacity:1" + offset="0" + id="s1874" /> + <stop + style="stop-color:#6d6d6d;stop-opacity:1" + offset="0.33000001" + id="s1876" /> + <stop + style="stop-color:#d3d3d3;stop-opacity:1" + offset="1" + id="s1878" /> + <a:midPointStop + offset="0" + style="stop-color:#575757" /> + <a:midPointStop + offset="0.5" + style="stop-color:#575757" /> + <a:midPointStop + offset="0.33" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="0.5" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="1" + style="stop-color:#D3D3D3" /> + </linearGradient> + <linearGradient + x1="228.35001" + y1="33.279999" + x2="215.42999" + y2="33.279999" + id="lg1991" + xlink:href="#XMLID_416_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> + <radialGradient + cx="603.19" + cy="230.77" + r="1.67" + fx="603.19" + fy="230.77" + id="x5010_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.1,0,0,1.1,-54.33,-75.4)"> + <stop + style="stop-color:#c9ffc9;stop-opacity:1" + offset="0" + id="stop29201" /> + <stop + style="stop-color:#23a11f;stop-opacity:1" + offset="1" + id="stop29203" /> + <a:midPointStop + offset="0" + style="stop-color:#C9FFC9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#C9FFC9" /> + <a:midPointStop + offset="1" + style="stop-color:#23A11F" /> + </radialGradient> + <radialGradient + cx="603.19" + cy="230.77" + r="1.67" + fx="603.19" + fy="230.77" + id="radialGradient5711" + xlink:href="#x5010_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.23,0,0,1.23,-709.93,-245.02)" /> + <linearGradient + x1="592.31" + y1="162.60001" + x2="609.32001" + y2="145.59" + id="lg5722" + xlink:href="#x5003_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="601.48999" + y1="170.16" + x2="613.84003" + y2="170.16" + id="x5002_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop29134" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.2" + id="stop29136" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="stop29138" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.20" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="1" + style="stop-color:#999999" /> + </linearGradient> + <linearGradient + x1="601.48999" + y1="170.16" + x2="613.84003" + y2="170.16" + id="lg5725" + xlink:href="#x5002_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.23" + id="x5004_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop29157" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop29159" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.23" + id="lg5728" + xlink:href="#x5004_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="592.31" + y1="162.60001" + x2="609.32001" + y2="145.59" + id="x5003_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0" + id="stop29143" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="1" + id="stop29145" /> + <a:midPointStop + offset="0" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="1" + style="stop-color:#E5E5E5" /> + </linearGradient> + <linearGradient + x1="592.31" + y1="162.60001" + x2="609.32001" + y2="145.59" + id="lg5732" + xlink:href="#x5003_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.24001" + id="x5000_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop29124" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop29126" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.24001" + id="lg5735" + xlink:href="#x5000_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="308.54999" + y1="149.89999" + x2="299.72" + y2="148.83" + id="XMLID_2433_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d6d6d6;stop-opacity:1" + offset="0" + id="71615" /> + <stop + style="stop-color:#a5a5a5;stop-opacity:1" + offset="1" + id="71617" /> + <a:midPointStop + offset="0" + style="stop-color:#D6D6D6" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D6D6D6" /> + <a:midPointStop + offset="1" + style="stop-color:#A5A5A5" /> + </linearGradient> + <linearGradient + x1="308.54999" + y1="149.89999" + x2="299.72" + y2="148.83" + id="lg1952" + xlink:href="#XMLID_2433_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> + <radialGradient + cx="307.39999" + cy="121" + r="23.35" + fx="307.39999" + fy="121" + id="XMLID_2432_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.98,0,0,0.98,2.88,2.75)"> + <stop + style="stop-color:#d2d2d2;stop-opacity:1" + offset="0.19" + id="71592" /> + <stop + style="stop-color:#cfcfcf;stop-opacity:1" + offset="0.44999999" + id="71594" /> + <stop + style="stop-color:#c7c7c7;stop-opacity:1" + offset="0.60000002" + id="71596" /> + <stop + style="stop-color:#b9b9b9;stop-opacity:1" + offset="0.74000001" + id="71598" /> + <stop + style="stop-color:#a4a4a4;stop-opacity:1" + offset="0.86000001" + id="71600" /> + <stop + style="stop-color:#8a8a8a;stop-opacity:1" + offset="0.95999998" + id="71602" /> + <stop + style="stop-color:gray;stop-opacity:1" + offset="1" + id="71604" /> + <a:midPointStop + offset="0.19" + style="stop-color:#D2D2D2" /> + <a:midPointStop + offset="0.8" + style="stop-color:#D2D2D2" /> + <a:midPointStop + offset="1" + style="stop-color:#808080" /> + </radialGradient> + <radialGradient + cx="307.39999" + cy="121" + r="23.35" + fx="307.39999" + fy="121" + id="radialGradient2331" + xlink:href="#XMLID_2432_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-276.62,-121.54)" /> + <linearGradient + x1="294.13" + y1="127.07" + x2="294.13" + y2="142.2" + id="XMLID_2430_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b5d8ff;stop-opacity:1" + offset="0" + id="71582" /> + <stop + style="stop-color:black;stop-opacity:1" + offset="1" + id="71584" /> + <a:midPointStop + offset="0" + style="stop-color:#B5D8FF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B5D8FF" /> + <a:midPointStop + offset="1" + style="stop-color:#000000" /> + </linearGradient> + <linearGradient + x1="294.13" + y1="127.07" + x2="294.13" + y2="142.2" + id="lg2820" + xlink:href="#XMLID_2430_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> + <linearGradient + x1="279.10999" + y1="148.03" + x2="309.16" + y2="148.03" + id="XMLID_2429_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e1e1e1;stop-opacity:1" + offset="0" + id="71564" /> + <stop + style="stop-color:#e1e1e1;stop-opacity:1" + offset="0.25" + id="71566" /> + <stop + style="stop-color:#a5a5a5;stop-opacity:1" + offset="0.44" + id="71568" /> + <stop + style="stop-color:#a5a5a5;stop-opacity:1" + offset="1" + id="71570" /> + <a:midPointStop + offset="0" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.25" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.44" + style="stop-color:#A5A5A5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#A5A5A5" /> + <a:midPointStop + offset="1" + style="stop-color:#A5A5A5" /> + </linearGradient> + <linearGradient + x1="279.10999" + y1="148.03" + x2="309.16" + y2="148.03" + id="lg2818" + xlink:href="#XMLID_2429_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> + <radialGradient + cx="622.34302" + cy="14.449" + r="26.496" + fx="622.34302" + fy="14.449" + id="lg3499_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.851,0,0,0.849,69.297,51.658)"> + <stop + style="stop-color:#23468e;stop-opacity:1" + offset="0" + id="stop10972" /> + <stop + style="stop-color:#012859;stop-opacity:1" + offset="1" + id="stop10974" /> + <a:midPointStop + offset="0" + style="stop-color:#23468E" /> + <a:midPointStop + offset="0.5" + style="stop-color:#23468E" /> + <a:midPointStop + offset="1" + style="stop-color:#012859" /> + </radialGradient> + <radialGradient + cx="622.34302" + cy="14.449" + r="26.496" + fx="622.34302" + fy="14.449" + id="rg5791" + xlink:href="#lg3499_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.858,0,0,0.857,-511.7,9.02)" /> + <linearGradient + x1="616.112" + y1="76.247002" + x2="588.14099" + y2="60.742001" + id="lg3497_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#01326e;stop-opacity:1" + offset="0" + id="stop10962" /> + <stop + style="stop-color:#012859;stop-opacity:1" + offset="1" + id="stop10964" /> + <a:midPointStop + offset="0" + style="stop-color:#01326E" /> + <a:midPointStop + offset="0.5" + style="stop-color:#01326E" /> + <a:midPointStop + offset="1" + style="stop-color:#012859" /> + </linearGradient> + <linearGradient + x1="617.698" + y1="82.445999" + x2="585.95203" + y2="54.848999" + id="lg3496_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="stop10950" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop10952" /> + <a:midPointStop + offset="0" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="617.698" + y1="82.445999" + x2="585.95203" + y2="54.848999" + id="lg5794" + xlink:href="#lg3496_" + gradientUnits="userSpaceOnUse" /> + <linearGradient + x1="601.39001" + y1="55.341" + x2="588.29199" + y2="71.515999" + id="lg3495_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop10941" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.52200001" + id="stop10943" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop10945" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.522" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="601.39001" + y1="55.341" + x2="588.29199" + y2="71.515999" + id="lg5771" + xlink:href="#lg3495_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.009,0,0,1.009,-581.615,-43.098)" /> + <linearGradient + x1="611.34601" + y1="55.279999" + x2="590.39001" + y2="81.157997" + id="lg3494_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop10932" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.52200001" + id="stop10934" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop10936" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.522" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="611.34601" + y1="55.279999" + x2="590.39001" + y2="81.157997" + id="lg5774" + xlink:href="#lg3494_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.009,0,0,1.009,-581.616,-43.098)" /> + <linearGradient + x1="798.72998" + y1="69.839996" + x2="799.04999" + y2="70.709999" + id="g3302_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#005e00;stop-opacity:1" + offset="0" + id="s6504" /> + <stop + style="stop-color:#23a11f;stop-opacity:1" + offset="1" + id="s6506" /> + <a:midPointstop + style="stop-color:#005E00" + offset="0" /> + <a:midPointstop + style="stop-color:#005E00" + offset="0.5" /> + <a:midPointstop + style="stop-color:#23A11F" + offset="1" /> + </linearGradient> + <linearGradient + x1="798.72998" + y1="69.839996" + x2="799.04999" + y2="70.709999" + id="lg5851" + xlink:href="#g3302_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> + <linearGradient + x1="779.19" + y1="122.73" + x2="811.69" + y2="149.74001" + id="g3301_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,129.19)"> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0" + id="s6483" /> + <stop + style="stop-color:#eee;stop-opacity:1" + offset="0.17" + id="s6485" /> + <stop + style="stop-color:#e3e3e3;stop-opacity:1" + offset="0.34" + id="s6487" /> + <stop + style="stop-color:#cfcfcf;stop-opacity:1" + offset="0.50999999" + id="s6489" /> + <stop + style="stop-color:#b4b4b4;stop-opacity:1" + offset="0.67000002" + id="s6491" /> + <stop + style="stop-color:#919191;stop-opacity:1" + offset="0.83999997" + id="s6493" /> + <stop + style="stop-color:#666;stop-opacity:1" + offset="1" + id="s6495" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.71" /> + <a:midPointstop + style="stop-color:#666666" + offset="1" /> + </linearGradient> + <linearGradient + x1="779.19" + y1="122.73" + x2="811.69" + y2="149.74001" + id="lg5855" + xlink:href="#g3301_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,103.123)" /> + <clipPath + id="g3299_"> + <use + id="use6469" + x="0" + y="0" + width="1005.92" + height="376.97" + xlink:href="#g101_" /> + </clipPath> + <radialGradient + cx="1189.9301" + cy="100.05" + r="40.400002" + fx="1189.9301" + fy="100.05" + id="g3300_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.34,-8.46e-2,0,0.34,394.16,137.13)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s6472" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="s6474" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointstop + style="stop-color:#000000" + offset="1" /> + </radialGradient> + <radialGradient + cx="1199.74" + cy="97.150002" + r="40.400002" + fx="1199.74" + fy="97.150002" + id="rg5860" + xlink:href="#g3300_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.409,-0.107,0,0.429,-451.489,113.149)" /> + <linearGradient + x1="796.38" + y1="67.580002" + x2="781.28003" + y2="58.549999" + id="g3298_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#4c8bca;stop-opacity:1" + offset="0" + id="s6462" /> + <stop + style="stop-color:#b7e9ff;stop-opacity:1" + offset="1" + id="s6464" /> + <a:midPointstop + style="stop-color:#4C8BCA" + offset="0" /> + <a:midPointstop + style="stop-color:#4C8BCA" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B7E9FF" + offset="1" /> + </linearGradient> + <linearGradient + x1="800.97998" + y1="140.72" + x2="777.71997" + y2="121.76" + id="g3297_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,129.19)"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="s6448" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s6450" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0.5" /> + <a:midPointstop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="800.97998" + y1="140.72" + x2="777.71997" + y2="121.76" + id="lg5890" + xlink:href="#g3297_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,129.19)" /> + <linearGradient + x1="790.03998" + y1="-16.33" + x2="779.84003" + y2="-3.73" + id="g3296_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(0,70.17)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="s6439" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.51999998" + id="s6441" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s6443" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0.5" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.52" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.5" /> + <a:midPointstop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="790.03998" + y1="-16.33" + x2="779.84003" + y2="-3.73" + id="lg5866" + xlink:href="#g3296_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,28.6)" /> + <linearGradient + x1="785.84003" + y1="72.989998" + x2="785.26001" + y2="76.279999" + id="g3293_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s6412" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="1" + id="s6414" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointstop + style="stop-color:#737373" + offset="1" /> + </linearGradient> + <linearGradient + x1="785.84003" + y1="72.989998" + x2="785.26001" + y2="76.279999" + id="lg5871" + xlink:href="#g3293_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> + <linearGradient + x1="789.37" + y1="69.879997" + x2="791.03998" + y2="77.120003" + id="g3292_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#999;stop-opacity:1" + offset="0" + id="s6403" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.28" + id="s6405" /> + <stop + style="stop-color:#666;stop-opacity:1" + offset="1" + id="s6407" /> + <a:midPointstop + style="stop-color:#999999" + offset="0" /> + <a:midPointstop + style="stop-color:#999999" + offset="0.5" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.28" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.5" /> + <a:midPointstop + style="stop-color:#666666" + offset="1" /> + </linearGradient> + <linearGradient + x1="789.37" + y1="69.879997" + x2="791.03998" + y2="77.120003" + id="lg5874" + xlink:href="#g3292_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> + <linearGradient + x1="786.65997" + y1="136.12" + x2="786.71002" + y2="134.33" + id="g3290_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,137.29)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="s6380" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="1" + id="s6382" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="1" /> + </linearGradient> + <linearGradient + x1="786.65997" + y1="136.12" + x2="786.71002" + y2="134.33" + id="lg5878" + xlink:href="#g3290_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,113.351)" /> + <radialGradient + cx="1458.77" + cy="-5.0999999" + r="35.130001" + fx="1458.77" + fy="-5.0999999" + id="g3289_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s6371" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="s6373" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointstop + style="stop-color:#999999" + offset="1" /> + </radialGradient> + <radialGradient + cx="1458.77" + cy="-5.0999999" + r="35.130001" + fx="1458.77" + fy="-5.0999999" + id="rg5881" + xlink:href="#g3289_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" /> + <radialGradient + cx="1612.98" + cy="-4.4699998" + r="36.580002" + fx="1612.98" + fy="-4.4699998" + id="g3288_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.34,0,0,0.36,238.56,86.87)"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="s6362" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0.63999999" + id="s6364" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="1" + id="s6366" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.64" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.5" /> + <a:midPointstop + style="stop-color:#737373" + offset="1" /> + </radialGradient> + <radialGradient + cx="1612.98" + cy="-4.4699998" + r="36.580002" + fx="1612.98" + fy="-4.4699998" + id="rg5884" + xlink:href="#g3288_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.408,0,0,0.448,-638.943,49.495)" /> + <radialGradient + cx="1470.5" + cy="-10.21" + r="33.290001" + fx="1470.5" + fy="-10.21" + id="g3287_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="s6347" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0.38999999" + id="s6349" /> + <stop + style="stop-color:#b1b1b1;stop-opacity:1" + offset="0.75" + id="s6351" /> + <stop + style="stop-color:#aaa;stop-opacity:1" + offset="0.88" + id="s6353" /> + <stop + style="stop-color:#9e9e9e;stop-opacity:1" + offset="0.97000003" + id="s6355" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="s6357" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.39" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.87" /> + <a:midPointstop + style="stop-color:#999999" + offset="1" /> + </radialGradient> + <radialGradient + cx="1470.5" + cy="-10.21" + r="33.290001" + fx="1470.5" + fy="-10.21" + id="rg5887" + xlink:href="#g3287_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" /> + <pattern + patternTransform="matrix(0.592927,0,0,0.592927,78,462)" + id="cream-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-365.3146,-513.505)" + id="g3047"> + id="path2858" /> + <path + inkscape:label="#path2854" + sodipodi:nodetypes="czzzz" + style="fill:#e3dcc0" + id="path3060" + d="M 390.31462,529.50504 C 390.31462,534.47304 386.28262,538.50504 381.31462,538.50504 C 376.34662,538.50504 372.31462,534.47304 372.31462,529.50504 C 372.31462,524.53704 376.34662,520.50504 381.31462,520.50504 C 386.28262,520.50504 390.31462,524.53704 390.31462,529.50504 z " /> +</g> + </pattern> + <pattern + patternTransform="matrix(0.733751,0,0,0.733751,67,367)" + id="dark-cream-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-408.0946,-513.505)" + id="dark-cream-spot" + inkscape:label="#g3043"> + <path + sodipodi:nodetypes="czzzz" + style="fill:#c8c5ac" + d="M 433.09458,529.50504 C 433.09458,534.47304 429.06258,538.50504 424.09458,538.50504 C 419.12658,538.50504 415.09458,534.47304 415.09458,529.50504 C 415.09458,524.53704 419.12658,520.50504 424.09458,520.50504 C 429.06258,520.50504 433.09458,524.53704 433.09458,529.50504 z " + id="path2953" /> + </g> + </pattern> + <pattern + patternTransform="matrix(0.375,0,0,0.375,379,400)" + id="white-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-484.3997,-513.505)" + id="white-spot" + inkscape:label="#g3035"> + <path + style="opacity:0.25;fill:white" + id="path3033" + d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z " + sodipodi:nodetypes="czzzz" /> + </g> + </pattern> + <pattern + patternTransform="matrix(0.455007,0,0,0.455007,-5e-5,1.9e-5)" + id="black-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-448.3997,-513.505)" + id="black-spot" + inkscape:label="#g3039"> + <path + sodipodi:nodetypes="czzzz" + d="M 473.39967,529.50504 C 473.39967,534.47304 469.36767,538.50504 464.39967,538.50504 C 459.43167,538.50504 455.39967,534.47304 455.39967,529.50504 C 455.39967,524.53704 459.43167,520.50504 464.39967,520.50504 C 469.36767,520.50504 473.39967,524.53704 473.39967,529.50504 z " + id="path2961" + style="opacity:0.25;fill:black" /> + </g> + </pattern> + <linearGradient + x1="501.0903" + y1="-19.2544" + x2="531.85413" + y2="0.72390002" + id="linearGradient17334" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop17336" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop17338" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop17340" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop17342" /> + <a:midPointStop + offset="0" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.5112" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.6461" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="1" + style="stop-color:#16336E" /> + </linearGradient> + <linearGradient + x1="415.73831" + y1="11.854" + x2="418.13361" + y2="18.8104" + id="linearGradient17426" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)"> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="0" + id="stop17428" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop17430" /> + <a:midPointStop + offset="0" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="0.5" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="1" + style="stop-color:#F2F2F2" /> + </linearGradient> + <linearGradient + x1="478.21341" + y1="-131.9297" + x2="469.85818" + y2="-140.28481" + id="linearGradient17434" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop17436" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop17438" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop17440" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop17442" /> + <a:midPointStop + offset="0" + style="stop-color:#F3403F" /> + <a:midPointStop + offset="0.4213" + style="stop-color:#F3403F" /> + <a:midPointStop + offset="1" + style="stop-color:#A6100C" /> + </linearGradient> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17709" + xlink:href="#XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" /> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17711" + xlink:href="#XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="linearGradient17713" + xlink:href="#XMLID_1753_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17715" + xlink:href="#XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="500.70749" + y1="-13.2441" + x2="513.46442" + y2="-2.1547" + id="linearGradient17717" + xlink:href="#XMLID_1757_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="linearGradient17721" + xlink:href="#XMLID_2274_" + gradientUnits="userSpaceOnUse" /> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="linearGradient17723" + xlink:href="#XMLID_2275_" + gradientUnits="userSpaceOnUse" /> + <linearGradient + x1="500.70749" + y1="-13.2441" + x2="513.46442" + y2="-2.1547" + id="linearGradient17416" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop17418" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop17420" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <defs + id="defs9929"> + <path + d="M 489.21,209.35 L 485.35,203.63 C 483.63,204.25 473.47,208.93 471.5,210.18 C 470.57,210.77 470.17,211.16 469.72,212.48 C 470.93,212.31 471.72,212.49 473.42,213.04 C 473.26,214.77 473.24,215.74 473.57,218.2 C 474.01,216.88 474.41,216.49 475.34,215.9 C 477.33,214.65 487.49,209.97 489.21,209.35 z " + id="XMLID_960_" /> + </defs> + <clipPath + id="clipPath17448"> + <use + id="use17450" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_960_" /> + </clipPath> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="linearGradient17452" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop17454" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop17456" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop17458" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop17460" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="linearGradient17463" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop17465" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop17467" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop17469" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop17471" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="linearGradient17807" + xlink:href="#XMLID_2275_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-177.1654,35.43307)" /> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="linearGradient17810" + xlink:href="#XMLID_2274_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-177.1654,35.43307)" /> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17812" + xlink:href="#XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" /> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17814" + xlink:href="#XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="linearGradient17816" + xlink:href="#XMLID_1753_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17818" + xlink:href="#XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17347" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop17349" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop17351" /> + <a:midPointStop + offset="0" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="1" + style="stop-color:#96BAD6" /> + </linearGradient> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="linearGradient17379" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop17381" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop17383" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="1" + style="stop-color:#F2F2F2" /> + </linearGradient> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17862" + xlink:href="#XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,-166.1427,-0.18283)" /> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17864" + xlink:href="#XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <defs + id="defs3859"> + <polygon + points="465.54,213.52 481.94,217.46 482.74,216.71 487.46,198.05 471.08,194.07 470.26,194.83 465.54,213.52 " + id="XMLID_343_" /> + </defs> + <linearGradient + x1="471.0806" + y1="201.07761" + x2="481.91711" + y2="210.4977" + id="linearGradient17389" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#6498c1;stop-opacity:1" + offset="0.005618" + id="stop17391" /> + <stop + style="stop-color:#79a9cc;stop-opacity:1" + offset="0.2332" + id="stop17393" /> + <stop + style="stop-color:#a4cde2;stop-opacity:1" + offset="0.74049997" + id="stop17395" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="1" + id="stop17397" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="5.618000e-003" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="0.4438" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="1" /> + </linearGradient> + <clipPath + id="clipPath17400"> + <use + id="use17402" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_343_" /> + </clipPath> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17404" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop17406" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop17408" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop17410" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop17412" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17882" + xlink:href="#XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <defs + id="defs3826"> + <polygon + points="463.52,216.14 480.56,220.24 481.36,219.5 483.03,202.04 469.05,196.69 468.24,197.45 463.52,216.14 " + id="XMLID_338_" /> + </defs> + <linearGradient + x1="468.2915" + y1="204.7612" + x2="479.39871" + y2="214.4166" + id="linearGradient17357" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop17359" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop17361" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <clipPath + id="clipPath17364"> + <use + id="use17366" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_338_" /> + </clipPath> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17368" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop17370" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop17372" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop17374" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop17376" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" + id="linearGradient2387" + xlink:href="#linearGradient2381" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> + <linearGradient + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" + id="linearGradient5105" + xlink:href="#linearGradient2381" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> + <linearGradient + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" + id="linearGradient5145" + xlink:href="#linearGradient2381" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient2381" + id="linearGradient2371" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" /> + </defs> + <g + transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" + id="g5089"> + <path + d="M 8.4382985,-6.28125 C 7.8309069,-6.28125 4.125,-0.33238729 4.125,1.96875 L 4.125,28.6875 C 4.125,29.533884 4.7068159,29.8125 5.28125,29.8125 L 30.84375,29.8125 C 31.476092,29.8125 31.968751,29.319842 31.96875,28.6875 L 31.96875,23.46875 L 32.25,23.46875 C 32.74684,23.46875 33.156249,23.059339 33.15625,22.5625 L 33.15625,-5.375 C 33.15625,-5.8718398 32.74684,-6.28125 32.25,-6.28125 L 8.4382985,-6.28125 z " + transform="translate(282.8327,227.1903)" + style="fill:#5c5c4f;stroke:black;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none" + id="path5091" /> + <rect + width="27.85074" + height="29.369793" + rx="1.1414107" + ry="1.1414107" + x="286.96509" + y="227.63805" + style="fill:#032c87" + id="rect5093" /> + <path + d="M 288.43262,225.43675 L 313.67442,225.43675 L 313.67442,254.80655 L 287.29827,254.83069 L 288.43262,225.43675 z " + style="fill:white" + id="rect5095" /> + <path + d="M 302.44536,251.73726 C 303.83227,259.59643 301.75225,263.02091 301.75225,263.02091 C 303.99609,261.41329 305.71651,259.54397 306.65747,257.28491 C 307.62455,259.47755 308.49041,261.71357 310.9319,263.27432 C 310.9319,263.27432 309.33686,256.07392 309.22047,251.73726 L 302.44536,251.73726 z " + style="fill:#a70000;fill-opacity:1;stroke-width:2" + id="path5097" /> + <rect + width="25.241802" + height="29.736675" + rx="0.89682275" + ry="0.89682275" + x="290.73544" + y="220.92249" + style="fill:#809cc9" + id="rect5099" /> + <path + d="M 576.47347,725.93939 L 582.84431,726.35441 L 583.25121,755.8725 C 581.35919,754.55465 576.39694,752.1117 574.98889,754.19149 L 574.98889,727.42397 C 574.98889,726.60151 575.65101,725.93939 576.47347,725.93939 z " + transform="matrix(0.499065,-0.866565,0,1,0,0)" + style="fill:#4573b3;fill-opacity:1" + id="rect5101" /> + <path + d="M 293.2599,221.89363 L 313.99908,221.89363 C 314.45009,221.89363 314.81318,222.25673 314.81318,222.70774 C 315.02865,229.0361 295.44494,244.47124 292.44579,240.30491 L 292.44579,222.70774 C 292.44579,222.25673 292.80889,221.89363 293.2599,221.89363 z " + style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1" + id="path5103" /> + </g> +</svg> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/master.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/master.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/master.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -54,12 +54,12 @@ <releaseinfo> Version: 2.1.1.GA </releaseinfo> -<abstract> + </bookinfo> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/modules.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/modules.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/modules.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -1,24 +1,21 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="modules"> <title>Deploying Modules</title> - + <para>In this chapter it will be described how to deploy modules onto the server.</para> - <para> First of all it is necessary to say that deploying to a server is mostly painless. There - are several ways to do it provided by WTP, and some additional methods provided by JBoss - Tools. These methods are described further in this chapter.</para> - + <para> + First of all it is necessary to say that deploying to a server is mostly painless. There are several ways to do it provided by WTP and some additional methods provided by JBoss Tools. These methods are described further in this chapter. + </para> + <section> <title>Deploying on the Package Explorer</title> - - <para>On the package explorer it is possible to publish either a project to a server or just - a single file. Let's look at how to do this.</para> + + <para>On the package explorer it is possible to publish either a project to a server or just a single file. Let's look at how to do this.</para> <section id="run_on_server_wizard"> <title>Deploying with Run On Server Wizard</title> - <para> The first WTP method is to right-click on a project, such as a Dynamic Web - project, EJB project, or EAR project and then select <emphasis> - <property>Run As > Run on Server</property> - </emphasis>. The resulting dialog allows you to select which supporting server the - project can be published to.</para> + <para> + The first WTP method is to right-click on a project, such as a Dynamic Web project, EJB project, or EAR project and then select <menuchoice><guimenuitem>Run As</guimenuitem><guimenuitem>Run on Server</guimenuitem></menuchoice>. The resulting dialog allows you to select which supporting server the project can be published to. + </para> <figure> <title>Define a New Server</title> <mediaobject> @@ -27,10 +24,7 @@ </imageobject> </mediaobject> </figure> - <para>Click <emphasis> - <property>Next</property> - </emphasis> button to see add or remove projects page where you can choose projects - to configure them on server.</para> + <para>Click the <guibutton>Next</guibutton> button to see add or remove projects page where you can choose projects to configure them on server.</para> <figure id="add_rem_proj"> <title>Add or Remove Projects</title> <mediaobject> @@ -39,42 +33,24 @@ </imageobject> </mediaobject> </figure> - <para>This page of the wizard also allows to undeploy modules from the server. For that - choose proper module(s) from the right and click <emphasis> - <property> < Remove</property> - </emphasis>. The modules will be completely undeployed after restarting your server - or republishing.</para> - <para>Generally, for the JBoss AS Server Adapters, publishing using this method will - force a default, best-guess, packaging configuration for your project. This - best-guess does not publish incrementally, but instead repackages your entire - project into a <emphasis> - <property>.war</property> - </emphasis>, <emphasis> - <property>.jar</property> - </emphasis>, or <emphasis> - <property>.ear</property> - </emphasis> as appropriate, and then copies that file into the proper deploy - directory. For quicker smarter deployment, you will need to create archives using - the <link linkend="Project_archivesView">Project Archives view</link> and customize - packaging yourself.</para> + <para> + This page of the wizard also allows to undeploy modules from the server. For that choose proper module(s) from the right and click the <guibutton> < Remove</guibutton>. The modules will be completely undeployed after restarting your server or republishing. + </para> + <para> + Generally, for the JBoss AS Server Adapters, publishing using this method will force a default, best-guess, packaging configuration for your project. This best-guess does not publish incrementally, but instead repackages your entire project into a <filename>.war</filename>, <filename>.jar</filename>, or <filename>.ear</filename> as appropriate and then copies that file into the proper deploy directory. For quicker smarter deployment, you will need to create archives using the Project Archives view (see <xref linkend="Project_archivesView"/>) and customize packaging yourself. + </para> - + </section> - + <section id="single_file_deployment"> <?dbhtml filename="DeployToServer.html"?> <title>Deploying single files</title> - - <para>Sometimes it becomes necessary to deploy one or more files to a server. For - that in order not to do a full republish in the context menu of files a <emphasis><property>Deploy To Server</property></emphasis> - option is provided that allows a single file deployment. To deploy these non-WTP files/projects - right click on the file (<emphasis> - <property>-ds.xml</property></emphasis>, <emphasis> - <property>.ear</property></emphasis>, <emphasis> - <property>.jar</property></emphasis> etc.) and select <emphasis> - <property>Deploy To Server</property> - </emphasis> and it will be automatically deployed.</para> + + <para> + Sometimes it becomes necessary to deploy one or more files to a server. For that in order not to do a full republish in the context menu of files a <guimenuitem>Deploy To Server</guimenuitem> option is provided that allows a single file deployment. To deploy these non-WTP files/projects right click on the file (<filename>-ds.xml</filename>, <filename>.ear</filename>, <filename>.jar</filename> etc.) and select <guimenuitem>Deploy To Server</guimenuitem> and it will be automatically deployed. + </para> <figure> <title>Deploy to Sever</title> <mediaobject> @@ -83,8 +59,7 @@ </imageobject> </mediaobject> </figure> - <para>The deployed files are listed side-by-side with other modules that are deployed to - the server.</para> + <para>The deployed files are listed side-by-side with other modules that are deployed to the server.</para> <figure> <title>Deployed files on the Server</title> @@ -94,21 +69,20 @@ </imageobject> </mediaobject> </figure> - + </section> - + </section> <section> <title>Deploying with Servers View</title> - <para>As it has been already mentioned <property>Servers</property> view contains two - parts: the top part that displays all defined servers and the bottom part which provides - categories with additional information. Thus, in this section we suggest two more ways - to deploy resources onto the server.</para> + <para> + As it has been already mentioned <guilabel>Servers</guilabel> view contains two parts: the top part that displays all defined servers and the bottom part which provides categories with additional information. Thus, in this section we suggest two more ways to deploy resources onto the server. + </para> <section> <title>Top part of Servers view</title> - <para>In the top part of the <property>Servers</property> view you should right click on a server and select the <emphasis> - <property>Add and Remove</property> - </emphasis> menu item.</para> + <para> + In the top part of the <guilabel>Servers</guilabel> view you should right click on a server and select the <guimenuitem>Add and Remove</guimenuitem> menu item. + </para> <figure> <title>Add and Remove Projects</title> <mediaobject> @@ -117,28 +91,17 @@ </imageobject> </mediaobject> </figure> - - <para>This will bring up a <link linkend="add_rem_proj">familiar dialog</link> allowing - you to either publish projects or modules to a server, or remove them from the - server. If the selected module is a project like a Dynamic Web project, EJB project, - or EAR project, it will be published as through <emphasis> - <property>Run on Server</property> - </emphasis> wizard, with a best-guess full package. If, however, the selected - element is an archive from the <link linkend="Project_archivesView">Project Archives - view</link>, it will be published according to the rules of that module - type.</para> + + <para> + This will bring up a dialog (see <xref linkend="add_rem_proj"/>) that allows you to either publish projects or modules to a server, or remove them from the server. If the selected module is a project like a Dynamic Web project, EJB project, or EAR project, it will be published as through <guilabel>Run on Server</guilabel> wizard, with a best-guess full package. If, however, the selected element is an archive from the Project Archives view (see <xref linkend="Project_archivesView"/>), it will be published according to the rules of that module type. + </para> </section> - + <section> <title>Bottom part of Servers view</title> - <para>In the bottom part of <emphasis> - <property>Servers</property> view - </emphasis> there is a category called <emphasis> - <property>Modules</property> - </emphasis> which should display all currently-published modules on the server. - Right-clicking on the desired module and selecting <emphasis> - <property>Full Publish</property> - </emphasis> will force a full rebuild of the entire module.</para> + <para> + In the bottom part of <guilabel>Servers</guilabel> view there is a category called <guilabel>Modules</guilabel> which should display all currently-published modules on the server. Right-clicking on the desired module and selecting <guimenuitem>Full Publish</guimenuitem> will force a full rebuild of the entire module. + </para> <figure> <title>Full Publish</title> <mediaobject> @@ -147,19 +110,17 @@ </imageobject> </mediaobject> </figure> - - <para>Here, <emphasis> - <property>Incremental Publish</property> - </emphasis> is meant to enable publishing of only those parts where changes have - been made.</para> + + <para> + Here, <guilabel>Incremental Publish</guilabel> is meant to enable publishing of only those parts where changes have been made. + </para> </section> </section> <section> <title>Deploying with Project Archives View</title> - <para>In the <property>Project Archives View</property> you can right-click on any declared - archive and select the <emphasis> - <property>Publish To Server</property> - </emphasis> element. For more on this subject, see <link linkend="PublishToServer">Publishing to Server</link> in the Project Archives View section.</para> + <para> + In the <guilabel>Project Archives View</guilabel> you can right-click on any declared archive and select the <guilabel>Publish To Server</guilabel> element. For more on this subject, see <xref linkend="PublishToServer"/> in the Project Archives View section. + </para> <figure> <title>Publish to Server</title> <mediaobject> @@ -168,16 +129,9 @@ </imageobject> </mediaobject> </figure> - <para> The only way to ensure an <emphasis> - <property>Incremental Build</property> - </emphasis>, such as changes to one <emphasis> - <property>.jsp</property>, </emphasis> - <emphasis> - <property>.html</property>, </emphasis> or <emphasis> - <property>.class</property> - </emphasis> file, is to enable the builder for that project. This is done by either - changing the global preferences for the <property>Archives View</property>, or by - enabling project-specific preferences and ensuring the builder is on.</para> + <para> + The only way to ensure an <guilabel>Incremental Build</guilabel>, such as changes to one <filename>.jsp</filename>, <filename>.html</filename>, or <filename>.class</filename> file, is to enable the builder for that project. This is done by either changing the global preferences for the <guilabel>Archives View</guilabel>, or by enabling project-specific preferences and ensuring the builder is on. + </para> <para>You can also use the "Finger touch" button for a quick restart of the project without restarting the server:</para> <figure> @@ -187,11 +141,12 @@ <imagedata fileref="images/modules/modules_8_finger_touch.png"/> </imageobject> </mediaobject> - </figure> - <para>The "Finger" touches descriptors dependent on project (i.e. web.xml for WAR, application.xml for EAR, jboss-esb.xml in ESB projects).</para> + </figure> - - <para>The last chapter covers a variety of methods on how you can deploy needed modules onto a - server.</para> + <para> + The "Finger" touches descriptors dependent on project (i.e. <filename>web.xml</filename> for WAR, <filename>application.xml</filename> for EAR, <filename>jboss-esb.xml</filename> in ESB projects). + </para> + + <para>The last chapter covers a variety of methods on how you can deploy needed modules onto a server.</para> </section> </chapter> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/perspective.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/perspective.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/perspective.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -1,519 +1,466 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="perspective" xreflabel="perspective" role="updated"> - <?dbhtml filename="perspective.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Developer Studio</keyword> - <keyword>Eclipse</keyword> - <keyword>Deploy</keyword> - <keyword>Deployment</keyword> - <keyword>JBoss</keyword> - </keywordset> - </chapterinfo> + <?dbhtml filename="perspective.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>Deploy</keyword> + <keyword>Deployment</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> - <title>JBoss AS Perspective</title> + <title>JBoss AS Perspective</title> - <para>This chapter tells how to manage installed <property>JBoss Server</property> via - <property>JBoss AS perspective</property>.</para> + <para>This chapter describes how to manage installed <productname>JBoss Servers</productname> via the <guilabel>JBoss AS</guilabel> perspective.</para> - <para>The <property>JBoss AS perspective</property> is similar to the <property>Java - perspective</property>, but it contains a few additional views. Two of the additional - views are standard views, specifically the <property>Console view</property> and the - <property>Properties view</property>. The other two views that are added are the - <property>Project archives view</property> and the <property>Servers - </property> view.</para> + <para> + The <guilabel>JBoss AS</guilabel> perspective is similar to the <guilabel>Java</guilabel> perspective, but it contains a few additional views. The <guilabel>Console view</guilabel> and the <guilabel>Properties view</guilabel> are standard views. The other two views that are added are the <guilabel>Project archives</guilabel> view and the <guilabel>Servers</guilabel> view. + </para> - <section id="JBossServerView" role="updated"> - <?dbhtml filename="JBossServerView.html"?> - <title>The Servers view</title> + <section id="JBossServerView" role="updated"> + <?dbhtml filename="JBossServerView.html"?> + <title>The Servers view</title> - <para>The <property>Servers</property> view is built on Common Navigator Framework - allowing extensions and is using label decorators what makes the UI enough compact - without loosing the vital information.</para> + <para> + The <guilabel>Servers</guilabel> view is built on the Common Navigator Framework allowing extensions and is using label decorators that make the UI compact enough without loosing the vital information. + </para> - <para>Let's have a look at the <property>Servers</property> view and inspect - in detail all parts it consists of. </para> - <figure> - <title>The Servers view</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_1.png"/> - </imageobject> - </mediaobject> - </figure> + <para>Let's have a detailed look at the <guilabel>Servers</guilabel> view and its constituent components.</para> + <figure> + <title>The Servers view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_1.png"/> + </imageobject> + </mediaobject> + </figure> - <section id="jbossserver_view_toolbar"> - <title>Servers view Toolbar</title> - <para>In the right top corner of the <property>Servers</property> view there is a - special toolbar which provides a quick access to starting a server (in the debug - mode, run mode, or profile mode), restarting a server, stopping a server and a - possibility to publish to a server.</para> + <section id="jbossserver_view_toolbar"> + <title>Servers view Toolbar</title> + <para> + In the right top corner of the <guilabel>Servers</guilabel> view there is a special toolbar which provides a quick access for starting a server (in the debug mode, run mode, or profile mode), restarting a server, stopping a server and a publishing to a server. + </para> - <figure> - <title>The Servers view Toolbar</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_2.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>The Servers view Toolbar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_2.png"/> + </imageobject> + </mediaobject> + </figure> - <para>In order to debug your applications or EJB's that are deployed to the server, you - must start the server in debug mode. By starting the server in debug mode, eclipse - will allow you to set breakpoints on code in your workspace and step through the - code.</para> + <para> + In order to debug your applications or EJB's that are deployed to the server, the server must be started in debug mode. By starting the server in debug mode, Eclipse will allow you to set breakpoints on code in your workspace and step through the code. + </para> - <para><emphasis> - <property>Start the server in profiling mode</property> - </emphasis> button allows to enable profiling actions for your application. For more - details on how to start using TPTP profiling with <property>JBoss Tools</property> - refer to <link linkend="tptp_support">TPTP Support</link> chapter.</para> + <para> + The <guibutton>Start the server in profiling mode</guibutton> button allows you to enable profiling actions for your application. For more details on how to start using TPTP profiling with <property>JBoss Tools</property> see <xref linkend="tptp_support"/>. + </para> - <para><emphasis> - <property>Publish to the server</property> - </emphasis> button will republish any modules where it has determined the workspace - is out of sync with the server. It will attempt to do an incremental publish if it - turns out that the module in question is capable of doing one.</para> + <para> + The <guibutton>Publish to the server</guibutton> button will republish any modules where it has determined that the workspace is out of synchronization with the server. It will attempt to do an incremental publish if the module in question is capable of doing one. + </para> - </section> + </section> - <section id="jbossserver_view_structure"> - <title>Servers view Structure</title> - <para>The <property>Servers</property> view displays all declared servers as well - as their current states (that is whether they are started or stopped) and statuses - in the square brackets next to a server name.</para> + <section id="jbossserver_view_structure"> + <title>Servers view Structure</title> + <para> + The <guilabel>Servers</guilabel> view displays all defined servers as well as their current status (that is whether they are started or stopped) in square brackets next to the server name. + </para> - <figure> - <title>The Servers view</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_1.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>The Servers view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_1.png"/> + </imageobject> + </mediaobject> + </figure> - <para>The following table lists possible server statuses.</para> + <para>The following table lists possible server statuses.</para> - <table> - <title>Server Publish Status</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> + <table> + <title>Server Publish Status</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> - <thead> - <row> - <entry align="center">Status</entry> + <thead> + <row> + <entry align="center">Status</entry> - <entry align="center">Description</entry> - </row> - </thead> + <entry align="center">Description</entry> + </row> + </thead> - <tbody> - <row> - <entry align="center"> - <para>Republish</para> - </entry> + <tbody> + <row> + <entry align="center"> + <para>Republish</para> + </entry> - <entry align="center"> - <para>The status which allows you to see if changes are - awaiting</para> - </entry> - </row> - <row> - <entry align="center"> - <para>Publishing...</para> - </entry> + <entry align="center"> + <para>The status which allows you to see if changes are awaiting</para> + </entry> + </row> + <row> + <entry align="center"> + <para>Publishing...</para> + </entry> - <entry align="center"> - <para>The status which shows if changes are being updated</para> - </entry> - </row> - <row> - <entry align="center"> - <para>Synchronized</para> - </entry> + <entry align="center"> + <para>The status which shows if changes are being updated</para> + </entry> + </row> + <row> + <entry align="center"> + <para>Synchronized</para> + </entry> - <entry align="center"> - <para>The status which allows you to see if changes are - in-sync</para> - </entry> - </row> - </tbody> - </tgroup> - </table> + <entry align="center"> + <para>The status which allows you to see if changes are synchronized</para> + </entry> + </row> + </tbody> + </tgroup> + </table> - <para>You can control a server behavior as well as adjust some server preferences with - the help of the context menu commands.</para> + <para>You can control a server behavior as well as adjust a number of server preferences through the context menu.</para> - <figure> - <title>Context Menu Commands</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_8.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Context Menu Commands</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_8.png"/> + </imageobject> + </mediaobject> + </figure> - <para>All available context menu commands are described in the following table.</para> - <table> - <title>Server Properties through the Context Menu</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> + <para>All available context menu commands are described in the following table.</para> + <table> + <title>Server Properties through the Context Menu</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> - <thead> - <row> - <entry align="center"> - <para>Name</para> - </entry> + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> - <tbody> - <row> - <entry> - <para>New Server</para> - </entry> - <entry> - <para>The option allows to define a new server</para> - </entry> - </row> + <tbody> + <row> + <entry> + <para>New Server</para> + </entry> + <entry> + <para>The option allows you to define a new server</para> + </entry> + </row> - <row> - <entry> - <para>Open</para> - </entry> - <entry> - <para>The option opens the Server editor</para> - </entry> - </row> + <row> + <entry> + <para>Open</para> + </entry> + <entry> + <para>The option opens the Server editor</para> + </entry> + </row> - <row> - <entry> - <para>Show in</para> - </entry> - <entry> - <para>This option gives an easy access to the next views: Console, - Debug view, Server Log or MBean Explorer</para> - </entry> - </row> + <row> + <entry> + <para>Show in</para> + </entry> + <entry> + <para>This option provides easy access to the Console, Debug, Server Log or MBean Explorer views</para> + </entry> + </row> - <row> - <entry> - <para>Delete</para> - </entry> - <entry> - <para>Standard option that allows to delete the chosen server</para> - </entry> - </row> + <row> + <entry> + <para>Delete</para> + </entry> + <entry> + <para>Standard option that allows you to delete the chosen server</para> + </entry> + </row> - <row> - <entry> - <para>Start</para> - </entry> - <entry> - <para>The action for stating a server in a run mode</para> - </entry> - </row> + <row> + <entry> + <para>Start</para> + </entry> + <entry> + <para>This will start the server in a run mode</para> + </entry> + </row> - <row> - <entry> - <para>Debug</para> - </entry> - <entry> - <para>The action for stating a server in a debug mode</para> - </entry> - </row> + <row> + <entry> + <para>Debug</para> + </entry> + <entry> + <para>This will start the server in a debug mode</para> + </entry> + </row> - <row> - <entry> - <para>Stop</para> - </entry> - <entry> - <para>The action for stopping a declared server</para> - </entry> - </row> + <row> + <entry> + <para>Stop</para> + </entry> + <entry> + <para>This will stop the server</para> + </entry> + </row> - <row> - <entry> - <para>Publish</para> - </entry> - <entry> - <para>The action for synchronizing the publish information between - the server and workspace</para> - </entry> - </row> + <row> + <entry> + <para>Publish</para> + </entry> + <entry> + <para>This will synchronize the publish information between the server and workspace</para> + </entry> + </row> - <row> - <entry> - <para>Explore</para> - </entry> - <entry> - <para>This action uses the native OS file explorer to browse the - deploy destination. Note: The option is also available for - deployed resources/projects (see the figure below).</para> - </entry> - </row> + <row> + <entry> + <para>Explore</para> + </entry> + <entry> + <para> + This action uses the native OS file explorer to browse the deploy destination. Note: The option is also available for deployed resources and projects (see the figure below). + </para> + </entry> + </row> - <row> - <entry> - <para>Add and Remove Projects</para> - </entry> - <entry> - <para>The option allows to publish a new project to the server (if - its type is supported)</para> - </entry> - </row> + <row> + <entry> + <para>Add and Remove Projects</para> + </entry> + <entry> + <para>This option will publish a new project to the server (if it's type is supported)</para> + </entry> + </row> - <row> - <entry> - <para>Monitoring</para> - </entry> - <entry> - <para>Possibility to add ports to be monitored on the current - server</para> - </entry> - </row> + <row> + <entry> + <para>Monitoring</para> + </entry> + <entry> + <para>Allows you to add ports to be monitored on the current server</para> + </entry> + </row> - <row> - <entry> - <para>Properties</para> - </entry> - <entry> - <para>Opens the window to adjust the current server - preferences</para> - </entry> - </row> + <row> + <entry> + <para>Properties</para> + </entry> + <entry> + <para>Opens a window that allows you to adjust the current server preferences</para> + </entry> + </row> - </tbody> - </tgroup> - </table> + </tbody> + </tgroup> + </table> - <para>Under the server element in the <property>Servers</property> view, you can - see currently deployed to the server modules and some server extensions which - provide the additional information on the server.</para> + <para> + Under the server element in the <guilabel>Servers</guilabel> view, you can see modules that are currently deployed to the server and some server extensions that provide additional information on the server. + </para> - <para>The context menu for any module allows you to remove it from the server, force a - full or incremental republish upon it.</para> + <para>The context menu for any module allows you to remove it from the server and force a full or incremental republish upon it.</para> - <figure> - <title>Modules Action</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_11.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Modules Action</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_11.png"/> + </imageobject> + </mediaobject> + </figure> - <section id="filesets"> - <title>Filesets</title> + <section id="filesets"> + <title>Filesets</title> - <para>The <emphasis> - <property>Filesets</property> - </emphasis> category in the <property>Servers</property> view is intended - for files filtering.</para> + <para>The <guilabel>Filesets</guilabel> category in the <guilabel>Servers</guilabel> view provides a way to filter files.</para> - <para>To add a new file filter, right-click the <emphasis> - <property>Filesets</property> - </emphasis> category and select <emphasis> - <property>Create File Filter</property>.</emphasis></para> - <para id="filefilterWiz">The <property>New File - Filter wizard</property> should appear.</para> + <para> + To add a new file filter, right-click the <guilabel>Filesets</guilabel> category and select the <guimenuitem>Create File Filter</guimenuitem> option. + </para> + <para id="filefilterWiz">The <guilabel>New File Filter wizard</guilabel> should appear.</para> - <figure> - <title>Creating a New File Filter</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/filesets1.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Creating a New File Filter</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/filesets1.png"/> + </imageobject> + </mediaobject> + </figure> - <para>The wizard asks you to enter the filter name and add includes and excludes - patterns. The preview box underneath gives a list of files matched to the - defined patterns (see the figures bellow).</para> - <para>In order to set up a default fileset relative to the concrete configuration of the server runtime, use the following variable: - <literal>${jboss_config}</literal>, i. e. you should type in the <emphasis> - <property>Root Directory</property></emphasis> something like <literal>server/${jboss_config}/</literal>. - This is implemented in order you can modify the runtime's configuration and not have to manually update paths.</para> - <figure> - <title>New File Filter Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/filesets2_a.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Notice, that the <emphasis> - <property>Browse</property></emphasis> button still returns an absolute path:</para> + <para> + The wizard asks you to enter the filter name and add includes and excludes patterns. The preview box underneath provides a list of files matched to the defined patterns (see the figures bellow). + </para> + <para> + In order to set up a default fileset relative to the fixed configuration of the server runtime, use the following variable: <filename>${jboss_config}</filename>, i. e. you should enter <filename>server/${jboss_config}/</filename> in the <guilabel>Root Directory</guilabel> option. This allows you to modify the runtime's configuration and not have to manually update paths. + </para> + <figure> + <title>New File Filter Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/filesets2_a.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>New File Filter Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/filesets2.png"/> - </imageobject> - </mediaobject> - </figure> + <para>Notice, that the <emphasis> + <property>Browse</property> + </emphasis> button still returns an absolute path:</para> - <para>After the filter is created, you can observe it by expanding the <emphasis> - <property>Filesets</property> - </emphasis> category in the <property>Servers</property> view.</para> + <figure> + <title>New File Filter Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/filesets2.png"/> + </imageobject> + </mediaobject> + </figure> - <para>It's possible now to edit files directly from the <emphasis> - <property>Filesets</property> - </emphasis> category. Double clicking on a file from <emphasis> - <property>Filesets</property> - </emphasis> opens up the editor automatically or you can use the <emphasis> - <property>Edit File</property> - </emphasis> context menu command.</para> + <para> + After the filter is created, you can explore it by expanding the <guilabel>Filesets</guilabel> category in the <guilabel>Servers</guilabel> view. + </para> - <figure> - <title>Direct Editing from the Filesets</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/filesets3.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + It is now possible to edit files directly from the <guilabel>Filesets</guilabel> category. Double clicking on a file from <guilabel>Filesets</guilabel> opens up the editor automatically, or you can use the <guimenuitem>Edit File</guimenuitem> context menu command. + </para> - <para>To delete a file filter (or just a file) from the <emphasis> - <property>Filesets</property>,</emphasis> right-click a file filter (or the - unnecessary file) and select the <emphasis> - <property>Delete File Filter</property> - </emphasis> - <emphasis>(<property>Delete File</property>)</emphasis> command.</para> + <figure> + <title>Direct Editing from the Filesets</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/filesets3.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Deleting the File from the Filesets</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/filesets4.png"/> - </imageobject> - </mediaobject> - </figure> - <para>If you want to set filesets for some server types, you should open - <emphasis><property>Window>Preferences</property></emphasis> - and then select <emphasis><property>Server > Default Filesets</property></emphasis> - from the categories available on the left.</para> + <para> + To delete a file filter (or just a file) from the <guilabel>Filesets</guilabel>, right-click a file filter or file and select the <guimenuitem>Delete File Filter</guimenuitem> or <guimenuitem>Delete File</guimenuitem> command. + </para> + + <figure> + <title>Deleting the File from the Filesets</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/filesets4.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + If you want to set filesets for some server types, select <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem></menuchoice> and then select <menuchoice><guimenuitem>Server</guimenuitem><guimenuitem>Default</guimenuitem></menuchoice> from the categories available on the left. + </para> + + <figure> + <title>Deleting the File from the Filesets</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/filesets5.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + On this preference page you can add a fileset to any server type or to all servers at once. To do this you should select the server type in the combo box and click the <guibutton>Add fileset...</guibutton> button. In the opened <guilabel>New File Filter wizard</guilabel> follow the steps described in <xref linkend="filefilterWiz"/> and finally click the <guibutton>Apply</guibutton> button on the preference page. + </para> + <para>The defined file filter will be automatically added to new servers during their creation.</para> - <figure> - <title>Deleting the File from the Filesets</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/filesets5.png"/> - </imageobject> - </mediaobject> - </figure> - <para>On this preference page you can add a fileset - to any server type or to all servers at once.To do this you should select the server type in the combo box and click <emphasis><property>Add fileset...</property></emphasis> button. - In the opened <property>New File - Filter wizard</property> follow the steps described <link linkend="filefilterWiz">before</link> and finally click <emphasis><property>Apply</property></emphasis> button on the preference page.</para> - <para>The defined file filter will be automatically added to new servers during creation.</para> - - - </section> - <section id="xml_configuration"> - <title>XML Configuration</title> - <para>The <emphasis> - <property>XML Configuration</property> - </emphasis> category allows you to quickly browse to descriptor files in your - server's deploy directory and check or change the values. Basically, <emphasis> - <property>XML Configuration</property> - </emphasis> includes XML XPaths where an xpath is a path used to access some - specific part of an xml document. </para> + </section> - <note> - <title>Note:</title> - <para>You are assumed to be familiar with XPath. If not, we highly suggested - that you look through an appropriate manual or tutorial on the topic.</para> - </note> + <section id="xml_configuration"> + <title>XML Configuration</title> + <para> + The <guilabel>XML Configuration</guilabel> category allows you to quickly browse to descriptor files in your server's deploy directory and check or change the values. Basically, <guilabel>XML Configuration</guilabel> includes XML XPaths, where an XPath is a path used to access some specific part of an XML document. + </para> - <para>The <emphasis> - <property>XML Configuration</property> - </emphasis> category itself contains only a list of categories. <emphasis> - <property>Ports</property> - </emphasis> are provided by default and is filled with many of the most commonly - used ports in the <property>JBoss Server</property>.</para> + <note> + <title>Note:</title> + <para> + This document assumes that you are familiar with XPath. If not, we highly suggested that you look through an appropriate manual or tutorial on the topic. + </para> + </note> - <figure> - <title>XML Configuration</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_14.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + The <guilabel>XML Configuration</guilabel> category itself contains only a list of categories. <guilabel>Ports</guilabel> are provided by default and display many of the most commonly used ports in the <productname>JBoss Server</productname>. + </para> + <figure> + <title>XML Configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_14.png"/> + </imageobject> + </mediaobject> + </figure> +  - <para>By right-clicking on <emphasis> - <property>XML Configuration</property>, </emphasis> you can create a new - category. Besides, context menu for <emphasis> - <property>XML Configuration</property> - </emphasis> category makes possible to disable it. You can disable any category - in the bottom part of the <emphasis> - <property>Servers</property> view.</emphasis> Look for them in the <emphasis> - <property>Inactive Categories</property> - </emphasis> afterwards to re-enable.</para> + <para> + By right-clicking on the <guilabel>XML Configuration</guilabel> node you can create a new category. Besides, context menu for <guilabel>XML Configuration</guilabel> category makes possible to disable it. You can disable any category in the bottom part of the <guilabel>Servers</guilabel> view. Look for them in the <guilabel>Inactive Categories</guilabel> afterwards to re-enable. + </para> - <figure> - <title>Adding New Category</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_15.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Adding New Category</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_15.png"/> + </imageobject> + </mediaobject> + </figure> - <para>By right-clicking on <emphasis> - <property>Ports</property> - </emphasis> or any other category in <emphasis> - <property>XML Configuration</property> - </emphasis>, you can create a new xpath.</para> + <para> + By right-clicking on the <guilabel>Ports</guilabel> category, or any other category in <guilabel>XML Configuration</guilabel>, you can create a new XPath. + </para> - <figure> - <title>Adding New XPath</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_16.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Adding New XPath</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_16.png"/> + </imageobject> + </mediaobject> + </figure> - <para>After that, the dialog shown below will appear.</para> + <para>After that, the dialog shown below will appear.</para> - <figure> - <title>Adding New XPath</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_17.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Adding New XPath</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_17.png"/> + </imageobject> + </mediaobject> + </figure> - <para>The goal here is to get an end result where the XPath matches up with a - necessary property. With that in mind, let's look how it works. If the - property you want to reach is the value of the <emphasis>name</emphasis> - attribute in the element <code><mbean></code>, then your <emphasis> - <property>XPath Patten</property> - </emphasis>should end with <emphasis>mbean</emphasis> and your <emphasis> - <property>Attribute Name</property> - </emphasis> should be <emphasis>name</emphasis> like on the next figure.</para> + <para> + The goal here is to get an end result where the XPath matches up with a necessary property. With that in mind, let's look how it works. If the property you want to reach is the value of the <code>name</code> attribute in the element <code><mbean></code>, then your <guilabel>XPath Patten</guilabel> should end with <code>mbean</code> and your <guilabel>Attribute Name</guilabel> should be <code>name</code>, as demonstrated in the next figure. + </para> - <programlisting role="XML"><![CDATA[... + <programlisting role="XML"><![CDATA[... <server> ... <mbean code="org.jboss.ejb.EJBDeployer" @@ -529,736 +476,664 @@ </server> ]]></programlisting> - <figure> - <title>XPath Preview</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_18.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>XPath Preview</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_18.png"/> + </imageobject> + </mediaobject> + </figure> - <tip> - <title>Tip:</title> - <para>Notice, when you type the fields autocomplete to help you locate exactly - what xpath you're looking for.</para> - </tip> + <note> + <title>Tip:</title> + <para>Notice when you type the fields autocomplete to help you locate exactly what XPath you're looking for.</para> + </note> - <para>Then, on the other hand, if your desired field is the text of an element - <code><description></code>, your <emphasis> - <property>XPath Patten</property> - </emphasis> should end with <emphasis>description</emphasis> and <emphasis> - <property>Attribute Name</property> - </emphasis> field should be left blank. When finished, click <emphasis> - <property>Preview</property> - </emphasis> to see how many matches you have for that particular XPath.</para> + <para> + If your desired field is the text of an element <code><description></code>, your <guilabel>XPath Patten</guilabel> should end with <code>description</code> and <guilabel>Attribute Name</guilabel> field should be left blank. When finished, click the <guibutton>Preview</guibutton> button to see how many matches are found for that particular XPath. + </para> - <figure> - <title>XPath Preview</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_19.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>XPath Preview</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_19.png"/> + </imageobject> + </mediaobject> + </figure> - </section> - </section> + </section> + </section> - <section id="dragndrop_to_jboss_server_view"> - <title>Drag-n-Drop to Servers view</title> + <section id="dragndrop_to_jboss_server_view"> + <title>Drag-n-Drop to Servers view</title> - <para>Starting from 2.0.0.CR2 version of <property>JBoss AS Tools</property> the - <property>Servers</property> view supports drag-n-drop of deployable and - runnable projects/resources.</para> + <para> + Starting from <productname>JBoss AS Tools</productname> 2.0.0.CR2 the <guilabel>Servers</guilabel> view supports drag-n-drop of deployable and runnable projects and resources. + </para> - <figure> - <title>Dragging to the Servers view</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/dnd_toJBossServerView.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Dragging to the Servers view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/dnd_toJBossServerView.png"/> + </imageobject> + </mediaobject> + </figure> - <para>With drag-n-drop the following actions can be performed:</para> + <para>With drag-n-drop the following actions can be performed:</para> - <itemizedlist> - <listitem> - <para>dragging a project to a server will deploy it to the server and run it by - showing the main page in a browser</para> - </listitem> + <itemizedlist> + <listitem> + <para>Dragging a project to a server will deploy it to the server and run it by showing the main page in a browser.</para> + </listitem> - <listitem> - <para>dragging an <emphasis> - <property>.xhtml</property> - </emphasis> file from <emphasis> - <property>WebContent</property> - </emphasis> will do the same and show the corresponding page in a - browser</para> - </listitem> + <listitem> + <para> + Dragging an <filename>.xhtml</filename> file from the <filename>WebContent</filename> folder will do the same and show the corresponding page in a browser. + </para> + </listitem> - <listitem> - <para>dragging a deployable resource (i.e. a datasource (<emphasis> - <property>-ds.xml</property> - </emphasis>) file that has been made deployable) will simply deploy that - resource directly to the server</para> - </listitem> - </itemizedlist> + <listitem> + <para> + Dragging a deployable resource (i.e. a datasource <filename>-ds.xml</filename> file that has been made deployable) will simply deploy that resource directly to the server. + </para> + </listitem> + </itemizedlist> - <para>In short, the feature does the same thing as if you used the <emphasis> - <property>Run On Server</property> - </emphasis> option or <emphasis> - <property>Add and Remove Projects</property> - </emphasis> option in the context menu of the server.</para> - </section> + <para> + In short, the feature does the same thing as if you used the <guimenuitem>Run On Server</guimenuitem> or <guimenuitem>Add and Remove Projects</guimenuitem> option in the context menu of the server. + </para> + </section> - <section id="server_log"> - <title>Server Log View</title> + <section id="server_log"> + <title>Server Log View</title> - <para>You can monitor the current server behavior with the help of the <property>Server - Log</property>. To open a server in the <property>Server Log view</property> you - should right-click on the server and follow to <emphasis> - <property>Open in > Server Log</property>.</emphasis></para> + <para> + You can monitor the current server behavior with the help of the <property>Server Log</property>. To open a server in the <property>Server Log view</property> you should right-click on the server and follow to <menuchoice><guimenuitem>Open in</guimenuitem><guimenuitem>Server Log</guimenuitem></menuchoice>. + </para> - <para>The <emphasis> - <property>Server Log</property> - </emphasis> shows relevant information to your server's startup, shutdown, - and publish processes. This allows you to keep an eye on what's going on - (such as automatic incremental deployment if you have it enabled).</para> + <para> + The <guilabel>Server Log</guilabel> view shows relevant information to your server's startup, shutdown and publish processes. This allows you to keep an eye on what's going on (such as automatic incremental deployment if you have it enabled). + </para> - <figure> - <title>Event Log Actions</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_12.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Event Log Actions</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_12.png"/> + </imageobject> + </mediaobject> + </figure> - <para>The <property>Server Log</property> toolbar contains several icons that perform - the following actions:</para> + <para>The <guilabel>Server Log</guilabel> view toolbar contains several icons that perform the following actions:</para> - <table> - <title>Server Log Toolbar Icons</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> + <table> + <title>Server Log Toolbar Icons</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> - <thead> - <row> - <entry align="center"> - <para>Name</para> - </entry> + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> - <tbody> - <row> - <entry> - <para>Export Log</para> - </entry> - <entry> - <para>Possibility to export the log into a text file</para> - </entry> - </row> + <tbody> + <row> + <entry> + <para>Export Log</para> + </entry> + <entry> + <para>Allows you to export the log into a text file</para> + </entry> + </row> - <row> - <entry> - <para>Clear Log Viewer</para> - </entry> - <entry> - <para>The option clears the current server log</para> - </entry> - </row> + <row> + <entry> + <para>Clear Log Viewer</para> + </entry> + <entry> + <para>This option clears the current server log</para> + </entry> + </row> - <row> - <entry> - <para>Delete Log</para> - </entry> - <entry> - <para>Click to delete the server log</para> - </entry> - </row> + <row> + <entry> + <para>Delete Log</para> + </entry> + <entry> + <para>Click to delete the server log</para> + </entry> + </row> - <row> - <entry> - <para>Open Log</para> - </entry> - <entry> - <para>Click to open the server log text file</para> - </entry> - </row> + <row> + <entry> + <para>Open Log</para> + </entry> + <entry> + <para>Click to open the server log text file</para> + </entry> + </row> - <row> - <entry> - <para>Restore Log</para> - </entry> - <entry> - <para>Click to restore the server log</para> - </entry> - </row> + <row> + <entry> + <para>Restore Log</para> + </entry> + <entry> + <para>Click to restore the server log</para> + </entry> + </row> - </tbody> - </tgroup> - </table> + </tbody> + </tgroup> + </table> - </section> + </section> - <section id="server_editor"> - <title>Server Editor</title> - <para>By double-clicking on any server, an editor window will appear allowing you to - edit parts of that server.</para> + <section id="server_editor"> + <title>Server Editor</title> + <para>By double-clicking on any server, an window will appear allowing you to edit the servers settings.</para> - <figure> - <title>Preferences Page for the Chosen Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_4.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Preferences Page for the Chosen Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_4.png"/> + </imageobject> + </mediaobject> + </figure> - <tip> - <title>Tip:</title> - <para>On the figure you can see that a username/password is available in the UI when - configuring the server. If you get a SecurityException when trying to launch the - server, it is most likely because your server is protected and hence you need to - fill the username/password fields with appropriate values.</para> - </tip> - - <para>Under the <emphasis> - <property>Publishing</property></emphasis> section it' possible to disable/inable the automatic publishing of the changes in the workspace.</para> + <note> + <title>Tip:</title> + <para> + On the figure you can see that the username and password fields are available. If you get a SecurityException when trying to launch the server, it is most likely because your server is protected, which requires that you need to fill the username and password fields with appropriate values. + </para> + </note> - <para>It should be pointed out that our server adapter by default tries to automatically - detect the ports it needs for integrating with a <property>JBoss Server</property>. - Sometimes it can though be relevant to override this automatic detection if you are - using some custom configuration. For this purposes the <emphasis> - <property>Server Ports</property> - </emphasis> section in the <property>Server editor</property> is provided where the - port settings are configurable. Click the <emphasis> - <property>Configure...</property> - </emphasis> link to bring up the wizard for adjusting the settings for the - ports.</para> + <para> + Under the <guilabel>Publishing</guilabel> section it is possible to disable or enable the automatic publishing of the changes in the workspace. + </para> - <figure> - <title>Server Ports Preferences</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_5.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + It should be pointed out that the server adapter tries to automatically detect the ports it needs for integrating with a <property>JBoss Server</property> by default. Sometimes it is necessary to override this automatic detection if you are using a custom configuration. The <guilabel>Server Ports</guilabel> section in the <guilabel>Server editor</guilabel> provides fields to customize port settings. Click the <guilabel>Configure...</guilabel> link to bring up the wizard for adjusting the settings for the ports. + </para> - <para>Press <emphasis> - <property>Edit XPath</property> - </emphasis> button for the chosen port to configure its XPath's values.</para> + <figure> + <title>Server Ports Preferences</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_5.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>XPath Pattern for a Server Port</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_6.png"/> - </imageobject> - </mediaobject> - </figure> + <para>Click the <guilabel>Edit XPath</guilabel> button for the chosen port to configure its XPath's values.</para> - <para>In the <property>Server editor</property> you are able to edit the timeouts and the server pollers to use.</para> - - <note> - <title>Note:</title> - <para>By default, the Startup poller is set to JMX Poller (see the <emphasis> - <property>Server Polling</property></emphasis> section). If you change the Startup poller - to Timeout Poller (it may need in case, for example, you're using the minimal configuration for your server), this will do no polling at all and will only set the server - state to <emphasis> - <property>"Started"</property></emphasis> after your startup timeout is reached.</para> - </note> + <figure> + <title>XPath Pattern for a Server Port</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_6.png"/> + </imageobject> + </mediaobject> + </figure> - <para id="com_line_arg"><property>Server editor</property> makes it also possible to - modify the server's launch configuration. It's just after clicking <emphasis> - <property>Open launch configuration</property> - </emphasis> link. In the open window there are the tabs for setting command line - arguments, main, classpaths and other things that are relevant to launching the - server.</para> + <para>In the <guilabel>Server editor</guilabel> you are able to edit the timeouts and the server pollers to use.</para> - <figure> - <title>Launch Configuration Properties</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_7.png"/> - </imageobject> - </mediaobject> - </figure> + <note> + <title>Note:</title> + <para> + By default, the Startup poller is set to JMX Poller. If you change the Startup poller to Timeout Poller (which may be required if you are using the minimal configuration for your server), this will do no polling at all and will only set the server state to <guilabel>"Started"</guilabel> after your startup timeout is reached. + </para> + </note> + + <para id="com_line_arg"> + The <guilabel>Server editor</guilabel> window also allows you to modify the server's launch configuration. The settings is available by clicking the the <guilabel>Open launch configuration</guilabel> link. The resulting window provides tabs for setting command line arguments, main, classpaths and other things that are relevant to launching the server. + </para> + + <figure> + <title>Launch Configuration Properties</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_7.png"/> + </imageobject> + </mediaobject> + </figure> - - <para>The first tab shows the Jboss server arguments</para> - <para>Look up <ulink - url="http://docs.jboss.org/jbossas/guides/installguide/r1/en/html/start-stop.html" - >AS Installation Guide </ulink> to find parameters which can be specified for <property>JBoss - Server</property>.</para> - <note> - <title>Note:</title> - <para>Please note, that the Launch Configurations for JBoss Servers are enough - strict in enforcing the configured values in the server in order to avoid - inconsistencies between server's and their configured runtime.</para> + <para>The first tab shows the JBoss server arguments</para> + <para> + See the <ulink url="http://docs.jboss.org/jbossas/guides/installguide/r1/en/html/start-stop.html">AS Installation Guide </ulink> to find the parameters that can be specified for <productname>JBoss Server</productname>. + </para> - <para>For example, if you change the launch configuration program arguments to - <emphasis>"-c myConfig"</emphasis> but do not change the - targeted runtime configuration, then your program arguments will be ignored. The - server runtime "wins" so to speak. This ensures consistency - and if you change the location of the runtime, your launch configurations will - automatically pick that up.</para> + <note> + <title>Note:</title> + <para> + Please note that the values in the Launch Configurations for JBoss Servers are strictly enforced in order to avoid inconsistencies between server's and their configured runtime. + </para> - <para>Values are not controlled by the server and its runtime setup will be passed - on unaltered.</para> - </note> - - <para>On the second tab you find the main class used for launching JBoss AS (default is org.jboss.Main), you can change it, if necessary. </para> + <para> + For example, if you change the launch configuration program arguments to <code>"-c myConfig"</code> but do not change the targeted runtime configuration, then your program arguments will be ignored. The configuration of the server runtime "wins" so to speak. This ensures consistency and if you change the location of the runtime, your launch configurations will automatically pick that up. + </para> - <para>Until 3.0.0.GA release of <property>JBoss Tools</property>, the servers classpath - was readonly, but that caused problems for users wanting to add their own jars in - the startup classpath. That is relevant if you need to patch the server, add a - custom charset or other tweaks that require early access to the classpath.</para> + <para>Values are not controlled by the server and its runtime setup will be passed on unaltered.</para> + </note> - <para>Now all servers have a custom 'server runtime classpath - container', which is there by default and point to the default jars in - JBoss. You can now adjust the classpath. Then just make sure this container is there - if you want the classpath to be picked up.</para> + <para> + On the second tab you find the main class used for launching JBoss AS (the default is <code>org.jboss.Main</code>). This value can be changed if necessary. + </para> - <figure> - <title>Server Classpaths</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/server_classpaths.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + Until <property>JBoss Tools</property> 3.0.0.GA the servers classpath was read only, but that caused problems for users wanting to add their own JARs in the startup classpath. That is relevant if you need to patch the server, add a custom charset or other tweaks that require early access to the classpath. + </para> - <para>If for some reason you have a launch configuration without this container, <emphasis> - <property>Restore Default Entries</property> - </emphasis> should add it properly. Also, <emphasis> - <property>Restore Default Entries</property> - </emphasis> will also remove any extra entries you added yourself.</para> - <para>Using <emphasis>Deployment tab</emphasis> you configure local deployment settings.</para> + <para> + Now all servers have a custom 'server runtime classpath container', which is there by default and point to the default JARs in JBoss. You can now adjust the classpath. Then just make sure this container is there if you want the classpath to be picked up. + </para> + + <figure> + <title>Server Classpaths</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/server_classpaths.png"/> + </imageobject> + </mediaobject> + </figure> + + <para> + If for some reason you have a launch configuration without this container, the <guibutton>Restore Default Entries</guibutton> button should add it properly. Also, the <guibutton>Restore Default Entries</guibutton> button will remove any extra entries you added yourself. + </para> + + <para>Using <guilabel>Deployment tab</guilabel> you configure local deployment settings.</para> - - <figure> - <title>Deployment tab</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_7a.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Using the group of radio buttons in <property>Default Settings section</property> - a user can set where the application will - be deployed to.By default it is deployed to the user's workspace folder, - exactly to <property>[workspaceDirecotry]\.metadata\.plugins</property>.If you would like the application to be deployed to your Jboss - server deploy folder select <emphasis><property>Use the JBoss deploy folder</property></emphasis>. - The option to specify your custom deploy folder is also available.</para> - </section> - <section> - <title>Relevant Resources Links</title> - <para>Find more about XPath in the <ulink url="http://www.w3.org/TR/xpath20/">XPath - Documentation</ulink>.</para> - </section> - </section> + <figure> + <title>Deployment tab</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_7a.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + Using the group of radio buttons in the <guilabel>Default Settings</guilabel> section a user can set where the application will be deployed to. By default it is deployed to the user's workspace folder, <filename>[workspaceDirecotry]\.metadata\.plugins</filename>. If you would like the application to be deployed to your JBoss server deploy folder select the <guilabel>Use the JBoss deploy folder</guilabel> option. The option to specify your custom deploy folder is also available. + </para> + </section> - <section id="Project_archivesView" role="updated"> - <title>Project Archives View</title> - <para>Every application, whether Plain Old Java, J2EE, or some other language altogether, - needs to be packaged in some way. In Java-related projects, many people use ANT. </para> - <note> - <title>Note:</title> - <para>Those who use ANT will appreciate how the Project Archives Ant task is now - improved: it supports variables and gives more informative error/logging messages - when something goes wrong.</para> - </note> + <section> + <title>Relevant Resources Links</title> + <para>Find more about XPath in the <ulink url="http://www.w3.org/TR/xpath20/">XPath Documentation</ulink>.</para> + </section> + </section> - <para>But <property>JBoss Tools</property> come with our own Archives tool with a bit easier - and less-verbose XML and a handy user interface. The Project Archives plugin consists - primarily of a view, that is <property>Project Archives view</property>, to set up each - packaging configuration.</para> - <para>So far, let's look through all functionality that the <property>Project - Archives view</property> provides.</para> + <section id="Project_archivesView" role="updated"> + <title>Project Archives View</title> + <para> + Every application, whether Plain Old Java, J2EE, or some other language altogether, needs to be packaged in some way. In Java-related projects, many people use ANT. + </para> + <note> + <title>Note:</title> + <para> + Those who use ANT will appreciate how the Project Archives Ant task is now improved: it supports variables and gives more informative error/logging messages when something goes wrong. + </para> + </note> - <section id="archives_overview"> - <title>Overview</title> + <para> + But <productname>JBoss Tools</productname> comes with our own Archives tool with simpler and less-verbose XML and a handy user interface. The Project Archives plugin consists primarily of the <guilabel>Project Archives</guilabel> view to set up each packaging configuration. + </para> + + <para>Let's look through all functionality that the <guilabel>Project Archives</guilabel> view provides.</para> - <para>The packaging configuration for each project is stored in the project's root - folder, and is in a file named <emphasis> - <property>.packages</property> - </emphasis>, which has a fairly simple XML structure. Modifying the file by hand is - neither required nor recommended, and using the UI is the official way of modifying - your packaging structure.</para> + <section id="archives_overview"> + <title>Overview</title> - <figure> - <title>Archives View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_21.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + The packaging configuration for each project is stored in the project's root folder in a file named <filename>.packages</filename>, which has a fairly simple XML structure. Modifying the file by hand is neither required nor recommended, as the UI is the only supported way to modify your packaging structure. + </para> - <para>A project's configuration contains archives. As you can see on the image - above a project can contain more than one archive. Internal archives and filesets - can be directly inside of an archive, or in some sub-folder of that archive.</para> + <figure> + <title>Archives View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_21.png"/> + </imageobject> + </mediaobject> + </figure> - <para>In the upper right corner of the view you can see an icon which, when clicked, - will build the selected top-level archive. Additionally, you can select <emphasis> - <property>Project > Build Packages</property> - </emphasis> when a project is selected in the <property>Packages View</property> to - build all declared packages in that project's <emphasis> - <property>.packages</property> - </emphasis> file. This will execute a full build on all declared archives.</para> - </section> + <para> + A project's configuration contains archives. As you can see on the image above a project can contain more than one archive. Internal archives and filesets can be directly inside of an archive, or in a sub-folder of that archive. + </para> - <section id="Creating_Archive"> - <title>Creating an Archive</title> + <para> + In the upper right corner of the view you can see an icon which, when clicked, will build the selected top-level archive. Additionally, you can select <menuchoice><guimenuitem>Project</guimenuitem><guimenuitem>Build Packages</guimenuitem></menuchoice> when a project is selected in the <guilabel>Packages View</guilabel> to build all declared packages in that project's <filename>.packages</filename> file. This will execute a full build on all declared archives. + </para> + </section> - <para>When you open the <property>Project archives view</property> for the first time, - it asks you to select the project for what you want to create an archive.</para> + <section id="Creating_Archive"> + <title>Creating an Archive</title> - <figure> - <title>Archives View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_21a.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + When you open the <guilabel>Project archives</guilabel> view for the first time, it asks you to select the project for which you want to create an archive. + </para> - <para>When creating a new archive for selected project, you have some different options - at your disposal. You need right-click inside the view and select <emphasis> - <property>New Archive</property> - </emphasis> to see your archive type options.</para> + <figure> + <title>Archives View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_21a.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Create an Archive</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_22.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + When creating a new archive for selected project, you have some different options at your disposal. You need right-click inside the view and select <guimenuitem>New Archive</guimenuitem> to see your archive type options. + </para> - <note> - <title>Note:</title> - <para>If you see only JAR from the list of available archive types, you should - verify whether AS Tools plugins/features are in place. EAR, EJB JAR and WAR - options are contributed by the AS Tools independently from webtools and the - virtual project model. Thus, without them only JAR will show up.</para> - </note> + <figure> + <title>Create an Archive</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_22.png"/> + </imageobject> + </mediaobject> + </figure> - <para><property>JAR</property> is the standard archive type, and does very little - configuration, leaving most of the work up to you. You can customize the name, add - folders, filesets, and inner jars to it.</para> + <note> + <title>Note:</title> + <para> + If you see only JAR from the list of available archive types, you should verify whether AS Tools plugins are installed. EAR, EJB JAR and WAR options are contributed by the AS Tools independently from webtools and the virtual project model. So without them only the JAR option will show up. + </para> + </note> - <para>The other types, for the most part, simply start off with a default setting, - usually the jar with some specific children based on an expected structure of the - project. For example, if the project is a Dynamic Web Project, and you create a - <property>WAR</property> archive, the archive will be created with a few - filesets relevant to the known structure of the project.</para> + <para> + <filename>JAR</filename> is the standard archive type and does very little configuration, leaving most of the work up to you. You can customize the name, add folders, filesets and inner JARs to it. + </para> - <para>Here is the first page of all New archive wizards. It is the same for any archive - type and the only page in the <property>New Jar wizard</property>.</para> - <figure> - <title>New WAR Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_23.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + The other types, for the most part, simply start off with a default setting, usually the JAR with some specific children based on an expected structure of the project. For example, if the project is a Dynamic Web Project and you create a <filename>WAR</filename> archive, the archive will be created with a few filesets relevant to the known structure of the project. + </para> - <para>The page is pretty simple. First it asks to set the name of your new archive and a - destination.</para> + <para> + Here is the first page of all New archive wizards. It is the same for any archive type and the only page in the <guilabel>New JAR</guilabel> wizard. + </para> + <figure> + <title>New WAR Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_23.png"/> + </imageobject> + </mediaobject> + </figure> - <para>The destination of an archive can be anywhere on the file system, anywhere in the - workspace, inside some other archive, or inside a folder declared inside an archive. - Select the necessary checkbox (either <emphasis> - <property>workspace</property> - </emphasis> or <emphasis> - <property> file system</property> - </emphasis>) for marking the destination as related to either workspace or file - system. You can browse to workspace or filesystem destinations by clicking on their - respective buttons. To select a destination inside some other archive, you'll need - to press the <emphasis> - <property>Workspace</property> - </emphasis> button. At the bottom of the list, you'll see archives that - have been declared in the workspace.</para> + <para>The page is pretty simple. First it prompts you to set the name of your new archive and a destination.</para> - <figure> - <title>Selecting the destination in the workspace</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_23a.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + The destination of an archive can be anywhere on the file system, anywhere in the workspace, inside another archive, or inside a folder declared inside an archive. Select the appropriate checkbox (either <guilabel>workspace</guilabel> or <guilabel>file system</guilabel>) to specify that the destination is related to either the workspace or filesystem. You can browse to workspace or filesystem destinations by clicking on their respective buttons. To select a destination inside some other archive, you'll need to click the <guibutton>Workspace</guibutton> button. At the bottom of the list, you will see the archives that have been declared in the workspace. + </para> - <para>Also in the wizard for creating a new archive you can choose whether an archive to - be compressed or exploded into a folder (without compression). You need just select - proper chechbox in the <emphasis> - <property>Archive type</property> - </emphasis> section.</para> - <para>If a build or incremental update fails Project Archives will show an error - dialog:</para> - <figure> - <title>Selecting the destination in the workspace</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/projectarchives_error.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Click in <emphasis> - <property>Details</property> - </emphasis> to see detailed information about what caused the error.</para> + <figure> + <title>Selecting the destination in the workspace</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_23a.png"/> + </imageobject> + </mediaobject> + </figure> - <para>In the <property>Package Explorer</property> you can observe the created - archive.</para> - <figure> - <title>The Archive in the Package Explorer</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_23b.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + Also in the wizard for creating a new archive you can choose whether an archive to be compressed or exploded into a folder (without compression). You need just select proper checkbox in the <guilabel>Archive type</guilabel> section. + </para> + + <para>If a build or incremental update fails Project Archives will show an error dialog:</para> + <figure> + <title>Selecting the destination in the workspace</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/projectarchives_error.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Click the <guibutton>Details</guibutton> button to view detailed information about the cause of the error.</para> - <para>If you use the exploded type of archiving, instead of a single file archive the - result put into a folder is displayed in the <property>Package - Explorer</property>.</para> - <figure> - <title>The Exploded Archive in the Package Explorer</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_23c.png"/> - </imageobject> - </mediaobject> - </figure> + <para>In the <guilabel>Package Explorer</guilabel> you can view the created archive.</para> + <figure> + <title>The Archive in the Package Explorer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_23b.png"/> + </imageobject> + </mediaobject> + </figure> - <section id="CreatingaFolder"> - <title>Creating a Folder</title> - <para>Creating a folder is much easier. You simply right-click on an archive or - folder you want your new folder to be a child under. The only piece of required - information is naming the file.</para> - </section> - <section id="CreatingaFileSet"> - <title>Creating a FileSet</title> - <para>To create a new fileset, you click on an available target location such as an - archive, a nested archive, or a folder within an archive, and select <emphasis> - <property>New Fileset</property>. </emphasis></para> - <para>The <property>New Fileset wizard</property> requires a destination (where the - files will go), and a root directory (or where the files are coming from). The - source can be anywhere in the workspace or from the filesystem at large.</para> + <para> + If you use the exploded type of archiving, instead of a single file archive the result put into a folder is displayed in the <guilabel>Package Explorer</guilabel>. + </para> + + <figure> + <title>The Exploded Archive in the Package Explorer</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_23c.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Adding a New FileSet</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_24.png"/> - </imageobject> - </mediaobject> - </figure> + <section id="CreatingaFolder"> + <title>Creating a Folder</title> + <para> + To create a folder right-click on an archive or folder you want your new folder to be a child of. The only piece of required information the folder name. + </para> + </section> + <section id="CreatingaFileSet"> + <title>Creating a FileSet</title> + <para> + To create a new fileset, right click on an available target location such as an archive, a nested archive, or a folder within an archive and select the <guimenuitem>New Fileset</guimenuitem> option. + </para> + <para> + The <guilabel>New Fileset</guilabel> wizard requires a destination (where the files will be located) and a root directory (or where the files are coming from). The source can be anywhere in the workspace or from the filesystem at large. + </para> - <para>Below that, the fileset requires only an includes pattern and an excludes - pattern. As you type in either of these fields, the preview viewer should update - itself with which files are matched.</para> + <figure> + <title>Adding a New FileSet</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_24.png"/> + </imageobject> + </mediaobject> + </figure> - <para>You can create a Fileset with flattening or without it. Look at the difference - on the figure below.</para> + <para> + Below that, the fileset requires only an <guilabel>Includes</guilabel> and <guilabel>excludes</guilabel> pattern. As you type in either of these fields, the preview viewer will list those files that are matched. + </para> - <figure> - <title>The FileSet with flattening and without it</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_24a.png"/> - </imageobject> - </mediaobject> - </figure> + <para>You can create a Fileset with flattening or without it. Look at the difference on the figure below.</para> - </section> - - <section id="CreatingaUserLibrariesFileSet"> - <title>Creating User Library FileSet</title> - - <para>If you use user libraries in your projects you can also refer to these from project archives and have all the .jar/.zip files they refer included into the archive.</para> - <para>To add a new user libraries file set, call the right-click menu on the necessary archive and choose " New User Libraries FileSet" item</para> - - <figure> - <title>Adding New User Library Fileset</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/userlibraryfileset1.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>You can edit the existing user libraries as well using "User Libraries Fileset Wizard". Call the right-click menu on the library fileset and choose "Edit Fileset " item</para> - - <figure> - <title>Editing User Library Fileset</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/userlibraryfileset2.png"/> - </imageobject> - </mediaobject> - </figure> - - </section> - - </section> + <figure> + <title>The FileSet with flattening and without it</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_24a.png"/> + </imageobject> + </mediaobject> + </figure> - <section id="View_Actions"> - <title>Archive Actions</title> - <figure> - <title>Context Menu on the Item</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_25.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The context menu on the items in the view is extendable, but there are several - that come standard.</para> + </section> - <table> - <title>Context Menu on the Item</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> + <section id="CreatingaUserLibrariesFileSet"> + <title>Creating User Library FileSet</title> + <para> + If you make use of user libraries in your projects you can also refer to these from project archives and have all the JAR and ZIP files they refer included into the archive. + </para> + <para> + To add a new user libraries file set, right-click on the necessary archive and select the <guimenuitem>New User Libraries FileSet</guimenuitem> option. + </para> - <thead> - <row> - <entry align="center"> - <para>Name</para> - </entry> + <figure> + <title>Adding New User Library Fileset</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/userlibraryfileset1.png"/> + </imageobject> + </mediaobject> + </figure> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> + <para> + You can edit the existing user libraries as well using <guilabel>User Libraries Fileset</guilabel> Wizard. Right-click on the library fileset and select the <guimenuitem>Edit Fileset</guimenuitem> option. + </para> - <tbody> + <figure> + <title>Editing User Library Fileset</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/userlibraryfileset2.png"/> + </imageobject> + </mediaobject> + </figure> - <row> - <entry> - <para>Build Archive (Full)</para> - </entry> + </section> - <entry> - <para>The action enabled only on top-level archives, which initiates - a full build on that archive</para> - </entry> - </row> + </section> - <row> - <entry> - <para>Edit Archive</para> - </entry> + <section id="View_Actions"> + <title>Archive Actions</title> + <figure> + <title>Context Menu on the Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_25.png"/> + </imageobject> + </mediaobject> + </figure> + <para>There are a number of variable options in the context menu, but there are also several that come standard.</para> - <entry> - <para>Standard action that brings up the wizard associated with that - particular node type and allows the details to be changed</para> - </entry> - </row> + <table> + <title>Context Menu on the Item</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> - <row> - <entry> - <para>Delete Archive</para> - </entry> - <entry> - <para>Deleting node is standard action with deletion not needing an - explanation</para> - </entry> - </row> + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> - <row> - <entry> - <para>Publish To Server</para> - </entry> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> - <entry> - <para>The action means the ability to publish to a declared - server</para> - </entry> - </row> + <tbody> - <row> - <entry> - <para>Edit publish settings</para> - </entry> + <row> + <entry> + <para>Build Archive (Full)</para> + </entry> - <entry> - <para>Gives possibility to edit an archive publish settings</para> - </entry> - </row> + <entry> + <para>This action is enabled only on top-level archives and initiates a full build on that archive</para> + </entry> + </row> - </tbody> - </tgroup> - </table> - - <note> - <title>Note:</title> - <para>When editing an archive, it is also updated in all folders and other archives where it is nested.</para> - </note> - </section> + <row> + <entry> + <para>Edit Archive</para> + </entry> - <section id="PublishToServer"> - <title>Publishing to Server</title> - <para>Finally, you'll need to publish your application to a server. Here, we - show you how to do it with the help of <emphasis> - <property>Archives View</property>. </emphasis></para> + <entry> + <para>Standard action that brings up the wizard associated with that particular node type and allows the details to be changed</para> + </entry> + </row> - <figure> - <title>Context Menu on the Item</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/perspective/perspective_26.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The dialog above appears after selecting <emphasis> - <property>Publish To Server</property>. </emphasis> To simply publish once, you - just select the server(s) that you want, and finish. If you want the <emphasis> - <property>Publish to Server</property> - </emphasis> action on that particular Archive to publish always to that set of - servers, then check the appropriate checkbox. And finally, to enable automatic - publishing upon build events, check the last checkbox.</para> - <para>The automatic publishing feature is nice if, for example, your package's - destination (where it is built) is a temporary folder and you want the archive - published to several servers. If you only really want your archive published to one - server, it might be easier to have the archive's destination folder be the deploy - folder of the server.</para> - </section> - <section id="rel_res_links_archiving"> - <title>Relevant Resources Links</title> - <para>Refer to <ulink url="http://ant.apache.org/manual/index.html">Ant manual</ulink> - to find more on how to build your applications with help of Ant.</para> + <row> + <entry> + <para>Delete Archive</para> + </entry> - <para>We also recommend you to watch the <ulink - url="http://docs.jboss.org/tools/movies/demos/archiving/archiving.htm" - >movie</ulink> which demonstrates a powerful archiving functionality in - <property>JBoss Tools</property>.</para> + <entry> + <para>This option deletes the selected node</para> + </entry> + </row> - <para>At this point, you are guessed to be familiar with <property>JBoss AS - perspective</property> and your next step now is to explore how to work with - different kinds of projects.</para> - </section> + <row> + <entry> + <para>Publish To Server</para> + </entry> - </section> + <entry> + <para>This action will publish to a declared server</para> + </entry> + </row> + <row> + <entry> + <para>Edit publish settings</para> + </entry> + <entry> + <para>This option edits the archives publish settings</para> + </entry> + </row> + + </tbody> + </tgroup> + </table> + + <note> + <title>Note:</title> + <para>When editing an archive, it is also updated in all folders and other archives where it is nested.</para> + </note> + </section> + + <section id="PublishToServer"> + <title>Publishing to Server</title> + <para> + Finally, you will need to publish your application to a server. This section describes how to do it with the help of the <guilabel>Archives</guilabel> View. + </para> + + <figure> + <title>Context Menu on the Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/perspective/perspective_26.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + The dialog shown above appears after selecting the <guilabel>Publish To Server</guilabel> option. To publish once, select the server(s) that you want and click the <guibutton>Finish</guibutton> button. If you want the <guilabel>Publish to Server</guilabel> action on that particular Archive to always publish to that set of servers, then check the appropriate checkbox. To enable automatic publishing upon build events, check the last checkbox. + </para> + <para> + The automatic publishing feature is nice if, for example, your package's destination (where it is built) is a temporary folder and you want the archive published to several servers. If you only need your archive published to one server, it might be easier to have the archive's destination folder be the deploy folder of the server. + </para> + </section> + <section id="rel_res_links_archiving"> + <title>Relevant Resources Links</title> + <para> + Refer to the <ulink url="http://ant.apache.org/manual/index.html">Ant manual</ulink> to find more on how to build your applications using Ant. + </para> + + <para> + We also recommend that you watch this <ulink url="http://docs.jboss.org/tools/movies/demos/archiving/archiving.htm">movie</ulink> which demonstrates the powerful archiving functionality in <productname>JBoss Tools</productname>. + </para> + + <para> + This chapter has covered the functionality provided by the <property>JBoss AS perspective</property>. The next chapter will explore working with different kinds of projects. + </para> + </section> + + </section> + + </chapter> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/quick_start.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/quick_start.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/quick_start.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -1,293 +1,290 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="quick_start" role="updated"> - <title>Quick Start with JBoss Server</title> + <title>Quick Start with JBoss Server</title> - <para>This chapter covers the basics of working with the <property>JBoss Server</property>.</para> - - <section id="JBoss_server_key_features"> - <title>Key Features of JBoss Server</title> - <para>For a start, we propose you to look through the table of main features of JBoss Server:</para> - - <table> - - <title>Key Functionality for JBoss AS and Archive Tools</title> - <tgroup cols="3"> - - <colspec colnum="1" align="left" colwidth="2*"/> - <colspec colnum="2" colwidth="4*"/> - <colspec colnum="3" align="left" colwidth="2*"/> - - <thead> - <row> - <entry>Feature</entry> - <entry>Benefit</entry> - <entry>Chapter</entry> - </row> - </thead> - <tbody> - <row> - <entry><para>JBoss AS plugin</para></entry> - <entry><para>Using WTP, JBoss AS plugin allows working with the server in run or debug mode. You can easily install runtimes and servers, copy the existing runtime configuration or configure it up to your needs.</para></entry> - <entry> - <link linkend="runtimes_servers">runtimes and servers</link> - </entry> - </row> - - <row> - <entry><para>JBoss AS Perspective</para></entry> - <entry><para>It makes managing installed JBoss Server quite easy and includes the standard Console and Properties views, and specially added Project archives view and Servers view for that purpose. </para></entry> - <entry> - <link linkend="perspective">JBoss AS perspective</link> - </entry> - </row> - - <row> - <entry><para>Modules Deployment</para></entry> - <entry><para>A number of ways, provided by WTP and JBoss Tools, to deploy either a project or a single file on the server.</para></entry> - <entry> - <link linkend="modules">deploying modules</link> - </entry> - </row> - - <row> - <entry><para>TPTP Support</para></entry> - <entry><para>Test and Performance Tools Platform (TPTP) profiling.</para></entry> - <entry> - <link linkend="tptp_support">TPTP support</link> - </entry> - </row> - - </tbody> - - </tgroup> - </table> + <para>This chapter covers the basics of working with the <property>JBoss Server</property>.</para> + + <section id="JBoss_server_key_features"> + <title>Key Features of JBoss Server</title> + <para>The table below lists the main features included in JBoss Server:</para> + + <table> + + <title>Key Functionality for JBoss AS and Archive Tools</title> + <tgroup cols="3"> + + <colspec colnum="1" align="left" colwidth="2*"/> + <colspec colnum="2" colwidth="4*"/> + <colspec colnum="3" align="left" colwidth="2*"/> + + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + <entry>Chapter</entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>JBoss AS plugin</para> + </entry> + <entry> + <para> + Using WTP the JBoss AS plugin allows you to work with the server in run or debug mode. You can easily install runtimes and servers, copy the existing runtime configuration or configure it up to your needs. + </para> + </entry> + <entry> + <link linkend="runtimes_servers">Runtimes and servers</link> + </entry> + </row> + + <row> + <entry> + <para>JBoss AS Perspective</para> + </entry> + <entry> + <para> + It provides easy management of an installed JBoss Server and includes the standard Console and Properties views and the specially added Project archives and Servers views. + </para> + </entry> + <entry> + <link linkend="perspective">JBoss AS perspective</link> + </entry> + </row> + + <row> + <entry> + <para>Modules Deployment</para> + </entry> + <entry> + <para>Provides a number of ways, using WTP and JBoss Tools, to deploy either a project or a single file on the server.</para> + </entry> + <entry> + <link linkend="modules">Deploying modules</link> + </entry> + </row> + + <row> + <entry> + <para>TPTP Support</para> + </entry> + <entry> + <para>Test and Performance Tools Platform (TPTP) profiling.</para> + </entry> + <entry> + <link linkend="tptp_support">TPTP support</link> + </entry> + </row> + + </tbody> + + </tgroup> + </table> - <para>If you - already have installed JBoss server and runtime you can quickly learn how to configure, start, - stop the server, to know deployment and archiving processes. How to install runtimes and servers - read in the <link linkend="runtimes_servers">Runtimes and Servers in the JBoss AS plugin</link> - chapter.</para> + <para> + If you already have installed the JBoss server and runtime this document will show you how to configure, start and stop the server, as well as the deployment and archiving processes. Installing runtimes and servers is covered in more detail in <xref linkend="runtimes_servers"/>. + </para> - <para>To start working with JBoss AS, select a <property>JBoss AS Perspective</property> via - <emphasis><property>Window > Show View > Other > Server > Servers</property>.</emphasis></para> - </section> + <para> + To start working with JBoss AS, select the <guilabel>JBoss AS</guilabel> Perspective via <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>Server</guimenuitem><guimenuitem>Servers</guimenuitem></menuchoice>. + </para> + </section> - <section id="starting"> - <title>Starting JBoss Server</title> + <section id="starting"> + <title>Starting JBoss Server</title> - <para>Starting <property>JBoss Server</property> is quite simple. You can control the server - behaviour with the help of a special toolbar in the <property>Servers</property> view - where you could <emphasis> - <property>start</property> - </emphasis> it in a regular or debug mode, <emphasis> - <property>stop</property> - </emphasis> it or <emphasis> - <property>restart</property> - </emphasis> it and <emphasis> - <property>publish</property> - </emphasis> to the server.</para> + <para> + Starting <productname>JBoss Server</productname> is quite simple. You can control the server behavior with the help of a special toolbar in the <guilabel>Servers</guilabel> view where you can <guibutton>start</guibutton> it in a regular or debug mode, <guibutton>stop</guibutton> or <guibutton>restart</guibutton> it and <guibutton>publish</guibutton> to the server. + </para> - <figure> - <title>Servers Toolbar</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start_1.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Servers Toolbar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_1.png"/> + </imageobject> + </mediaobject> + </figure> - <para>To launch the server click the green-with-white-arrow icon on the <property>Servers - </property> view or right click server name in this view and select <emphasis> - <property>Start</property>. </emphasis> If this view is not open, select - <emphasis><property>Window > Show View > Other > Server > - Servers</property>.</emphasis></para> + <para> + To launch the server click the green-with-white-arrow icon on the <guilabel>Servers</guilabel> view or right click server name in this view and select <guimenuitem>Start</guimenuitem>. If this view is not open, select <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>Server</guimenuitem><guimenuitem>Servers</guimenuitem></menuchoice>. + </para> - <figure> - <title>Start JBoss Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start_2.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Start JBoss Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_2.png"/> + </imageobject> + </mediaobject> + </figure> - </section> + </section> - <section id="stopping"> - <title>Stopping JBoss Server</title> + <section id="stopping"> + <title>Stopping JBoss Server</title> - <para>To stop the server, click the <emphasis> - <property>Stop</property> - </emphasis> icon in the <property>Servers</property> view or right click the server name - and press <emphasis><property>Stop</property>.</emphasis></para> + <para> + To stop the server, click the <guibutton>Stop</guibutton> icon in the <guilabel>Servers</guilabel> view or right click the server name + and select the <guimenuitem>Stop</guimenuitem> option. + </para> - <figure> - <title>Stop JBoss Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start_3.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Stop JBoss Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_3.png"/> + </imageobject> + </mediaobject> + </figure> - <para>When the server is stopped you will see <emphasis> - <property>Stopped</property> - </emphasis> state next to its name in the square brackets.</para> - <para>Learn more about the <property>Servers</property> view - <link linkend="JBossServerView">here</link>.</para> - </section> + <para>When the server is stopped you will see <guilabel>Stopped</guilabel> state next to its name in the square brackets.</para> + <para>Learn more about the <guilabel>Servers</guilabel> view in <xref linkend="JBossServerView"/>.</para> + </section> - <section id="archiving"> + <section id="archiving"> - <title>Project Archiving</title> + <title>Project Archiving</title> - <para><property>JBoss Tools</property> comes with our own archives tool. The Project Archives - plugin consists primarily of a view to set up each packaging configuration <emphasis>( - <property>Window > Show View > Other > JBoss Tools > Project archives</property>). - </emphasis></para> - <para>Right clicking in the <property>Project archives</property> view you can create War, - EJB War, EAR or JAR archive.</para> + <para> + <property>JBoss Tools</property> comes with our own archives tool. The Project Archives plugin consists primarily of a view to set up each packaging configuration (<menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Show View</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>JBoss Tool</guimenuitem><guimenuitem>Project archives</guimenuitem></menuchoice>). + </para> + <para>Right clicking in the <guilabel>Project archives</guilabel> view you can create a War, EJB War, EAR or JAR archive.</para> - <figure> - <title>Archive Creating</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start_7.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Archive Creating</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_7.png"/> + </imageobject> + </mediaobject> + </figure> - <para>Using the context menu on the item you can initiate a <emphasis><property>full build</property></emphasis> on - archive, <emphasis><property>edit</property>,</emphasis> <emphasis><property>delete</property></emphasis> or - <emphasis><property>publish</property></emphasis> it.</para> + <para> + Using the context menu on the item you can initiate a <emphasis><property>full build</property></emphasis> on an archive, <emphasis><property>edit</property>,</emphasis><emphasis><property>delete</property></emphasis> or <emphasis><property>publish</property></emphasis> it. + </para> - <figure> - <title>Context Menu on the Item</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start_8.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Context Menu on the Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_8.png"/> + </imageobject> + </mediaobject> + </figure> - <para>If you wish, you can assign a hotkey for the Build Project Archive action. A key binding can be added - by navigating to <emphasis> - <property>Window > Preferences > General > Keys</property>.</emphasis></para> + <para> + If you wish, you can assign a hotkey for the Build Project Archive action. A key binding can be added by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>General</guimenuitem><guimenuitem>Keys</guimenuitem></menuchoice>. + </para> - <figure> - <title>Setting the Hotkey for Build Project Archive Action</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/hotkeys.png" scale="80"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Setting the Hotkey for Build Project Archive Action</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/hotkeys.png" scale="80"/> + </imageobject> + </mediaobject> + </figure> - <para>To perform the building of the project archives, select the project in the <property>Package Explorer</property> view and execute the hotkey combination - you assigned for this action.</para> + <para> + To build a project archive, select the project in the <guilabel>Package Explorer</guilabel> view and execute the hotkey combination + you assigned for this action. + </para> - <para>Learn more about the <property>Project Archives</property> view - <link linkend="Project_archivesView">here</link>.</para> - </section> - - <section id="deployment"> - <title>Deploying an Application to a Server</title> + <para>More information about the <guilabel>Project Archives</guilabel> view can be found in <xref linkend="Project_archivesView"/>.</para> + </section> - <para>There are two times to deploy your application:</para> - <itemizedlist> - <listitem> - <para>While creating it</para> - </listitem> - <listitem> - <para>After it already exists</para> - </listitem> - </itemizedlist> + <section id="deployment"> + <title>Deploying an Application to a Server</title> - <para>When you create a new project (Seam, JSF or Struts) with the New Project or Import Project - wizards, the one of wizards steps has a <emphasis> - <property>Target Runtime</property> - </emphasis> and <emphasis> - <property>Target Server</property> - </emphasis> sections. You can deploy the application through the appropriate selection in - these sections.</para> + <para>There are two times to deploy your application:</para> + <itemizedlist> + <listitem> + <para>While creating it</para> + </listitem> + <listitem> + <para>After it already exists</para> + </listitem> + </itemizedlist> - <figure> - <title>Runtime and Server Sections in the New Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start_4a.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + When you create a new project (Seam, JSF or Struts) with the New Project or Import Project wizards, they will include the <guilabel>Target Runtime</guilabel> and <guilabel>Target Server</guilabel> sections. You can deploy the application through the appropriate configuration in these sections. + </para> - <figure> - <title>Runtime and Server Sections in the Import Project Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start_4b.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Runtime and Server Sections in the New Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_4a.png"/> + </imageobject> + </mediaobject> + </figure> - <para>You can deploy an existing application to a server by right-clicking the target defined - server in the <property>Servers</property> view and then selecting <emphasis><property>Add and - Remove Projects</property></emphasis> from the context menu.</para> + <figure> + <title>Runtime and Server Sections in the Import Project Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_4b.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Add and Remove Projects From the Context Menu.</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start_5.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + You can deploy an existing application to a server by right-clicking the target defined server in the <guilabel>Servers</guilabel> view and then selecting <guimenuitem>Add and Remove Projects</guimenuitem> from the context menu. + </para> - <para>If this application is not assigned to a server, it will be in the left-hand available - projects list. Clicking on the <property>Add ></property> button will add it to the right-hand - configured projects list and deploy the application to this server.</para> + <figure> + <title>Add and Remove Projects From the Context Menu.</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_5.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Modifying The Projects that are Configured on the Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/quick_start/quick_start_6.png"/> - </imageobject> - </mediaobject> - </figure> - </section> + <para> + If this application is not assigned to a server, it will be in the left-hand available projects list. Clicking on the <guibutton>Add ></guibutton> button will add it to the right-hand configured projects list and deploy the application to this server. + </para> + + <figure> + <title>Modifying The Projects that are Configured on the Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/quick_start/quick_start_6.png"/> + </imageobject> + </mediaobject> + </figure> + </section> <section id="publishing"> <title>Publishing to JBoss Server</title> <para>The publishing of all the modules added to a Server is performed automatically when starting a Server.</para> - <para>The automatic publish of the changes made to the workspace is turned on by default in order to permanently keep - the workspace in sync with the publish folder. If you need to control when to publish the changes, - just disable the automatic publish in the <link linkend="server_editor">Server Editor</link> and use the <emphasis> - <property>Publish to Server</property></emphasis> (<inlinemediaobject> - <imageobject> - <imagedata fileref="images/quick_start/publish_button.png"/> - </imageobject> - </inlinemediaobject>) button which initiates an incremental publish. + <para> + Automatically publishing changes made to the workspace is enabled by default, allowing the workspace to remain in sync with the publish folder. If you need to control when to publish the changes, just disable the automatic publish in the Server Editor (see <xref linkend="server_editor"/>) and use the <guibutton>Publish to Server</guibutton> (<inlinemediaobject><imageobject><imagedata fileref="images/quick_start/publish_button.png"/></imageobject></inlinemediaobject>) button which will incrementally publish the workspace. </para> - <para>Here, we have just performed the basic steps you should know to quick start with JBoss - server. In fact, there are more functionalities which you can make use of. Further we will - talk about them in detail.</para> + <para> + This section has provided some basic information that will allow you to use the common features provided by the JBoss server. However, JBoss server includes a great deal more functionality, which will be discussed in subsequent chapters. + </para> </section> - <section> - <title>Other relevant resources on the topic</title> + <section> + <title>Other relevant resources on the topic</title> - <para>All JBoss Developer Studio/JBoss Tools documentation you can find <ulink - url="http://docs.jboss.org/tools/2.1.0.GA">on JBoss Tools release documentation page</ulink>.</para> - <para>The latest documentation builds are available <ulink - url="http://download.jboss.org/jbosstools/nightly-docs/"> JBoss Tools nightly builds documentation page</ulink>.</para> - - <para>Find out the answers on the frequently asked questions about JBoss AS 5 usage in the - <ulink url="http://community.jboss.org/wiki/JBossAS5FAQ">JBossAS5FAQ</ulink>. + <para> + All JBoss Developer Studio/JBoss Tools documentation can be found on the <ulink url="http://docs.jboss.org/tools/2.1.0.GA">on JBoss Tools release documentation page</ulink>. + </para> + <para> + The latest documentation builds are available from the <ulink url="http://download.jboss.org/jbosstools/nightly-docs/"> JBoss Tools nightly builds documentation page</ulink>. + </para> + + <para> + Find answers to frequently asked questions about JBoss AS 5 usage in the <ulink url="http://community.jboss.org/wiki/JBossAS5FAQ">JBossAS5FAQ</ulink>. </para> - <para>The information on how to monitor a remote JBoss Server from Eclipse you can find in the following - <ulink url="http://www.jboss.org/community/wiki/MonitorARemoteJbossServerFromEclipse">wiki article</ulink>.</para> - </section> + <para> + Information on how to monitor a remote JBoss Server from Eclipse can be found in this <ulink url="http://www.jboss.org/community/wiki/MonitorARemoteJbossServerFromEclipse">wiki article</ulink>.</para> + </section> </chapter> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/runtimes_servers.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/runtimes_servers.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/runtimes_servers.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -1,405 +1,372 @@ <?xml version="1.0" encoding="UTF-8"?> -<chapter id="runtimes_servers" xreflabel="runtimes_servers"> - <?dbhtml filename="runtimes_servers.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Developer Studio</keyword> - <keyword>Eclipse</keyword> - <keyword>Deploy</keyword> - <keyword>Deployment</keyword> - <keyword>JBoss</keyword> - </keywordset> - </chapterinfo> - <title>Runtimes and Servers in the JBoss AS plugin</title> - - <para>In this chapter we will discuss how to install runtimes and servers.</para> - - <para>First of all it is necessary to mention that the JBoss AS plugin makes use of WTP. - This includes starting and stopping servers in run or debug mode. It also includes targeting WTP - projects, such as Dynamic Web Projects, to certain server runtimes in order to ensure that the - proper jars from a specific server are added to the project's classpath - properly.</para> - <para>In order to get started creating, running, and debugging J2EE applications, we should create - our <property>runtime</property> and <property>server</property> instances.</para> - - <section> - <title>Runtimes</title> - <para>In <property>JBoss Tools</property>, the main purpose of Server Runtimes is to point to a - server installation somewhere on disk. In our case, this will be a JBoss installation, and it - can then be used for two primary purposes:</para> - <itemizedlist> - <listitem> - <para>it provides classpath additions to WTP projects that require them.</para> - </listitem> - <listitem> - <para>for <property>JBoss server</property> at least, it provides information necessary for - the starting and stopping of the server, it tells which jars to run and which - configuration to use.</para> - </listitem> - </itemizedlist> - <section id="InstNewRuntime"> - <title>Installing a new runtime</title> - <para>You can install runtimes into eclipse from the <emphasis> - <property>Window > Preferences </property> - </emphasis> menu, and then select <emphasis> - <property>Server > Runtime Environments</property> - </emphasis> from the categories available on the left.</para> - <figure> - <title>Installed Runtimes</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_1.png"/> - </imageobject> - </mediaobject> - </figure> - <para>From this preference page you can see all declared runtimes and their types as well. - Here, it's possible to edit or remove existing runtimes as well as add a new - one.</para> - - <para>To create a JBoss runtime click <emphasis> - <property>Add</property> - </emphasis> button and choose a necessary type of runtime from the <emphasis> - <property>JBoss Community</property> - </emphasis> category.</para> - - <figure> - <title>Adding a Runtime</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_2.png"/> - </imageobject> - </mediaobject> - </figure> - - <note> - <title>Note:</title> - - <para>Now there is a separation between .org servers (the <emphasis> - <property>JBoss Community</property> - </emphasis> category) and product server that comes with JBoss EAP in JBDS ( the <emphasis> - <property>JBoss Enterprise Middleware</property> - </emphasis> category).</para> - </note> - - <para>As you can see, <property>JBoss Tools</property> provide its own adapters such as JBoss - 3.2, 4.0, 4.2 and 5.0 as well. The last one comes with its own new feature, that is a safer - incremental deployment, which prevents partial deployments to be picked up by the server. It - means that scanning for auto-deployment is suspended while files are being copied to the - deployment location and resumed when the copy is completed.</para> - - <note> - <title>Note:</title> - <para>Currently we recommend you to use a fully supported JBoss 5.0 server adapter.</para> - </note> - - <para>You'll also note a Deploy-Only Runtime type. This type provides no classpath - for WTP projects. It is used solely by its server type for the purpose of setting up a - deploy directory for users who don't wish to make use of starting, stopping, or - debugging their projects inside eclipse.</para> - - <figure id="add_runtime_figure"> - <title>Adding a JBoss 5.0 Runtime</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_3.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>The following table describes all the available options of the currant wizard - page.</para> - <table> - <title>Server Runtime Wizard Parameters</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - - <thead> - <row> - <entry align="center"> - <para>Name</para> - </entry> - - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> - - <tbody> - <row> - <entry> - <para>Name</para> - </entry> - <entry> - <para>The name of a new Runtime for a chosen server. We suggest that you - don't leave a default value. It's better to give descriptive - names that will help to distinguish one runtime from another.</para> - </entry> - </row> - - <row> - <entry> - <para>Home directory</para> - </entry> - <entry> - <para>The path to a directory where the runtime is installed.</para> - </entry> - </row> - - <row> - <entry> - <para>JRE</para> - </entry> - <entry> - <para>The proper Java Runtime Environment. Because of the open-source nature of - JBoss, a user is likely to want to modify and repackage some of the - configuration-specific jboss jars and create their own configuration. Thus, rather - than forcing you to copy his entire JBoss installation, the structure of the - wizard allows to create only a new configuration instead.</para> - </entry> - </row> - - <row> - <entry> - <para>Directory</para> - </entry> - <entry> - <para>The path to a directory where the configurations are installed.</para> - </entry> - </row> - <row> - <entry> - <para>Configuration</para> - </entry> - <entry> - <para>The list of configurations (all, default, minimal) that is updated as soon as - you browse to a valid runtime installation folder.</para> - </entry> - </row> - - </tbody> - </tgroup> - </table> - - <para>As a result of having each runtime represent a specific configuration rather than the - server installation as a whole, it is very likely you'll create several different - runtimes to test each of your configurations. It becomes important to ensure your runtimes, - and later your servers, are given descriptive names that help you to remember which is - which.</para> - - <para>Press <emphasis> - <property>Finish</property> - </emphasis> to see your new runtime in the list.</para> - <note> - <title>Note:</title> - <para>If you edit the configuration of a runtime, the changes don't affect the settings of the servers that currently use the runtime. - To apply the changes to them also,you should double right click the server, <emphasis> - <property>Overview>Runtime Environment</property> </emphasis> - ,make sure that necessary configuration is chosen,click <emphasis><property>Finish</property> </emphasis> and then <emphasis><property>Save</property></emphasis> button.</para> - </note> - </section> - <section id="Detecting_an_existing_runtime"> - <title>Detecting an existing runtime</title> - <para> - JBoss Tools features the ability to search, detect and add existing JBoss server runtimes installed on your system. If you don't have an existing runtime <xref linkend="InstNewRuntime"/> will guide you through the creation process. To begin searching for your existing JBoss runtime navigate to <menuchoice> - <guimenuitem>Window</guimenuitem> - <guimenuitem>Preferences</guimenuitem> - <guimenuitem>JBoss Tools</guimenuitem> - <guimenuitem>JBoss Runtimes</guimenuitem> - </menuchoice>. +<chapter id="runtimes_servers"> + <?dbhtml filename="runtimes_servers.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Developer Studio</keyword> + <keyword>Eclipse</keyword> + <keyword>Deploy</keyword> + <keyword>Deployment</keyword> + <keyword>JBoss</keyword> + </keywordset> + </chapterinfo> + <title>Runtimes and Servers in the JBoss AS plugin</title> + + <para>In this chapter we will discuss how to install runtimes and servers.</para> + + <para> + First of all it is necessary to mention that the JBoss AS plugin makes use of WTP. This includes starting and stopping servers in run or debug mode. It also includes targeting WTP projects, such as Dynamic Web Projects, to certain server runtimes in order to ensure that the proper JARs from a specific server are added to the project's classpath properly. + </para> + <para> + In order to get started creating, running and debugging J2EE applications, we should create our <property>runtime</property> and <property>server</property> instances. + </para> + + <section> + <title>Runtimes</title> + <para> + In <property>JBoss Tools</property>, the main purpose of Server Runtimes is to point to a server installation somewhere on disk. In our case, this will be a JBoss installation. It can then be used for two primary purposes: + </para> + <itemizedlist> + <listitem> + <para>Providing classpath additions to WTP projects that require them.</para> + </listitem> + <listitem> + <para> + For <property>JBoss server</property> at least, it provides the necessary information to allow the server to be started and stopped and provides information on which JARs to run and which configuration to use. + </para> + </listitem> + </itemizedlist> + <section id="InstNewRuntime"> + <title>Installing a new runtime</title> + <para> + You can install runtimes into Eclipse by selecting <menuchoice><guimenuitem>Window</guimenuitem> + <guimenuitem>Preferences</guimenuitem> + </menuchoice> menu and then selecting <menuchoice><guimenuitem>Server</guimenuitem> + <guimenuitem>Runtime Environments</guimenuitem> + </menuchoice> from the categories available on the left. + </para> + <figure> + <title>Installed Runtimes</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + From this preference page you can see all declared runtimes along with their types. Here, it is possible to edit or remove existing runtimes, as well as add a new one. + </para> + + <para> + To create a JBoss runtime click the <guibutton>Add</guibutton> button and choose the appropriate type of runtime from the <guilabel>JBoss Community</guilabel> category. + </para> + + <figure> + <title>Adding a Runtime</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_2.png"/> + </imageobject> + </mediaobject> + </figure> + + <note> + <title>Note:</title> + + <para> + Now there is a separation between .org servers (the <guilabel>JBoss Community</guilabel> category) and product server that comes with JBoss EAP in JBDS ( the <guilabel>JBoss Enterprise Middleware</guilabel> category). + </para> + </note> + + <para> + As you can see, <productname>JBoss Tools</productname> provide its own adapters such as JBoss 3.2, 4.0, 4.2 and 5.0 as well. The last one comes a new safer incremental deployment feature, which prevents partial deployments to be picked up by the server. It means that scanning for auto-deployment is suspended while files are being copied to the deployment location and resumed when the copy is completed. + </para> + + <note> + <title>Note:</title> + <para>Currently we recommend you to use a fully supported JBoss 5.0 server adapter.</para> + </note> + + <para> + You will also note a Deploy-Only Runtime type. This type does not provide a classpath for WTP projects. It is used solely by it's server type for the purpose of setting up a deploy directory for users who do not wish to make use of starting, stopping, or debugging their projects inside Eclipse. + </para> + + <figure id="add_runtime_figure"> + <title>Adding a JBoss 5.0 Runtime</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_3.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>The following table describes all the available options of the current wizard page.</para> + <table> + <title>Server Runtime Wizard Parameters</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> + + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + + <tbody> + <row> + <entry> + <para>Name</para> + </entry> + <entry> + <para> + The name of a new Runtime for a chosen server. We suggest that you do not leave the default value for this field. It is better to give descriptive names that will help to distinguish one runtime from another. + </para> + </entry> + </row> + + <row> + <entry> + <para>Home directory</para> + </entry> + <entry> + <para>The path to a directory where the runtime is installed.</para> + </entry> + </row> + + <row> + <entry> + <para>JRE</para> + </entry> + <entry> + <para> + The proper Java Runtime Environment. Because of the open-source nature of JBoss, a user is likely to want to modify and repackage some of the configuration-specific JBoss JARs and create their own configuration. So rather than forcing you to copy your entire JBoss installation, the structure of the wizard allows to create a new configuration instead. + </para> + </entry> + </row> + + <row> + <entry> + <para>Directory</para> + </entry> + <entry> + <para>The path to a directory where the configurations are installed.</para> + </entry> + </row> + <row> + <entry> + <para>Configuration</para> + </entry> + <entry> + <para>The list of configurations (all, default, minimal), which is updated as soon as you browse to a valid runtime installation folder.</para> + </entry> + </row> + + </tbody> + </tgroup> + </table> + + <para> + As a result of having each runtime represent a specific configuration rather than the server installation as a whole, it is very likely you will create several different runtimes to test each of your configurations. So it becomes important to ensure your runtimes and later your servers, are given descriptive names that help you to remember which is which. + </para> + + <para>Click the <guibutton>Finish</guibutton> button to see your new runtime in the list.</para> + <note> + <title>Note:</title> + <para> + If you edit the configuration of a runtime, the changes don't affect the settings of the servers that currently use the runtime. To apply the changes to them also, you should double left click on the server, select <menuchoice><guimenuitem>Overview</guimenuitem> + <guimenuitem>Runtime Environment</guimenuitem> + </menuchoice>, make sure that necessary configuration is chosen, click the <guibutton>Finish</guibutton> button and then <guibutton>Save</guibutton> button. + </para> + </note> + </section> + <section id="Detecting_an_existing_runtime"> + <title>Detecting an existing runtime</title> + <para> + JBoss Tools features the ability to search, detect and add existing JBoss server runtimes installed on your system. If you don't have an existing runtime <xref linkend="InstNewRuntime"/> will guide you through the creation process. To begin searching for your existing JBoss runtime select <menuchoice><guimenuitem>Window</guimenuitem> + <guimenuitem>Preferences</guimenuitem> + <guimenuitem>JBoss Tools</guimenuitem> + <guimenuitem>JBoss Runtimes</guimenuitem> + </menuchoice>. </para> - <figure> - <title>Preference page for JBoss Runtimes</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers-detecting_new_runtime_1.png"/> - </imageobject> - </mediaobject> - </figure> - <para> + <figure> + <title>Preference page for JBoss Runtimes</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers-detecting_new_runtime_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para> The JBoss Runtimes preference page allows you to perform three different actions: <guibutton>Search</guibutton> for a JBoss runtime installation, <guibutton>Export</guibutton> a JBoss runtime configuration and <guibutton>Import</guibutton> the configuration of a JBoss runtime. </para> - <para> - The <guibutton>Search</guibutton> button opens a file system browser window. Select a directory where you wish JBoss Tools to begin recursively searching for JBoss runtimes and upon completion it will return all those found. From the returned list, choose the runtimes you wish to make available to your JBoss Tools instance by clicking the box beside each runtime and clicking the <guibutton>OK</guibutton> button. + <para> + The <guibutton>Search</guibutton> button opens a file system browser window. Select the directory where you wish JBoss Tools to begin recursively searching for JBoss runtimes and upon completion it will return all those found. From the returned list, choose the runtimes you wish to make available to your JBoss Tools instance by clicking the box beside each runtime and clicking the <guibutton>OK</guibutton> button. </para> - <figure> - <title>JBoss Runtime search results</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers-detecting_new_runtime_2.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section id="Exporting_and_Importing_runtime_preferences"> - <title>Exporting and Importing runtime preferences</title> - <para> - The <guimenuitem>JBoss Runtimes</guimenuitem> <guilabel>Preferences</guilabel> interface seen in <xref linkend="Detecting_an_existing_runtime"/> also allows you to export and import your runtime preferences. You can navigate to the page through <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>JBoss Tools</guimenuitem><guimenuitem>JBoss Runtimes</guimenuitem></menuchoice>. + <figure> + <title>JBoss Runtime search results</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers-detecting_new_runtime_2.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="Exporting_and_Importing_runtime_preferences"> + <title>Exporting and Importing runtime preferences</title> + <para> + The <guimenuitem>JBoss Runtimes</guimenuitem> + <guilabel>Preferences</guilabel> interface seen in <xref linkend="Detecting_an_existing_runtime"/> also allows you to export and import your runtime preferences. You can navigate to the page by selecting <menuchoice><guimenuitem>Window</guimenuitem> + <guimenuitem>Preferences</guimenuitem> + <guimenuitem>JBoss Tools</guimenuitem> + <guimenuitem>JBoss Runtimes</guimenuitem> + </menuchoice>. </para> - <para> - The <guibutton>Export</guibutton> button opens the <guilabel>Export Preferences</guilabel> dialog. The <guilabel>Export all</guilabel> box will automatically be selected, however you can choose to only export specific preference settings (such as only those related to your JBoss runtime) by selecting individual entries from the displayed list. + <para> + The <guibutton>Export</guibutton> button opens the <guilabel>Export Preferences</guilabel> dialog. The <guilabel>Export all</guilabel> box will automatically be selected, however you can choose to only export specific preference settings (such as only those related to your JBoss runtime) by selecting individual entries from the displayed list. </para> - <figure> - <title>Export Preferences dialog</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers-export_runtime_1.png"/> - </imageobject> - </mediaobject> - </figure> - <para> - To export the preference settings you must specify a preference file that the information will be written to. This file, once exported, can be used to reapply your settings by clicking on the <guilabel>Import</guilabel> button. + <figure> + <title>Export Preferences dialog</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers-export_runtime_1.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + To export the preference settings you must specify the preference file that the information will be written to. This file, once exported, can be used to reapply your settings by clicking on the <guilabel>Import</guilabel> button. </para> - <para> - The <guibutton>Import</guibutton> button opens the <guilabel>Import Preferences</guilabel> dialog. The <guilabel>Import all</guilabel> box will automatically be selected, however you can choose to only import specific preference settings (such as only those related to your JBoss runtime) by selecting individual entries from the list that displays after using the <guibutton>Browse</guibutton> button to select your exported preference file (for example: preference_file.epf). + <para> + The <guibutton>Import</guibutton> button opens the <guilabel>Import Preferences</guilabel> dialog. The <guilabel>Import all</guilabel> box will automatically be selected, however you can choose to only import specific preference settings (such as only those related to your JBoss runtime) by selecting individual entries from the list that displays after using the <guibutton>Browse</guibutton> button to select your exported preference file (for example: preference_file.epf). </para> - <figure> - <title>Import Preferences dialog</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers-import_runtime_1.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section id="CopyRuntime"> - <title>Duplicating a runtime configuration</title> - <para>While installing a new runtime you can copy the configuration from the existing one. - To do this you should perform all the steps in the <link linkend="InstNewRuntime">previous</link> section except pressing <emphasis> - <property>Finish</property></emphasis> - in the New Server Runtime Environment menu . + <figure> + <title>Import Preferences dialog</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers-import_runtime_1.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="CopyRuntime"> + <title>Duplicating a runtime configuration</title> + <para> + While installing a new runtime you can copy the configuration from the existing one. To do this you should perform all the steps in <xref linkend="InstNewRuntime"/>, with the exception of clicking the <guibutton>Finish</guibutton> button in the New Server Runtime Environment menu. </para> - <para>Make sure that you browse to a valid runtime folder and can see the list of configurations (all, default, minimal) in the Configuration section . - Then choose necessary Configuration from the list and click <emphasis> - <property>Copy</property></emphasis>.The next dialog should appear. + <para> + Make sure that you browse to a valid runtime folder and can see the list of configurations (all, default, minimal) in the Configuration section. Then choose appropriate Configuration from the list and click the <guibutton>Copy</guibutton> button.The next dialog should appear. </para> - <figure> - <title>Copy the existing configuration</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_4a.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Change the name Click on <emphasis> - <property>Browse</property></emphasis> and select your configuration location or leave as it's if you want it to be located together with other runtime configurations. + <figure> + <title>Copy the existing configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_4a.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + Change the name, click the <guibutton>Browse</guibutton> button and select your configuration location or leave as it is if you want it to be located together with other runtime configurations. </para> - <figure> - <title>Copy the existing configuration</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_4b.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Click<emphasis> - <property> Ok </property></emphasis>and you should see the next wizard with the just added copied configuration. - + <figure> + <title>Copy the existing configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_4b.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Click the <guibutton>OK</guibutton> button and you should see the next wizard with the newly copied configuration.</para> + <figure> + <title>Runtime with copied configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_4c.png"/> + </imageobject> + </mediaobject> + </figure> + <para> Click the <guibutton>Finish</guibutton> button and you will see your new runtime in the list. </para> - <figure> - <title>Runtime with copied configuration</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_4c.png"/> - </imageobject> - </mediaobject> - </figure> - <para> Press <emphasis> - <property>Finish</property> - </emphasis> and you will see your new runtime in the list. + <para> + You can also change the configuration of existing runtime to a copied one in the same way by selecting <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem><guimenuitem>Server</guimenuitem><guimenuitem>Runtime Environments</guimenuitem></menuchoice> and clicking the <guibutton>Edit</guibutton> button. </para> - <para>You can also change a configuration of existing runtime to a copied one in the same way from the <emphasis> - <property> Window > Preferences </property></emphasis> - menu <emphasis> - <property>Server > Runtime Environments </property></emphasis> - and clicking <emphasis> - <property>Edit</property></emphasis>. - </para> - </section> - </section> - <section> - <title>Servers</title> - <para>WTP servers are eclipse-representations of a backing server installation. They are used to - start or stop servers, deploy to servers, or debug code that will run on the server. They keep - track of the modules (jars, wars, etc) you deploy to the server and also allow you to undeploy - those modules (see <link linkend="run_on_server_wizard">Deploying with Run On Server - Wizard</link> section). </para> - <para>Servers can be started or stopped with different <link linkend="com_line_arg">command-line - arguments</link>. They are often backed by a runtime object representing that server's - location.</para> + </section> + </section> + <section> + <title>Servers</title> + <para> + WTP servers are Eclipse-representations of a back end server installation. They are used to start or stop servers, deploy to servers, or debug code that will run on the server. They keep track of the modules (JARs, WARs, etc) you deploy to the server and also allow you to undeploy those modules (see <xref linkend="run_on_server_wizard"/>). + </para> + <para> + Servers can be started or stopped with different <link linkend="com_line_arg">command-line arguments</link>. They are often backed by a runtime object representing that server's location. + </para> + + <section> + <title>Creating a New Server</title> + + <para> + There are many ways to get to the new server wizard. One way is to select <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other...</guimenuitem><guimenuitem>Server</guimenuitem></menuchoice>. This should show the wizard like below. + </para> + <figure> + <title>Adding a JBoss Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_4.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + A server object keeps track of things like command line arguments when starting or stopping and the runtimes keep track of the location of the installation. Thus, each server instance must be backed by an appropriate runtime. + </para> + + <para> + The <guilabel>New server wizard</guilabel> allows you to name the server via the <guilabel>Server name</guilabel> field, or you can use a generated default name .If it is necessary to restore the default name, click the <guibutton>Reset default</guibutton> button (<inlinemediaobject> <imageobject><imagedata fileref="images/runtimes_servers/runtimes_servers_4d.png"/></imageobject></inlinemediaobject>). + </para> + <para> + You can select the appropriate runtime from the <guilabel>Server runtime environment</guilabel> combo box. If there is no runtime that matches your needs just press the <guilabel>Add...</guilabel> link nearby to bring up the wizard for creating a new runtime (see <xref linkend="add_runtime_figure"/>). To configure an existing runtimes you should go to server preferences by pressing the <guilabel>Configure runtime environments...</guilabel> link. + </para> + + <para>If the server you want to create does not have any installed runtime yet, the combobox and the links are absent.</para> + + <figure> + <title>Installed Server Runtime Environments</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_6.png"/> + </imageobject> + </mediaobject> + </figure> + + <para> + In this case the next page of the wizard which has the same form as in <link linkend="add_runtime_figure">the previous section</link> and will ask you to create the associated runtime. + </para> + <para> + Either way, after targeting your server to a runtime, the final screen in this wizard presents a summary of the selected options, giving you a chance to verify that you have selected the appropriate runtime. + </para> + + <figure> + <title>Installed Server Runtime Environments</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/runtimes_servers/runtimes_servers_7.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Click the <guibutton>Finish</guibutton> button to complete the process of the server creation.</para> + <para>Now that we have created our runtimes and servers, we can explore the services and tools provided by the JBoss Server Manager.</para> + + <para> + We hope this guide helped you to get started with the JBoss Tools server manager. For additional information you are welcome on <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>. + </para> + </section> + </section> - <section> - <title>Creating a New Server</title> - <para>There are many ways to get to the new server wizard. One way is to use the old standard <emphasis> - <property>File > New > Other... </property> - </emphasis> and then <emphasis> - <property>Server</property> - </emphasis>. This should show the wizard like below.</para> - <figure> - <title>Adding a JBoss Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_4.png"/> - </imageobject> - </mediaobject> - </figure> - <para>A server object is that keeps track of things like command line arguments when starting - or stopping, and runtimes keep track of the location of the installation. Thus, each server - instance must be backed by an appropriate runtime. </para> - - <para> <emphasis><property> New server wizard </property></emphasis> allows to name the server appropriately in the <emphasis><property>Server name field </property></emphasis >or you can use a generated default name.If it's nessecary to restore the default name,after you defined yours, click the Reset default button(<inlinemediaobject> <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_4d.png"/> - </imageobject></inlinemediaobject>). - From the list of already declared runtimes in the combo box below the view it's - possible to select which runtime you want your server to be backed by. If there is no - runtime that matches your needs just press the <emphasis> - <property>Add...</property> - </emphasis> link nearby to bring up the wizard for creating a new runtime (see the <link - linkend="add_runtime_figure">Installing a New Runtime section</link>). To configure the already installed - runtimes you should go to server preferences that you can easily do by pressing the <emphasis> - <property>Configure runtime environments...</property></emphasis> link.</para> - - <para>If the server you want to create doesn't have any installed runtime yet, the combo box - and the links are absent.</para> - - <figure> - <title>Installed Server Runtime Environments</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_6.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>In this case the next page in the wizard which has the same form as in <link - linkend="add_runtime_figure">the previous section</link> will ask you to create the - associated runtime.</para> - <para>Either way, after targeting your server to a runtime, the final screen in this wizard is - largely confirmational, giving you a chance to verify that you've selected the - appropriate runtime. </para> - - <figure> - <title>Installed Server Runtime Environments</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/runtimes_servers/runtimes_servers_7.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Press <emphasis> - <property>Finish</property> - </emphasis> to complete the process of the server creation.</para> - <para>Now that we've created our runtimes and servers, we can dwell on all services - and tools that JBoss Server Manager provides.</para> - - <para>We hope, this guide helped you to get started with the JBoss Tools server manager. Besides, for additional information you are welcome on <ulink - url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss forum</ulink>.</para> - </section> - </section> - - </chapter> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/tptp_support.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/tptp_support.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/tptp_support.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -1,69 +1,59 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="tptp_support"> - <title>TPTP Support</title> - <para>This chapter provides an overview on how to enable TPTP Profiling for <property>JBoss - AS</property> adapters in <property>JBoss Tools</property>.</para> + <title>TPTP Support</title> + <para> + This chapter provides an overview on how to enable TPTP Profiling for <productname>JBoss AS</productname> adapters in <productname>JBoss Tools</productname>. + </para> - <section> - <title>TPTP Profiling</title> + <section> + <title>TPTP Profiling</title> - <para>To get TPTP profiling work on <property>JBoss Application Server</property> you should - do the following:</para> - - <itemizedlist> - <listitem><para>Download <ulink - url="http://www.eclipse.org/tptp/home/downloads/" - >TPTP Runtime</ulink> and install it, i. e. just add the content of <emphasis> - <code>plugins/features</code> - </emphasis> folders from downloaded directory to the same folders in your eclipse - installation directory or use the <emphasis><property>Help > Install New Software</property></emphasis> - command.</para> - </listitem> - <listitem><para>Install <property>JBoss TPTP Tools</property> - which provide TPTP support for JBoss AS servers (find the latest stable version of the JBoss TPTP profile feature at - <ulink url="http://www.jboss.org/tools/download/stable">http://www.jboss.org/tools/download/stable</ulink>).</para></listitem> - </itemizedlist> + <para>To get TPTP profiling work on <productname>JBoss Application Server</productname> you should do the following:</para> - <para>And now all profile actions should work for you. To start <property>JBoss - AS</property> in profiling mode use <emphasis> - <property>Start the server in profiling mode</property> - </emphasis> button or <emphasis> - <property>Profile As > Profile on Server</property> - </emphasis> option in the context menu of the project.</para> + <itemizedlist> + <listitem> + <para> + Download <ulink url="http://www.eclipse.org/tptp/home/downloads/">TPTP Runtime</ulink> and install it, i. e. just add the content of <emphasis><code>plugins/features</code></emphasis> folders from downloaded directory to the same folders in your eclipse installation directory or use the <menuchoice><guimenuitem>Help</guimenuitem><guimenuitem>Install New Software</guimenuitem></menuchoice> command. + </para> + </listitem> + <listitem> + <para> + Install <property>JBoss TPTP Tools</property> which provide TPTP support for JBoss AS servers (find the latest stable version of the JBoss TPTP profile feature at <ulink url="http://www.jboss.org/tools/download/stable">http://www.jboss.org/tools/download/stable</ulink>). + </para> + </listitem> + </itemizedlist> - <figure> - <title>Start the Server in Profiling mode</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/tptp_support/tptp_support_1.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + And now all profile actions should work for you. To start <productname>JBoss AS</productname> in profiling mode use <guibutton>Start the server in profiling mode</guibutton> button or select <menuchoice><guimenuitem>Profile As</guimenuitem><guimenuitem>Profile on Server</guimenuitem></menuchoice> from the context menu of the project. + </para> - <para>To enable TPTP features in your workbench use <property>Profiling and Logging - Perspective</property> that you can find in the list of proposed perspectives: <emphasis> - <property>Window > Open Perspective > Other…</property> - </emphasis> - </para> + <figure> + <title>Start the Server in Profiling mode</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/tptp_support/tptp_support_1.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Profiling and Logging Perspective</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/tptp_support/tptp_support_2.png"/> - </imageobject> - </mediaobject> - </figure> - </section> + <para> + To enable TPTP features in your workbench use <property>Profiling and Logging Perspective</property> that you can find in the list of proposed perspectives: <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Open Perspective</guimenuitem><guimenuitem>Other...</guimenuitem></menuchoice> + </para> - <section> - <title>Relevant Resources Links</title> - <para>All additional information on TPTP(Test and Performance Tools Platform) you can find - in <ulink - url="http://www.eclipse.org/tptp/home/downloads/4.5.0/documents/quicktour/quic..." - >eclipse documentation</ulink>.</para> - <para>In summary, this reference should help you to start with <ulink - url="http://www.jboss.org/jbossas">JBoss AS</ulink> and get to know with functionality - for work with it.</para> - </section> + <figure> + <title>Profiling and Logging Perspective</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/tptp_support/tptp_support_2.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + + <section> + <title>Relevant Resources Links</title> + <para> + All additional information on TPTP (Test and Performance Tools Platform) can be found in the <ulink url="http://www.eclipse.org/tptp/home/downloads/4.5.0/documents/quicktour/quic...">Eclipse documentation</ulink>. + </para> + </section> </chapter> Modified: branches/jbosstools-3.2.x/as/docs/reference/en-US/webtools.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/en-US/webtools.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/en-US/webtools.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -1,48 +1,36 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="webtools"> <title>Projects</title> - <para>The most popular of the projects we deal with are the J2EE ones, such as Dynamic Web - Project, EJB Project, or EAR project. Web projects of <property>JBoss Tools</property> are - Struts, JSF and Seam projects. All of them are called faceted projects. Thus, in this - chapter we are going to tell you about facets the main benefit of which to provide proper - structuring and packaging for any type of project.</para> - + <para> + The most popular of the projects we deal with are the J2EE ones, such as Dynamic Web Project, EJB Project, or EAR project. <productname>JBoss Tools</productname> web projects include Struts, JSF and Seam projects. These are referred to as faceted projects. This chapter will cover facets, which are used to provide a consistent structure and packaging features to any type of project. + </para> + <section> <title>Faceted Projects Overview</title> - <para>The idea behind faceted projects is that each project can accept units of - functionality, or facets, which can be added or removed by the user. Most often, these - facets either add to the project's classpath, enable a builder, or watch the project in - some other fashion. Generally, every project concerned has at least one facet when - it's created. As an example, a Web project has a WebDoclet facet, or an EJB - Project has an EJB Module facet as prerequisites.</para> - - <para> WTP projects have undergone some criticism as being - <emphasis>over-engineered</emphasis> or too restrictive in their design. WTP projects - are set up in a tree-relationship to each other, where one project can be a child of - another. For example, an EAR project may have a Web Project child, an EJB project child, - or other types.</para> - - <para> However, the benefit of this is that the structure of your projects is then known, - and packaging it up *should* be trivial. Apparently, if your project is non-standard, or - you feel too confined by such rigid structural requirements, you can still choose to - package your project using the <link linkend="Project_archivesView">Archives - plugin</link>.</para> + <para> + The idea behind faceted projects is that each project can accept units of functionality, or facets, which can be added or removed by the user. These facets either add to the project's classpath, enable a builder, or watch the project in some other fashion. Typically every project concerned has at least one facet when it is created. As an example, a Web project has a WebDoclet facet, or an EJB Project has an EJB Module facet as prerequisites. + </para> + + <para> + WTP projects have been criticized for being over-engineered or too restrictive in their design. WTP projects are set up in a tree-relationship to each other, where one project can be a child of another. For example, an EAR project may have a Web Project child, an EJB project child, or other types. + </para> + + <para> + However, the benefit of this is that the structure of your projects is then known and packaging it up <emphasis>should</emphasis> be trivial. If your project is non-standard, or you feel too confined by such rigid structural requirements, you can still choose to package your project using the Archives plugin (see <xref linkend="Project_archivesView"/>). + </para> </section> - + <section> <title>Adding Facets to a Project</title> - - <para>In this section we're going to consider the facets added by <property>JBoss - Tools</property> and show how you can configure them in a project: add new ones or - modify already existing configuration of the facets.</para> - - <para>One way to configure the facets is doing it while organizing a new project. To - demonstrate this let's create a new <property>Dynamic Web Project</property> by - selecting <emphasis> - <property>File > New > Other...</property> - </emphasis> and then <emphasis> - <property>Web > Dynamic Web Project</property>. </emphasis></para> + + <para> + This section will cover the facets added by <property>JBoss Tools</property> and show how you can configure them in a project by adding new ones or modifying existing facet configurations. + </para> + + <para> + One way to configure the facets is doing it while organizing a new project. To demonstrate this let's create a new <guilabel>Dynamic Web Project</guilabel> by selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other...</guimenuitem><guimenuitem>Web</guimenuitem><guimenuitem>Dynamic Web Project</guimenuitem></menuchoice>. + </para> <figure> <title>New Dynamic Web Project</title> <mediaobject> @@ -51,17 +39,15 @@ </imageobject> </mediaobject> </figure> - <para>Click <emphasis> - <property>Next</property> - </emphasis> and you will see Dynamic Web Project page like on the figure below.</para> - - <para> The first page of most WTP projects allows you to target a specific runtime, - representing a server's library location. It will also provide you the ability to add - this project to an EAR project, and select a preselected default set of facets, called - a configuration, rather than manually select each facet you might want.</para> - <para> Selecting the runtime, again, allows the project to install the proper classpaths to - the project so it knows what code to compile against.</para> - + <para>Click the <guibutton>Next</guibutton> button and you will see a Dynamic Web Project page like on the figure below.</para> + + <para> + The first page of most WTP projects allows you to target a specific runtime, which represents a server's library location. It will also provide you the ability to add this project to an EAR project and select a preselected default set of facets, called a configuration, rather than manually select each required facet. + </para> + <para> + Selecting the runtime allows the project to install the proper classpaths to the project so it knows what code to compile against. + </para> + <figure id="dyn_web_project"> <title>New Dynamic Web Project</title> <mediaobject> @@ -70,12 +56,10 @@ </imageobject> </mediaobject> </figure> - <para>Click on the <emphasis> - <property>Modify</property> - </emphasis> button next to <property>Configuration</property> section in order to open - the wizard which allows you to modify a chosen configuration. The wizard looks as - follows.</para> - + <para> + Click the <guibutton>Modify</guibutton> button next to the <guilabel>Configuration</guilabel> section to open a wizard which allows you to modify the chosen configuration. The wizard is shown in the image below. + </para> + <figure id="project_facets"> <title>Project Facets Wizard</title> <mediaobject> @@ -84,9 +68,8 @@ </imageobject> </mediaobject> </figure> - - <para>Here part of the listed facets are those which are provided by WTP. Some of them are - added by <property>JBoss Tools</property>. They are:</para> + + <para>Here part of the listed facets are those which are provided by WTP. Some of them are added by <property>JBoss Tools</property>. They are:</para> <itemizedlist> <listitem> <para>BIRT Charting Runtime Component</para> @@ -107,11 +90,10 @@ <para>Seam</para> </listitem> </itemizedlist> - - <para>On this wizard page you can enable or disable any facet as well as change it version. - What you should note here is that some facets or facets versions may conflict with each - other. In case of incompatibility you'll be prompted about this in the combo - box underneath.</para> + + <para> + On this wizard page you can enable or disable any facet as well as change its version. What you should note here is that some facets or facets versions may conflict with each other. In case of incompatibility you will be notified in the combobox underneath. + </para> <figure> <title>Facet Constraints</title> <mediaobject> @@ -120,9 +102,7 @@ </imageobject> </mediaobject> </figure> - <para>When switching on the <emphasis> - <property>Runtimes</property> - </emphasis> tab on the right you'll see the current server Runtime.</para> + <para>When switching on the <guilabel>Runtimes</guilabel> tab on the right you will see the current server Runtime.</para> <figure> <title>Runtimes on the Project Facets Wizard</title> <mediaobject> @@ -131,33 +111,27 @@ </imageobject> </mediaobject> </figure> - <para>On this tab you can also create a new Server Runtime and make it primary by pressing <emphasis> - <property>Make Primary</property> - </emphasis> button after enabling it.</para> + <para> + On this tab you can also create a new Server Runtime and make it primary by enabling it and then clicking the <guibutton>Make Primary</guibutton> button. + </para> + + <para> + Clicking on the <guibutton>OK</guibutton> button will save the chosen configuration of the facets and return you to the Dynamic Web Project wizard (see <xref linkend="dyn_web_project"/>). Additional pages in the wizard are specific to either the project type or the facets selected. + </para> - <para>Clicking on <emphasis> - <property>OK</property> - </emphasis> will save the chosen configuration of the facets and return you to the <link - linkend="dyn_web_project">Dynamic Web Project wizard</link>. Further pages in the - wizard are specific to either the project type or the facets selected.</para> - - - <para>If you need to configure the facets for the existing project, you should bring up the - context menu for selected project and click <emphasis> - <property>Properties</property> - </emphasis> and then <emphasis> - <property>Project Facets</property>. </emphasis> This will bring up the familiar - <link linkend="project_facets">Project Facets wizard</link>, where you can create - your own custom facets configuration.</para> - + + <para> + If you need to configure the facets for an existing project, right click on the project, select <guimenuitem>Properties</guimenuitem> and then select <guilabel>Project Facets</guilabel>. This will bring up the Project Facets wizard (see <xref linkend="project_facets"/>), where you can create your own custom facets configuration. + </para> + <para/> - + </section> <section id="rel_resources_links"> <title>Relevant Resources Links</title> - - <para>More on the WTP facets you can read in the <ulink - url="http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.jst.j2ee.do..." - >eclipse help</ulink>.</para> + + <para> + More information on the WTP facets can be found in the <ulink url="http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclipse.jst.j2ee.do...">Eclipse help</ulink>. + </para> </section> </chapter> Modified: branches/jbosstools-3.2.x/as/docs/reference/pom.xml =================================================================== --- branches/jbosstools-3.2.x/as/docs/reference/pom.xml 2011-07-18 02:02:34 UTC (rev 32976) +++ branches/jbosstools-3.2.x/as/docs/reference/pom.xml 2011-07-18 02:06:02 UTC (rev 32977) @@ -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>AS_Reference_Guide</docname> - <bookname>AS Reference Guide</bookname> - </properties> - - <profiles> + <properties> + <translation>en-US</translation> + <docname>AS_Reference_Guide</docname> + <bookname>AS Reference Guide</bookname> + </properties> + <profiles> +  - <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>  - <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>  - <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>  - <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>  - <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>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>

14 years, 9 months

1
0
0 / 0

JBoss Tools SVN: r32976 - in branches/jbosstools-3.2.x/portlet/docs/reference: en-US and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2011-07-17 22:02:34 -0400 (Sun, 17 Jul 2011) New Revision: 32976 Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Book_Info.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Feedback.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/JBoss_Portlet_Tools_User_Guide.ent branches/jbosstools-3.2.x/portlet/docs/reference/en-US/JBoss_Portlet_Tools_User_Guide.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Preface.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Revision_History.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/intro.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/jsf_portlet.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/master.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/reference.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/seam_portlet.xml branches/jbosstools-3.2.x/portlet/docs/reference/en-US/starting_project.xml branches/jbosstools-3.2.x/portlet/docs/reference/pom.xml Log: updated for GA Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Book_Info.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Book_Info.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Book_Info.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -5,9 +5,9 @@ <title>JBoss Portlet Tools User Guide</title> <subtitle>Provides information relating to the JBoss Portlet Tools set.</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 JBoss Portlet Tools User Guide explains how to begin with and manage JBoss Portlet Tools.</para> </abstract> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Feedback.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Feedback.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Feedback.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -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=12310500&issu...">https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...</ulink> - </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> +  <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/portlet/docs/reference/en-US/JBoss_Portlet_Tools_User_Guide.ent =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/JBoss_Portlet_Tools_User_Guide.ent 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/JBoss_Portlet_Tools_User_Guide.ent 2011-07-18 02:02:34 UTC (rev 32976) @@ -1,4 +1,7 @@ <!ENTITY PRODUCT "JBoss"> <!ENTITY BOOKID "JBoss_Portlet_Tools_Reference_Guide"> -<!ENTITY YEAR "2010"> +<!ENTITY YEAR "2011"> <!ENTITY HOLDER "Red Hat"> +<!ENTITY BZPRODUCT "JBoss Developer Studio"> +<!ENTITY BZCOMPONENT "Portlet Tools User Guide"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Develope...'>http://bugzilla.redhat.com/</ulink>"> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/JBoss_Portlet_Tools_User_Guide.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/JBoss_Portlet_Tools_User_Guide.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/JBoss_Portlet_Tools_User_Guide.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -8,5 +8,6 @@ <xi:include href="portlet_tools_tasks.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="reference.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="summary.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/portlet/docs/reference/en-US/Preface.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Preface.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Preface.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -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.html">Red Hat Documentation</ulink> website under the <guilabel>JBoss Developer Studio</guilabel> section. </para> -  </preface> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Revision_History.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Revision_History.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/Revision_History.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -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</surname><email>irooskov(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>General updates</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>0</revnumber><date>Fri Nov 20 2009</date> - <author> - <firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>Initial creation of book by publican</member> - </simplelist> - </revdescription> - </revision> - </revhistory> - </simpara> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>2</revnumber> + <date>Tue Jan 18 2011</date> + <author> + <firstname>JBoss Tools</firstname> + <surname>Documentation Team</surname> + <email>mcaspers(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>General updates</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>1</revnumber> + <date>Wed Jun 09 2010</date> + <author> + <firstname>JBoss Tools</firstname> + <surname>Documentation Team</surname> + <email>irooskov(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>General updates</member> + </simplelist> + </revdescription> + </revision> + <revision> + <revnumber>0</revnumber> + <date>Fri Nov 20 2009</date> + <author> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + <email>irooskov(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>Initial creation of book by publican</member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </simpara> </appendix> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/intro.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/intro.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/intro.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -1,96 +1,94 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="intro"> - <?dbhtml filename="intro.html"?> - <title>Introduction</title> + <?dbhtml filename="intro.html"?> + <title>Introduction</title> + + <para> + Starting from 3.0.0.Alpha1 version, the JBoss set of plugins includes tools for supporting <property>JBoss Portal</property> and JSR-186/JSR-286 portlets. Thus, this guide provides instructions on how to get started and manage <property>JBoss Portlet Tools</property>. + </para> + <section> + <title>What JBoss Portal and Portlet Tools are</title> + <para> + <property>JBoss Portal</property> provides an open source platform for hosting and serving a portal's Web interface, publishing and managing its content, and customizing its experience. It supports a wide range of features, including standard portlets, single sign-on, clustering, and internationalization. More about <property>JBoss Portal</property> can be found by visiting its home page at: <ulink url="http://www.jboss.org/jbossportal/">http://www.jboss.org/jbossportal/</ulink>. + </para> + + <para> + With <property>JBoss Portlet Tools</property> you can easily create a Java, JSF and Seam portlet and deploy it to <property>JBoss Portal</property>. + </para> + </section> - <para>Starting from 3.0.0.Alpha1 version, JBoss set of plugins includes tools for supporting <property>JBoss Portal</property> and JSR-186/JSR-286 portlets. - Thus, this guide is intended to explain you how to get started and manage <property>JBoss Portlet Tools</property>.</para> -<section> - <title>What is JBoss Portal and Portlet Tools?</title> - <para><property>JBoss Portal</property> provides an open source platform for hosting and - serving a portal's Web interface, publishing and managing its content, and customizing - its experience. It supports a wide range of features, including standard portlets, - single sign-on, clustering, and internationalization. More about <property>JBoss Portal</property> you can find visiting - its home page at: <ulink url="http://www.jboss.org/jbossportal/">http://www.jboss.org/jbossportal/</ulink>.</para> + <section id="key_features"> + <title>Key Features of JBoss Portlet Tools</title> + <para> + <property>JBoss Portlet Tools</property> supports the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification (Portlet 1.0)</ulink> and <ulink url="http://www.jcp.org/en/jsr/detail?id=286">JSR-286 Portlet Specification (Portlet 2.0)</ulink> and works with <ulink url="http://www.jboss.org/portletbridge/">JBoss Portlet Bridge</ulink> for supporting Portlets in JSF/Seam applications. To enable these features, you need to add the JBoss Portlet facet to a new or an existing web project (see <xref linkend="portlet_tools_tasks"/>). The project could be a non-WTP project, but you should know that if it does not have the proper portlet API JAR's, the generated classes will have compile errors. + </para> - <para>With <property>JBoss Portlet Tools</property> you can easily create a Java, JSF and Seam portlet and deploy it to <property>JBoss Portal</property>.</para> - </section> + <para>The next table lists key features supplied by <property>JBoss Portlet Tools</property>.</para> - <section id="key_features"> - <title>Key Features of JBoss Portlet Tools</title> - <para><property>JBoss Portlet Tools</property> supports the <ulink url="http://www.jcp.org/en/jsr/detail?id=168">JSR-168 Portlet Specification (Portlet 1.0)</ulink> and - <ulink url="http://www.jcp.org/en/jsr/detail?id=286">JSR-286 Portlet Specification (Portlet 2.0)</ulink> and works with - <ulink url="http://www.jboss.org/portletbridge/">JBoss Portlet Bridge</ulink> for supporting Portlets - in JSF/Seam applications. To enable these features, you need to add the JBoss Portlet facet to a new or an existing web project - (see <xref linkend="portlet_tools_tasks"/>). The project could be a non-WTP project, but you should know that - if it does not have the proper portlet API jar's the generated classes will have compile errors.</para> - - <para>The next table lists key features supplied by <property>JBoss Portlet Tools</property>.</para> + <table> + <title>Key Features of JBoss Portlet Tools</title> + <tgroup cols="3"> - <table> - <title>Key Features of JBoss Portlet Tools</title> - <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="5*"/> + <colspec colnum="3" align="left" colwidth="1*"/> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="5*"/> - <colspec colnum="3" align="left" colwidth="1*"/> + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + <entry>Chapter</entry> + </row> + </thead> - <thead> - <row> - <entry>Feature</entry> - <entry>Benefit</entry> - <entry>Chapter</entry> - </row> - </thead> + <tbody> - <tbody> + <row> + <entry> + <para>JBoss Portlet facets</para> + </entry> + <entry> + <para> + <property>JBoss Portlet Tools</property> provides the Java, JSF and Seam Portlet facets that could be enabled for a Web project.</para> + </entry> + <entry> + <xref linkend="portlet_tools_tasks"/> + </entry> + </row> - <row> - <entry> - <para>JBoss Portlet facets</para> - </entry> - <entry> - <para><property>JBoss Portlet Tools</property> provides the Java, JSF and Seam Portlet facets that could be enabled for a Web project.</para> - </entry> - <entry> - <xref linkend="portlet_tools_tasks"/> - </entry> - </row> + <row> + <entry> + <para>Java Portlet wizard</para> + </entry> - <row> - <entry> - <para>Java Portlet wizard</para> - </entry> + <entry> + <para>The wizard helps create a JSR-186/JSR-286 compliant portlets</para> + </entry> + <entry> + <xref linkend="java_portlet_wizard"/> + </entry> + </row> - <entry> - <para>The wizard helps create a JSR-186/JSR-286 compliant - portlets</para> - </entry> - <entry> - <xref linkend="java_portlet_wizard"/> - </entry> - </row> - - <row> - <entry> - <para>JSF/Seam Portlet wizard</para> - </entry> - <entry> - <para>This wizard helps create JSF/Seam portlets</para> - </entry> - <entry> - <xref linkend="jsf_seam_portlet_wizard"/> - </entry> - </row> - </tbody> - </tgroup> - </table> - </section> + <row> + <entry> + <para>JSF/Seam Portlet wizard</para> + </entry> + <entry> + <para>This wizard helps create JSF/Seam portlets</para> + </entry> + <entry> + <xref linkend="jsf_seam_portlet_wizard"/> + </entry> + </row> + </tbody> + </tgroup> + </table> + </section> <section id="requirements_installation"> <title>Requirements and Installation</title> - <para><property>JBoss - Portlet Tools</property> needs the following minimal requirements:</para> + <para> + <property>JBoss Portlet Tools</property> needs the following minimum requirements:</para> <itemizedlist> <listitem> @@ -100,24 +98,55 @@ <para>JBoss Tools 3.0.0.Alpha1 (for higher versions of JBoss Tools make sure you use the <ulink url="http://www.jboss.org/community/wiki/Matrixofsupportedplatformsruntimesand...">compatible version of Eclipse</ulink>)</para> </listitem> - <listitem><para>JDK 5 or higher</para></listitem> <listitem> - <para>JBoss Portal + JBoss AS bundle from: <ulink - url="http://www.jboss.org/jbossportal/download/index.html">http://www.jboss.org/jbossportal/download/index.html</ulink></para> - <note> - <title>Note:</title> - <para>JBoss Portlet Tools has been tested using 2.6.5 and 2.7.0.ALPHA - versions of <property>JBoss Portal</property>. Remember, if you want to use Portlet - version 2.0 (JSR-268), you have to choose JBoss Portal 2.7.</para> - </note> + <para>JDK 5 or higher</para> </listitem> <listitem> - <para>JBoss Portlet Bridge (optionally) from: <ulink url="http://www.jboss.org/portletbridge/downloads.html">http://www.jboss.org/portletbridge/downloads.html</ulink></para> + <para> + One of the following technologies: + </para> + <itemizedlist> + <listitem> + <para> + JBoss Enterprise Portal Platform version 4.3 or 5.1 + </para> + </listitem> + <listitem> + <para> + GateIn and JBoss Application Server + </para> + </listitem> + <listitem> + <para> + JBoss Portal and JBoss Application Server + </para> + <para> + A specific JBoss Portal and JBoss Application Server bundle is available from: <ulink url="http://www.jboss.org/jbossportal/download/index.html">http://www.jboss.org/jbossportal/download/index.html</ulink> + </para> + <note> + <title>Note:</title> + <para> + JBoss Portlet Tools has been tested using 2.6.5 and 2.7.0.ALPHA versions of <property>JBoss Portal</property>. Remember, if you want to use Portlet version 2.0 (JSR-268), you have to choose JBoss Portal 2.7. + </para> + </note> + </listitem> + </itemizedlist> </listitem> + <listitem> + <para>JBoss Portlet Bridge (optionally) from: <ulink url="http://www.jboss.org/portletbridge/downloads.html">http://www.jboss.org/portletbridge/downloads.html</ulink> + </para> + </listitem> </itemizedlist> - - <para><property>JBoss Portlet Tools</property> is included as part of <property>JBoss Tools</property> project. + + <para> + <property>JBoss Portlet Tools</property> is included as part of the <property>JBoss Tools</property> project. Refer to <ulink url="http://www.jboss.org/tools/download/installation.html">http://www.jboss.org/tools/download/installation.html</ulink> - for installation methods of <property>JBoss Tools</property>.</para> -</section> + for <property>JBoss Tools</property> installation instructions. + </para> + <note> + <para> + This guide will only refer to JBoss Portal from here, however you can use (and it is recommended to use) JBoss Enterprise Portal Platform or GateIn instead, as mentioned above. + </para> + </note> + </section> </chapter> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/jsf_portlet.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/jsf_portlet.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/jsf_portlet.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -2,256 +2,250 @@ <section id="jsf_portlet"> <title>Creating and Deploying a JSF Portlet</title> - <para>This chapter will explain how you can configure a JSF portlet within a JSF project with JBoss Portlet capabilities - and then deploy it to <property>JBoss Portal</property>.</para> + <para> + This chapter will explain how you can configure a JSF portlet within a JSF project with JBoss Portlet capabilities and then deploy it to <property>JBoss Portal</property>. + </para> - <section id="jsf_portlet1"> - <title>Creating a JSF Project with JBoss Portlet Capabilities</title> - - <para>You can create a JSF project with JBoss Portlet capabilities in two ways:</para> + <section id="jsf_portlet1"> + <title>Creating a JSF Project with JBoss Portlet Capabilities</title> + + <para>You can create a JSF project with JBoss Portlet capabilities in two ways:</para> - <orderedlist> - <listitem> - <para>Create a dynamic Web project with the <emphasis><property>JavaServer Faces</property></emphasis> - and <emphasis><property>JBoss JSF Portlet</property></emphasis> facets enabled (see - <xref linkend="create_dyn_web_proj_jsf"/>)</para> - </listitem> - <listitem><para>Or create a JSF project using the wizard JBoss JSF Tools provides, then enable - JSF and JBoss Portlet facets and add JBoss Portlet capabilities (see - <xref linkend="create_jsf_proj"/>)</para></listitem> - </orderedlist> + <orderedlist> + <listitem> + <para> + Create a dynamic Web project with the <emphasis><property>JavaServer Faces</property></emphasis> and <emphasis><property>JBoss JSF Portlet</property></emphasis> facets enabled (see <xref linkend="create_dyn_web_proj_jsf"/>) + </para> + </listitem> + <listitem> + <para> + Or create a JSF project using the wizard provided by JBoss JSF Tools, then enable JSF and JBoss Portlet facets and add JBoss Portlet capabilities (see + <xref linkend="create_jsf_proj"/>) + </para> + </listitem> + </orderedlist> - <para>Refer to the further sections for the procedures on how to do this.</para> + <para>Refer to the further sections for the procedures on how to do this.</para> - <section id="create_dyn_web_proj_jsf"> - <title>Creating a Dynamic Web Project with the JBoss Portlet Capabilities</title> + <section id="create_dyn_web_proj_jsf"> + <title>Creating a Dynamic Web Project with the JBoss Portlet Capabilities</title> - <para>The basic steps to create a dynamic Web project with the JBoss Portlet capabilities are as follows:</para> + <para>The basic steps to create a dynamic Web project with the JBoss Portlet capabilities are as follows:</para> - <orderedlist> - <listitem> - <para>Start the <emphasis><property>Dynamic Web Project</property></emphasis> wizard navigating to - <emphasis><property>File > New > Other > Web > Dynamic Web Project</property>.</emphasis></para> + <orderedlist> + <listitem> + <para> + Start the <emphasis><property>Dynamic Web Project</property></emphasis> wizard navigating to <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>Web</guimenuitem><guimenuitem>Dynamic Web Project</guimenuitem></menuchoice>. + </para> - <note> - <title>Tip:</title> - <para>You can also select the <property>Java EE</property> perspective and then go to - <emphasis><property>File > New > Dynamic Web Project</property>.</emphasis></para> - </note> + <note> + <title>Tip:</title> + <para> + You can also select the <property>Java EE</property> perspective and then selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Dynamic Web Project</guimenuitem></menuchoice>. + </para> + </note> - <figure> - <title>Setting the JSF Configuration</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet1.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>Setting the JSF Configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet1.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>Specify the project name and set the target runtime to <property>JBoss Portal</property> by following the points 3, 4 and 5 in the - <xref linkend="jboss_core_portlet"/> procedure.</para> - </listitem> + <listitem> + <para>Specify the project name and set the target runtime to <property>JBoss Portal</property> by following the points 3, 4 and 5 in the <xref linkend="jboss_core_portlet"/> procedure.</para> + </listitem> - <listitem> - <para>In the <emphasis><property>Configuration</property></emphasis> - area, click <emphasis><property>Modify</property></emphasis> and enable <emphasis><property>JavaServer Faces</property>,</emphasis> - <emphasis><property>JBoss Core Portlet</property></emphasis> and <emphasis><property>JBoss JSF Portlet</property></emphasis> facets. - Hit <emphasis><property>OK</property>.</emphasis></para> + <listitem> + <para>In the <emphasis><property>Configuration</property></emphasis>area, click the <guibutton>Modify</guibutton> button and enable <emphasis><property>JavaServer Faces</property>,</emphasis><emphasis><property>JBoss Core Portlet</property></emphasis> and <emphasis><property>JBoss JSF Portlet</property></emphasis> facets. Click the <guibutton>OK</guibutton> button. + </para> - <figure> - <title>Enabling the Portlet Facets</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet2.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>Enabling the Portlet Facets</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>You may leave the next two wizard pages with defaults, just press <emphasis><property>Next</property></emphasis> to proceed.</para> - </listitem> + <listitem> + <para>You may leave the next two wizard pages with their defaults, just press the <guibutton>Next</guibutton> button to proceed.</para> + </listitem> - <listitem> - <para>On the <property>JBoss Portlet Capabilities</property> page, select <emphasis> - <property>Portlet Target Runtime Provider</property></emphasis> and click <emphasis><property>Next</property>.</emphasis></para> + <listitem> + <para>On the <property>JBoss Portlet Capabilities</property> page, select <emphasis><property>Portlet Target Runtime Provider</property></emphasis> and click the <guibutton>Next</guibutton> button. + </para> - <figure> - <title>JBoss Portlet Capabilities</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet2a.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>JBoss Portlet Capabilities</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet2a.png"/> + </imageobject> + </mediaobject> + </figure> - <note> - <title>Tip:</title> - <para>All types of the portlet implementation library are described more closely in the wiki article at: + <note> + <title>Tip:</title> + <para>All types of the portlet implementation library are described more closely in the wiki article at: <ulink url="http://www.jboss.org/community/wiki/PortletFacetLibraries">http://www.jboss.org/community/wiki/PortletFacetLibraries</ulink>.</para> - </note> - </listitem> + </note> + </listitem> - <listitem> - <para>Next wizard page is for configuring JSF capabilities. You can leave everything as it - is here.</para> + <listitem> + <para>Next wizard page is for configuring JSF capabilities. You can leave everything as it is here.</para> - <figure> - <title>JSF Capabilities</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet3.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>JSF Capabilities</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet3.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>On the <property>JBoss JSF Portlet Capabilities</property> page, select - <emphasis><property>JSF Portlet Target Runtime Provider</property></emphasis> as the JSF portlet implementation library. It will - copy Portlet Bridge libraries from the server runtime to the project classpath.</para> + <listitem> + <para> + On the <property>JBoss JSF Portlet Capabilities</property> page, select <emphasis><property>JSF Portlet Target Runtime Provider</property></emphasis> as the JSF portlet implementation library. It will copy Portlet Bridge libraries from the server runtime to the project classpath. + </para> - <figure> - <title>JBoss JSF PortletCapabilities</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet4.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>JBoss JSF PortletCapabilities</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet4.png"/> + </imageobject> + </mediaobject> + </figure> - <note> - <title>Tip:</title> - <para>On this page, it is also possible to add the RichFaces libraries from the RichFaces distribution by checking - <emphasis><property>Add/Change Richfaces Libraries</property>.</emphasis></para> - </note> + <note> + <title>Tip:</title> + <para>On this page, it is also possible to add the RichFaces libraries from the RichFaces distribution by checking<emphasis><property>Add/Change Richfaces Libraries</property>.</emphasis> + </para> + </note> - <note> - <title>Note:</title> - <para>You can select the <emphasis><property>JSF Portletbridge Runtime Provider</property></emphasis> type. Then it - is necessary to set the home of the Portlet Bridge distribution.</para> - <para>For information about all the JSF Portlet facet library providers, refer to the wiki article at: - <ulink url="http://community.jboss.org/wiki/PortletFacetLibraries">http://community.jboss.org/wiki/PortletFacetLibraries</ulink>.</para> - </note> - </listitem> + <note> + <title>Note:</title> + <para> + You can select the <emphasis><property>JSF Portletbridge Runtime Provider</property></emphasis> type. Then it is necessary to set the home of the Portlet Bridge distribution. + </para> + <para> + For information about all the JSF Portlet facet library providers, refer to the wiki article at: <ulink url="http://community.jboss.org/wiki/PortletFacetLibraries">http://community.jboss.org/wiki/PortletFacetLibraries</ulink>. + </para> + </note> + </listitem> - <listitem> - <para>Click <emphasis><property>Finish</property>.</emphasis> The project will be created in the workbench.</para> - </listitem> - </orderedlist> - </section> + <listitem> + <para>Click the <guibutton>Finish</guibutton> button. The project will be created in the workbench.</para> + </listitem> + </orderedlist> + </section> - <section id="create_jsf_proj"> - <title>Creating a JSF Project and adding the JBoss Portlet Capabilities</title> + <section id="create_jsf_proj"> + <title>Creating a JSF Project and adding the JBoss Portlet Capabilities</title> - <para>How to organize a JSF project you can find out in the JSF Tools User Guide. Just - remember to point the target runtime to <property>JBoss Portal</property> directory location (see - how it is done for a dynamic Web project: steps 3, 4 and 5 in the - <xref linkend="jboss_core_portlet"/> procedure).</para> + <para> + For information on how to organize a JSF project you can read the JSF Tools User Guide. Just remember to point the target runtime to <property>JBoss Portal</property> directory location (see how it is done for a dynamic Web project with steps 3, 4 and 5 in the <xref linkend="jboss_core_portlet"/> procedure). + </para> - <figure> - <title>Creating New JSF Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet8.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Creating New JSF Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet8.png"/> + </imageobject> + </mediaobject> + </figure> - <para>To add the JBoss Portlet capabilities to the created JSF project you should complete the next steps:</para> - - <orderedlist> - <listitem> - <para>Right-click the project and click <emphasis> - <property>Properties</property> - </emphasis> to open the project <property>Properties</property> sheet. Select <property>Project Facets</property> - on the left and enable the <emphasis><property>JavaServer Faces</property>,</emphasis> - <emphasis><property>JBoss Core Portlet</property></emphasis> and <emphasis><property>JBoss JSF Portlet</property></emphasis> facets.</para> + <para>To add the JBoss Portlet capabilities to the JSF project you should complete the next steps:</para> + + <orderedlist> + <listitem> + <para>Right-click the project and click <guimenuitem>Properties</guimenuitem> to open the project <property>Properties</property> sheet. Select <property>Project Facets</property> on the left and enable the <emphasis><property>JavaServer Faces</property>, </emphasis><emphasis><property>JBoss Core Portlet</property></emphasis> and <emphasis><property>JBoss JSF Portlet</property></emphasis> facets.</para> - <figure> - <title>Project Facets</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet9.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>Project Facets</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet9.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>Notice, <emphasis> - <property>"Further configuration available..."</property> - </emphasis> warning appears at the bottom of the screen. It means that next you should configure the JSF Portlet capabilities in the project. - Click the link. The <property>Modify Faceted Project</property> wizard appears.</para> - </listitem> + <listitem> + <para>Notice that the <emphasis><property>"Further configuration available..."</property></emphasis> warning appears at the bottom of the screen. It means that next you should configure the JSF Portlet capabilities in the project. Click the link. The <property>Modify Faceted Project</property> wizard appears.</para> + </listitem> - <listitem> - <para>Complete all wizard pages the same way as described in the steps 5, 6, 7 of the - <xref linkend="jboss_core_portlet"/> procedure. - Hit <emphasis><property>OK</property>.</emphasis></para> - </listitem> + <listitem> + <para>Complete all wizard pages the same way as described in the steps 5, 6, 7 of the <xref linkend="jboss_core_portlet"/> procedure. Click the <guibutton>OK</guibutton> button. + </para> + </listitem> - <listitem> - <para>To apply the changes click <emphasis><property>Apply</property></emphasis> and then - <emphasis><property>OK</property></emphasis> to close the project <property>Properties</property> sheet.</para> - </listitem> - </orderedlist> - </section> - </section> + <listitem> + <para> + To apply the changes click the <guibutton>Apply</guibutton> button and then the <guibutton>OK</guibutton> button to close the project <property>Properties</property> sheet. + </para> + </listitem> + </orderedlist> + </section> + </section> - <section id="jsf_portlet_to_JSF_project"> - <title>Adding a JSF Portlet to the Project and Deploying It to JBoss Portal</title> - - <para>The previous section has shown how to create a JSF project with JBoss Portlet and JSF Portlet capabilities enabled. Use - the following procedure to add a JSF portlet to the created project and deploy it to <property>JBoss Portal</property>.</para> + <section id="jsf_portlet_to_JSF_project"> + <title>Adding a JSF Portlet to the Project and Deploying It to JBoss Portal</title> + + <para> + The previous section demonstrated how to create a JSF project with JBoss Portlet and JSF Portlet capabilities enabled. Use the following procedure to add a JSF portlet to the created project and deploy it to <property>JBoss Portal</property>. + </para> - <orderedlist> - <listitem> - <para>Call the - <property>Create Portlet</property> wizard by navigating to <emphasis> - <property>New > Other > JBoss Tools Web > Portlet > JSF/Seam - Portlet</property></emphasis> on the context menu of the project (for information about the wizard options, see - <xref linkend="jsf_seam_portlet_wizard"/> in the guide reference).</para> + <orderedlist> + <listitem> + <para>Display the <property>Create Portlet</property> wizard by selecting <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>JBoss Tools Web</guimenuitem><guimenuitem>Portlet</guimenuitem><guimenuitem>JSF/Seam Portlet</guimenuitem></menuchoice> from the context menu of the project (for information about the wizard options, see <xref linkend="jsf_seam_portlet_wizard"/> in the guide reference).</para> - <figure> - <title>Calling New Portlet Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet5.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Calling New Portlet Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet5.png"/> + </imageobject> + </mediaobject> + </figure> - <note> - <title>Tip:</title> - <para>As you see, the JSF and Seam Portlet wizards are merged into one. We have set the JSF + <note> + <title>Tip:</title> + <para>As you see, the JSF and Seam Portlet wizards are merged into one. We have set the JSF configuration for the project, so the default values in this wizard will be set as for a JSF portlet.</para> - </note> - </listitem> + </note> + </listitem> - <listitem> - <para>Leave all the wizard pages with default values by clicking the <emphasis><property>Next</property></emphasis> button, - on the last one click <emphasis><property>Finish</property></emphasis> to complete the JSF portlet creation.</para> - </listitem> + <listitem> + <para> + Leave all the wizard pages with default values by clicking the <guibutton>Next</guibutton> button, on the last one click the <guibutton>Finish</guibutton> button to complete the JSF portlet creation. + </para> + </listitem> - <listitem> - <para>Complete the steps described in the <xref linkend="deploying_to_portal"/> procedure to - deploy a JSF portlet to <property>JBoss Portal</property>. Just use the other URL to see it in the browser: - <emphasis>http://localhost:8080/portal/portal/default/JSFPortlet</emphasis>.</para> + <listitem> + <para> + Complete the steps described in the <xref linkend="deploying_to_portal"/> procedure to deploy a JSF portlet to <property>JBoss Portal</property>. Just use the other URL to see it in the browser: <emphasis>http://localhost:8080/portal/portal/default/JSFPortlet</emphasis>. + </para> - <figure> - <title>JSF Portlet in the Browser</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet7.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </orderedlist> + <figure> + <title>JSF Portlet in the Browser</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet7.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </orderedlist> - </section> + </section> </section> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/master.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/master.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/master.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -53,12 +53,12 @@ Version: 1.1.1.GA </releaseinfo> -<abstract> + </bookinfo> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/reference.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/reference.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/reference.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -648,11 +648,7 @@ <section id="preferences"> <title>JBoss Portlet Preferences</title> - <para>To open <property>JBoss Portlet Preferences</property> property sheet, go to <emphasis> - <property>Window > Preferences</property> - </emphasis> and then <emphasis> - <property>JBoss Tools > JBoss Portlet</property>. - </emphasis></para> + <para>To open <property>JBoss Portlet Preferences</property> property sheet, go to <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Preferences</guimenuitem></menuchoice> and then <menuchoice><guimenuitem>JBoss Tools</guimenuitem><guimenuitem>JBoss Portlet.</guimenuitem></menuchoice></para> <figure> <title>JBoss Runtime Preferences</title> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/seam_portlet.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/seam_portlet.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/seam_portlet.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -2,219 +2,218 @@ <section id="seam_portlet"> <title>Creating and Deploying a Seam Portlet</title> - <para>This chapter covers the steps on how to configure a Seam portlet within a Seam - project with the help of the <property>JBoss Portlet Tools</property> features.</para> - - <section id="seam_portlet1"> - <title>Creating a Seam Project with JBoss Portlet Capabilities</title> + <para> + This chapter covers the steps required to configure a Seam portlet within a Seam project with the help of the <property>JBoss Portlet Tools</property> features. + </para> - <para>Follow one of two ways of creating a Seam project with JBoss Portlet capabilities enabled:</para> - <orderedlist> - <listitem> - <para>Create a dynamic Web project with the <emphasis><property>Seam</property></emphasis> - and <emphasis><property>JBoss Portlets</property></emphasis> facets enabled (see <xref linkend="create_dyn_web_proj_seam"/>)</para> - </listitem> - <listitem><para>Or create a Seam project with the JBoss Seam portlet configuration using the wizard JBoss Seam Tools provides - and follow all the wizard steps to enable JBoss Portlet capabilities (see <xref linkend="create_seam_proj"/>)</para></listitem> - </orderedlist> + <section id="seam_portlet1"> + <title>Creating a Seam Project with JBoss Portlet Capabilities</title> + + <para>One of the following two procedures can be used to create a Seam project with JBoss Portlet capabilities enabled:</para> + <orderedlist> + <listitem> + <para> + Create a dynamic Web project with the <emphasis><property>Seam</property></emphasis> and <emphasis><property>JBoss Portlets</property></emphasis> facets enabled (see <xref linkend="create_dyn_web_proj_seam"/>) + </para> + </listitem> + <listitem> + <para> + Create a Seam project with the JBoss Seam portlet configuration using the wizard JBoss Seam Tools provides and follow all the wizard steps to enable JBoss Portlet capabilities (see <xref linkend="create_seam_proj"/>) + </para> + </listitem> + </orderedlist> - <section id="create_dyn_web_proj_seam"> - <title>Creating a Dynamic Web Project with Seam and JBoss Portlet Capabilities</title> + <section id="create_dyn_web_proj_seam"> + <title>Creating a Dynamic Web Project with Seam and JBoss Portlet Capabilities</title> - <para>To create a dynamic Web project with Seam and JBoss Portlet capabilities you should take the following steps:</para> + <para>To create a dynamic Web project with Seam and JBoss Portlet capabilities you should complete the following steps:</para> - <orderedlist> - <listitem> - <para>In the <emphasis><property>File</property></emphasis> menu, go to - <emphasis><property>New > Other > Web > Dynamic Web Project</property>.</emphasis> The <property>New Dynamic Web Project</property> - wizard starts.</para> + <orderedlist> + <listitem> + <para> Select. <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>Web</guimenuitem><guimenuitem>Dynamic Web Project</guimenuitem></menuchoice>. The <property>New Dynamic Web Project</property> wizard will then be displayed.</para> - <figure> - <title>Creating a New Dynamic Web Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/seam_portlet/seam_portlet1.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>Creating a New Dynamic Web Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_portlet/seam_portlet1.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>Give the project a name and follow the steps 3, 4, 5 of the - <xref linkend="jboss_core_portlet"/> procedure to set the target runtime.</para> - </listitem> + <listitem> + <para>Give the project a name and follow the steps 3, 4, 5 of the <xref linkend="jboss_core_portlet"/> procedure to set the target runtime.</para> + </listitem> - <listitem> - <para>In the <emphasis><property>Configuration</property></emphasis> area of the first wizard page, - select <emphasis> - <property>JBoss Seam Portlet Project v2.0</property>.</emphasis> It will add needed facets to the project.</para> + <listitem> + <para> + In the <emphasis><property>Configuration</property></emphasis> area of the first wizard page, select <emphasis><property>JBoss Seam Portlet Project v2.0</property>.</emphasis> It will add needed facets to the project. + </para> - <note> - <title>Tip:</title> - <para>If you now click the <emphasis><property>Modify</property></emphasis> button, you should see the - <emphasis><property>JavaServer Faces</property>,</emphasis> <emphasis><property>Jboss Portlets</property></emphasis> - and <emphasis><property>Seam</property></emphasis> facets enabled.</para> - </note> + <note> + <title>Tip:</title> + <para>If you now click the <guibutton>Modify</guibutton> button, you should see the<emphasis><property>JavaServer Faces</property>,</emphasis><emphasis><property>Jboss Portlets</property></emphasis> and <emphasis><property>Seam</property></emphasis> facets enabled.</para> + </note> - <figure> - <title>Project Facets</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/seam_portlet/seam_portlet2.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>Project Facets</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_portlet/seam_portlet2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>The next two pages are for adjusting the project Java and Web modules. - They include the default values, so you can skip them by pressing <emphasis> - <property>Next</property>.</emphasis></para> - </listitem> + <listitem> + <para> + The next two pages are for adjusting the project Java and Web modules. They include the default values, so you can skip them by clicking the <guibutton>Next</guibutton> button. + </para> + </listitem> - <listitem> - <para>On the <property>Jboss Portlet Capabilities</property> page, select - <emphasis><property>Portlet Target Runtime Provider</property></emphasis> as the portlet implementation library.</para> + <listitem> + <para> + On the <property>Jboss Portlet Capabilities</property> page, select <emphasis><property>Portlet Target Runtime Provider</property></emphasis> as the portlet implementation library. + </para> - <note> - <title>Tip:</title> - <para>All types of the portlet implementation library are described more closely in the wiki article at: - <ulink url="http://www.jboss.org/community/wiki/PortletFacetLibraries">http://www.jboss.org/community/wiki/PortletFacetLibraries</ulink>.</para> - </note> - </listitem> + <note> + <title>Tip:</title> + <para> + All types of the portlet implementation library are described more closely in the wiki article at: <ulink url="http://www.jboss.org/community/wiki/PortletFacetLibraries">http://www.jboss.org/community/wiki/PortletFacetLibraries</ulink>. + </para> + </note> + </listitem> - <listitem> - <para>The next page is for configuring JSF capabilities. As it contains the default values, just click - <emphasis><property>Next</property></emphasis> to proceed.</para> - </listitem> + <listitem> + <para> + The next page is for configuring JSF capabilities. As it contains the default values, just click the <guibutton>Next</guibutton> button to proceed. + </para> + </listitem> - <listitem> - <para>On the <property>Seam Facet</property> page, set a Seam runtime and - a connection profile.</para> + <listitem> + <para>On the <property>Seam Facet</property> page, set a Seam runtime and a connection profile.</para> - <note> - <title>Tip:</title> - <para>For details about how to set a Seam runtime and a connection profile, see - Configure Seam Facet Settings in the Chapter 2 of the - Seam Dev Tools Reference Guide.</para> - </note> + <note> + <title>Tip:</title> + <para> + For details about how to set a Seam runtime and a connection profile, see Configure Seam Facet Settings in the Chapter 2 of the Seam Dev Tools Reference Guide. + </para> + </note> - <figure> - <title>Seam Facet Settings</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/seam_portlet/seam_portlet3.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>Seam Facet Settings</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_portlet/seam_portlet3.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>On the <property>JBoss JSF Portlet Capabilities</property> page, select the - <emphasis><property>JSF Portlet Target Runtime Provider</property></emphasis> type of the implementation library.</para> + <listitem> + <para> + On the <property>JBoss JSF Portlet Capabilities</property> page, select the <emphasis><property>JSF Portlet Target Runtime Provider</property></emphasis> type of the implementation library. + </para> - <note> - <title>Tip:</title> - <para>If you have <property>JBoss Portlet Bridge</property> downloaded, - alternatively you can select <emphasis><property>JSF Portletbridge Runtime Provider</property></emphasis> and then provide a path to - the <property>JBoss Portlet Bridge</property> distribution.</para> - </note> + <note> + <title>Tip:</title> + <para> + If you have <property>JBoss Portlet Bridge</property> downloaded, alternatively you can select <emphasis><property>JSF Portletbridge Runtime Provider</property></emphasis> and then provide a path to the <property>JBoss Portlet Bridge</property> distribution. + </para> + </note> - <figure> - <title>Setting Portlet Bridge Provider</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/jsf_portlet/jsf_portlet4.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Setting Portlet Bridge Provider</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/jsf_portlet/jsf_portlet4.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>It will add <property>JBoss Portlet Bridge</property> libraries to the project classpath.</para> + </listitem> - <para>It will add <property>JBoss Portlet Bridge</property> libraries to the project classpath.</para> - </listitem> - - <listitem> - <para>Hit <emphasis><property>Finish</property></emphasis> to complete the project creation.</para> - </listitem> - </orderedlist> - </section> + <listitem> + <para>Click the <guibutton>Finish</guibutton> button to complete the project creation.</para> + </listitem> + </orderedlist> + </section> - <section id="create_seam_proj"> - <title>Creating a Seam Project with JBoss Portlet Capabilities</title> + <section id="create_seam_proj"> + <title>Creating a Seam Project with JBoss Portlet Capabilities</title> - <para>The steps to create a Seam project with JBoss Portlet capabilities are as follows:</para> + <para>The steps to create a Seam project with JBoss Portlet capabilities are as follows:</para> - <orderedlist> - <listitem> - <para>In the <emphasis><property>File</property></emphasis> menu, go to <emphasis> - <property>New > Other > Seam > Seam Web Project</property>.</emphasis> The <property>New Seam Project</property> - wizard appears.</para> - </listitem> + <orderedlist> + <listitem> + <para> Select <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>Seam</guimenuitem><guimenuitem>Seam Web Project</guimenuitem></menuchoice>. The <property>New Seam Project</property> wizard will be displayed.</para> + </listitem> - <listitem> - <para>Next steps are the same as in the <xref - linkend="create_dyn_web_proj_seam"/> - procedure starting from the step 2.</para> - </listitem> - </orderedlist> - </section> - </section> - - <section id="seam_portlet_to_seam_project"> - <title>Adding a Seam Portlet to the Project and Deploying It to JBoss Portal</title> + <listitem> + <para>Next steps are the same as in the <xref linkend="create_dyn_web_proj_seam"/> procedure starting from the step 2.</para> + </listitem> + </orderedlist> + </section> + </section> + + <section id="seam_portlet_to_seam_project"> + <title>Adding a Seam Portlet to the Project and Deploying It to JBoss Portal</title> - <para>The previous section has shown you how to create a Web project with Seam and JBoss Portlet capabilities. Now you can create a Seam portlet - and deploy it to <property>JBoss Portal</property> by following the next procedure:</para> - - <orderedlist> - <listitem> - <para>In the <emphasis><property>File</property></emphasis> or context menu of the project go to - <emphasis><property>New > Other > JBoss Tools Web > Portlet > JSF/Seam - Portlet</property>.</emphasis></para> + <para> + The previous section has demonstrated how to create a Web project with Seam and JBoss Portlet capabilities. Now you can create a Seam portlet and deploy it to <property>JBoss Portal</property> by following the next procedure: + </para> + + <orderedlist> + <listitem> + <para> + Select <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>JBoss Tools Web</guimenuitem><guimenuitem>Portlet</guimenuitem><guimenuitem>JSF/Seam Portlet</guimenuitem></menuchoice>. + </para> - <figure> - <title>Calling the Create Portlet Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/seam_portlet/seam_portlet5.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>Calling the Create Portlet Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_portlet/seam_portlet5.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>The <property>Create Portlet</property> wizard starts (for more information about wizard options, see - <xref linkend="jsf_seam_portlet_wizard"/> in the guide reference). - As the Seam configuration is set for the project, the wizard puts the values as for Seam portlet.</para> + <listitem> + <para> + The <property>Create Portlet</property> wizard is displayed (for more information about wizard options, see <xref linkend="jsf_seam_portlet_wizard"/> in the guide reference). As the Seam configuration is set for the project, the wizard enters the values for the for Seam portlet. + </para> - <figure> - <title>Creating Seam Portlet</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/seam_portlet/seam_portlet6.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>Creating Seam Portlet</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_portlet/seam_portlet6.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>Next two pages are filled out with default values, just press <emphasis><property>Next</property></emphasis> to - proceed. On the last one click <emphasis><property>Finish</property></emphasis> to complete.</para> - </listitem> + <listitem> + <para>Next two pages are filled out with default values, just click the <guibutton>Next</guibutton> button to proceed. On the last one click the <guibutton>Finish</guibutton> button to complete the procedure.</para> + </listitem> - <listitem> - <para>To deploy and run the portlet on <property>JBoss Portal</property> complete the steps described in the - <xref linkend="deploying_to_portal"/> procedure. Just use the following URL to see it in the browser: - <emphasis>http://localhost:8080/portal/portal/default/SeamPortlet</emphasis>.</para> + <listitem> + <para> + To deploy and run the portlet on <property>JBoss Portal</property> complete the steps described in the <xref linkend="deploying_to_portal"/> procedure. Just use the following URL to see it in the browser: <emphasis>http://localhost:8080/portal/portal/default/SeamPortlet</emphasis>. + </para> - <figure> - <title>Seam Portlet in the Browser Window</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/seam_portlet/seam_portlet7.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </orderedlist> - </section> + <figure> + <title>Seam Portlet in the Browser Window</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/seam_portlet/seam_portlet7.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </orderedlist> + </section> </section> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/en-US/starting_project.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/en-US/starting_project.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/en-US/starting_project.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -2,20 +2,16 @@ <section id="starting_project"> <title>Creating and Deploying a Java Portlet</title> - <para>This chapter shows how to create a Dynamic Web Project, add a Java + <para>This chapter shows how to create a Dynamic Web Project, add a Java Portlet to it and deploy it to the <property>JBoss Portal</property>.</para> - + <section id="jboss_core_portlet"> <title>Creating a Web Project with JBoss Portlet Capabilities</title> - <para>Fallow the next procedure to create a Web project with JBoss Portlet capabilities pointed to the JBoss Portal runtime.</para> + <para>Follow the next procedure to create a Web project with JBoss Portlet capabilities pointed to the JBoss Portal runtime.</para> <orderedlist> <listitem> - <para>Go to <emphasis> - <property>File > New > Dynamic Web Project</property> - </emphasis> if you are in the <property>Web</property> perspective or <emphasis><property>File > - New > Other > Web > Dynamic Web Project</property></emphasis> in any other perspective. - The <property>New Dynamic Web Project</property> wizard appears.</para> + <para>Select <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Dynamic Web Project</guimenuitem></menuchoice> if you are in the <property>Web</property> perspective or select <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>Web</guimenuitem><guimenuitem>Dynamic Web Project</guimenuitem></menuchoice> in any other perspective. This will display the <property>New Dynamic Web Project</property> wizard.</para> <figure> <title>New Dynamic Web Project</title> @@ -27,19 +23,14 @@ </figure> </listitem> - <listitem><para>Specify the name of the project.</para></listitem> + <listitem> + <para>Specify the name of the project.</para> + </listitem> <listitem> - <para>Click <emphasis> - <property>New</property> - </emphasis> in the <emphasis> - <property>Target Runtime</property> - </emphasis> area to create a JBoss Portal runtime. Choose <emphasis> - <property>JBoss Community > JBoss 4.2 Runtime</property> - </emphasis> and select the <emphasis> - <property>Create a new local server</property> - </emphasis> check box below. Click <emphasis> - <property>Next</property>.</emphasis></para> + <para>Click the <guibutton>New</guibutton> in the <emphasis><property>Target Runtime</property></emphasis> area to create a JBoss Portal runtime. Choose <emphasis><property>JBoss Community > JBoss 4.2 Runtime</property></emphasis> and select the <emphasis><property>Create a new local server</property> + </emphasis> check box below. Click the <guibutton>Next</guibutton> button. + </para> <figure> <title>New Server Runtime</title> @@ -52,12 +43,7 @@ </listitem> <listitem> - <para>The <property>New Server Runtime Environment</property> wizard appears. In the <emphasis> - <property>Name</property></emphasis> field, type <emphasis> - <property>JBoss Portal 2.7 Runtime</property>, - </emphasis> and then use the <emphasis> - <property>Browse</property></emphasis> button to point to the location of JBoss Portal + JBoss AS extracted. Click <emphasis> - <property>Next</property></emphasis> to proceed.</para> + <para>The <property>New Server Runtime Environment</property> wizard appears. In the <emphasis><property>Name</property></emphasis> field, type <emphasis><property>JBoss Portal 2.7 Runtime</property>,</emphasis> and then use the <guibutton>Browse</guibutton> button to point to the location of JBoss Portal + JBoss AS extracted. Click <guibutton>Next</guibutton> button to proceed.</para> <figure> <title>New Server Runtime Environment</title> @@ -70,11 +56,9 @@ </listitem> <listitem> - <para>At this point a new JBoss Server instance will be created. On the next page you can verify the - runtime information defined. If something is incorrect, press <emphasis> - <property>Back</property> - </emphasis> to return to the previous wizard page. Click <emphasis> - <property>Finish</property>.</emphasis></para> + <para> + At this point a new JBoss Server instance will be created. On the next page you can verify the runtime information and configuration. If something is incorrect, press the <guibutton>Back</guibutton> button to return to the previous wizard page. Click the <guibutton>Finish</guibutton> button. + </para> <figure> <title>Target Server</title> @@ -87,10 +71,9 @@ </listitem> <listitem> - <para>Click <emphasis> - <property>Modify</property> - </emphasis> in the <emphasis><property>Configuration</property></emphasis> area to enable - a portlet facet for the project.</para> + <para> + Click the <guibutton>Modify</guibutton> button in the <emphasis><property>Configuration</property></emphasis> area to enable a portlet facet for the project. + </para> <figure> <title>Setting the Project Configuration</title> @@ -103,11 +86,7 @@ </listitem> <listitem> - <para>In the <property>Project Facets</property> dialog, check <emphasis> - <property>JBoss Core Portlet</property> - </emphasis> and press <emphasis> - <property>OK</property> - </emphasis>.</para> + <para>In the <property>Project Facets</property> dialog, check <emphasis><property>JBoss Core Portlet</property></emphasis> and click the <guibutton>OK</guibutton> button.</para> <figure> <title>Enabling the JBoss Core Portlet Facet</title> @@ -120,24 +99,23 @@ <note> <title>Note:</title> - <para>If the portlet libraries aren't available in the runtime you targeted, - <emphasis> - <property>JBoss Portlets</property></emphasis> facets will be hidden on this page.</para> - <para>To make them always visible no matter what the runtime is set, you should enable the appropriate option in - <xref linkend="preferences"/>.</para> + <para> + If the portlet libraries aren't available in the runtime you targeted, <emphasis><property>JBoss Portlets</property></emphasis> facets will be hidden on this page. + </para> + <para>To make them always visible no matter what the runtime is set, you should enable the appropriate option in <xref linkend="preferences"/>.</para> </note> </listitem> <listitem> - <para>The <property>Java</property> and <property>Web Module</property> pages are for configuring Java and Web modules in the project. - Here all values are set, so leave everything as it is.</para> + <para> + The <property>Java</property> and <property>Web Module</property> pages are for configuring Java and Web modules in the project. Here the default values are fine, so leave everything as it is. + </para> </listitem> <listitem> - <para>The last wizard page will ask you to add JBoss Portlet capabilities to the - project. Select <emphasis> - <property>Portlet Target Runtime Provider</property></emphasis> and click <emphasis> - <property>Finish</property></emphasis> to complete the project creation.</para> + <para> + The last wizard page will ask you to add JBoss Portlet capabilities to the project. Select <emphasis><property>Portlet Target Runtime Provider</property></emphasis> and click the <guibutton>Finish</guibutton> button to complete the project creation. + </para> <figure> <title>Including the Portlet Libraries Provided by Target Runtime</title> @@ -151,15 +129,17 @@ <note> <title>Note:</title> <para>All types available under <emphasis> - <property>Portlet Implementation Library</property></emphasis> are fully described in the Wiki article at: + <property>Portlet Implementation Library</property> + </emphasis> are fully described in the Wiki article at: <ulink url="http://www.jboss.org/community/wiki/PortletFacetLibraries">http://www.jboss.org/community/wiki/PortletFacetLibraries</ulink>.</para> </note> </listitem> </orderedlist> <para>As the result, <property>JBoss Portlet Tools</property> adds <emphasis> - <property>JBoss Core Portlet</property></emphasis> facet to the project, - creates an empty <literal>portlet.xml</literal> file and adds the JBoss Portlet library to the project classpath.</para> + <property>JBoss Core Portlet</property> + </emphasis> facet to the project, + creates an empty <filename>portlet.xml</filename> file and adds the JBoss Portlet library to the project classpath.</para> <figure> <title>Portlet Project Structure Overview</title> @@ -169,19 +149,21 @@ </imageobject> </mediaobject> </figure> - </section> + </section> - <section id="adding_java_portlet"> - <title>Adding a Java Portlet to a Web Project</title> - - <para>At the previous section you have created a web project with JBoss Portlet capabilities. - The next steps will show you how to add a new Java portlet to the project.</para> + <section id="adding_java_portlet"> + <title>Adding a Java Portlet to a Web Project</title> + <para> + At the previous section you have created a web project with JBoss Portlet capabilities. The next steps will show you how to add a new Java portlet to the project. + </para> + <orderedlist> - <listitem> - <para>Right-click the project and follow to <emphasis> - <property>New > Other > JBoss Tools Web > Portlet > Java - Portlet</property>.</emphasis></para> + <listitem> + <para> + Right-click the project and select <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>JBoss Tools Web</guimenuitem><guimenuitem>Portlet</guimenuitem><guimenuitem>Java + Portlet</guimenuitem></menuchoice>. + </para> <figure> <title>New Java Portlet</title> @@ -194,15 +176,7 @@ </listitem> <listitem> - <para>The <property>Create Portlet</property> wizard starts (for information about the wizard options, see - <xref linkend="java_portlet_wizard"/> in the guide reference). - The wizard fills in the <emphasis><property>Project</property></emphasis> and <emphasis> - <property>Source Folder</property></emphasis> fields for you. You should specify a Java package and a class name - (for instance, <emphasis> - <property>org.example</property></emphasis> and <emphasis> - <property>TestPortlet</property></emphasis>). Then click <emphasis> - <property>Next</property> - </emphasis>.</para> + <para>The <property>Create Portlet</property> wizard starts (for information about the wizard options, see <xref linkend="java_portlet_wizard"/> in the guide reference). The wizard fills in the <emphasis><property>Project</property></emphasis> and <emphasis><property>Source Folder</property></emphasis> fields for you. You should specify a Java package and a class name (for instance, <emphasis><property>org.example</property></emphasis> and <emphasis><property>TestPortlet</property></emphasis>). Then click the <guibutton>Next</guibutton> button.</para> <figure> <title>Specifying Class File Destination</title> @@ -214,84 +188,85 @@ </figure> </listitem> - <listitem><para>You may leave the next three pages with default values, on the last one hit <emphasis> - <property>Finish</property>.</emphasis></para> + <listitem> + <para> + You may leave the next three pages with default values, on the last one click the <guibutton>Finish</guibutton> button. + </para> </listitem> </orderedlist> - <para>Once a Java portlet is created, new resources are added to the project structure: a Java portlet class (<literal>TestPortlet.java</literal>), - <literal>default-object.xml</literal> and <literal>portlet-instances.xml</literal> files and the <literal>portlet.xml</literal> descriptor is updated as well.</para> + <para> + Once a Java portlet is created, new resources are added to the project structure: a Java portlet class (<filename>TestPortlet.java</filename>), <filename>default-object.xml</filename> and <filename>portlet-instances.xml</filename> files and the <filename>portlet.xml</filename> descriptor is updated as well. + </para> - <figure> - <title>Structure of the Project with a Java Portlet</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/starting_project/starting_project_12.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Structure of the Project with a Java Portlet</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/starting_project/starting_project_12.png"/> + </imageobject> + </mediaobject> + </figure> - <para>Thus, now the project is ready to be built and deployed.</para> - </section> + <para>Now the project is ready to be built and deployed.</para> + </section> - <section id="deploying_to_portal"> - <title>Deploying a Portlet to JBoss Portal</title> + <section id="deploying_to_portal"> + <title>Deploying a Portlet to JBoss Portal</title> - <para>You can deploy a portlet project in the way you deploy any other web application.</para> + <para>You can deploy a portlet project in the way you deploy any other web application.</para> - <orderedlist> - <listitem> - <para>Right-click the project and do <emphasis> - <property>Run As > Run On Server</property>. - </emphasis> The <property>Run On Server</property> wizard starts.</para> + <orderedlist> + <listitem> + <para> + Right-click the project and select <menuchoice><guimenuitem>Run As</guimenuitem><guimenuitem>Run On Server</guimenuitem></menuchoice>. The <guilabel>Run On Server</guilabel> wizard starts. + </para> - <figure> - <title>Running the Java Portlet on Server</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/starting_project/runOnServer.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> + <figure> + <title>Running the Java Portlet on Server</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/starting_project/runOnServer.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> - <listitem> - <para>Select <emphasis><property>JBoss Portal 2.7 Server</property></emphasis> created before and click <emphasis><property>Next</property>.</emphasis></para> - </listitem> + <listitem> + <para>Select <emphasis><property>JBoss Portal 2.7 Server</property></emphasis> created before and click the <guibutton>Next</guibutton> button. + </para> + </listitem> - <listitem> - <para>On the <emphasis> - <property>Add and Remove</property> - </emphasis> page move the created project to the right and click <emphasis> - <property>Finish</property>.</emphasis></para> + <listitem> + <para> + On the <emphasis><property>Add and Remove</property></emphasis> page move the created project to the right and click <guilabel>Finish</guilabel>. + </para> - <figure> - <title>Deploying the Portlet Application</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/starting_project/starting_project_13.png"/> - </imageobject> - </mediaobject> - </figure> + <figure> + <title>Deploying the Portlet Application</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/starting_project/starting_project_13.png"/> + </imageobject> + </mediaobject> + </figure> - <para>It will deploy the portlet application and start <property>JBoss - AS</property>.</para> - </listitem> + <para>It will deploy the portlet application and start <property>JBoss AS</property>.</para> + </listitem> - <listitem> - <para>Use the <emphasis>http://localhost:8080/portal/portal/default/default</emphasis> URL to see your - portlet in the browser.</para> + <listitem> + <para>Use the <ulink url="http://localhost:8080/portal/portal/default/default">http://localhost:8080/portal/portal/default/default</ulink> URL to see your portlet in the browser.</para> - <figure> - <title>Java Portlet in the Browser Window</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/starting_project/starting_project_14.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </orderedlist> - </section> + <figure> + <title>Java Portlet in the Browser Window</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/starting_project/starting_project_14.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </orderedlist> + </section> </section> Modified: branches/jbosstools-3.2.x/portlet/docs/reference/pom.xml =================================================================== --- branches/jbosstools-3.2.x/portlet/docs/reference/pom.xml 2011-07-18 01:59:12 UTC (rev 32975) +++ branches/jbosstools-3.2.x/portlet/docs/reference/pom.xml 2011-07-18 02:02:34 UTC (rev 32976) @@ -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>JBoss_Portal_Tools_Reference_Guide</docname> - <bookname>JBoss Portal Tools Reference Guide</bookname> - </properties> - - <profiles> + <properties> + <translation>en-US</translation> + <docname>JBoss_Portal_Tools_Reference_Guide</docname> + <bookname>JBoss Portal Tools Reference Guide</bookname> + </properties> + <profiles> +  - <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>  - <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>  - <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>  - <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>  - <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>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>

14 years, 9 months

1
0
0 / 0

JBoss Tools SVN: r32975 - in branches/jbosstools-3.2.x/hibernatetools/docs/reference: en-US and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2011-07-17 21:59:12 -0400 (Sun, 17 Jul 2011) New Revision: 32975 Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Book_Info.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Feedback.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Hibernate_Tools_Reference_Guide.ent branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Hibernate_Tools_Reference_Guide.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Preface.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Revision_History.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/ant.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/codegen.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/codegenarchitecture.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property1.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property2.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property3.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property4.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property5.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/annotations1.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/annotations1_a.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/annotations2.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/annotations3.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration1.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration10.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration11.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration2.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration3.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration4.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration5.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration7.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration9.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/diagram1.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/diagram2.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/diagramToolbar.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/map_diagram1.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/map_diagram2.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/map_diagram3.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_0.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_0_a.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_0_b.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_1.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_12.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_12_a.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_12_b.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_13.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_14.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_15.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_16.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_17.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_17_a.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_18.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_18_a.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_18_b.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_18_g.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_19.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_19_b.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_19_c.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_19_d.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_2.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_20.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_21_a.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_21_b.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_22.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_2_a.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_3.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_4_a.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_4_b.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_4_c.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_4_d.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_5.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_6.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_7.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_8.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_8a.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_8b.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_9.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/prototypingQueries.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/saveDiagram.png branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/introduction.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/master.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/plugins.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/reverseengineering.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/setup.xml branches/jbosstools-3.2.x/hibernatetools/docs/reference/pom.xml Log: updated for GA Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Book_Info.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Book_Info.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Book_Info.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -5,11 +5,13 @@ <title>Hibernate Tools Reference Guide</title> <subtitle>Provides information relating to the Hibernate Tools set.</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 Hibernate Tools Reference Guide explains how to use the Hibernate Tools to perform reverse engineering, code generation, visualization and interaction with Hibernate.</para> + <para> + The Hibernate Tools Reference Guide explains how to use the Hibernate Tools to perform reverse engineering, code generation, visualization and interaction with Hibernate. + </para> </abstract> <corpauthor> <inlinemediaobject> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Feedback.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Feedback.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Feedback.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -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=12310500&issu...">https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...</ulink> - </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> +  <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/hibernatetools/docs/reference/en-US/Hibernate_Tools_Reference_Guide.ent =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Hibernate_Tools_Reference_Guide.ent 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Hibernate_Tools_Reference_Guide.ent 2011-07-18 01:59:12 UTC (rev 32975) @@ -1,4 +1,7 @@ <!ENTITY PRODUCT "JBoss"> <!ENTITY BOOKID "Hibernate_Tools_Reference_Guide"> -<!ENTITY YEAR "2010"> +<!ENTITY YEAR "2011"> <!ENTITY HOLDER "Red Hat"> +<!ENTITY BZPRODUCT "JBoss Developer Studio"> +<!ENTITY BZCOMPONENT "Hibernate Tools Reference Guide"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Develope...'>http://bugzilla.redhat.com/</ulink>"> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Hibernate_Tools_Reference_Guide.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Hibernate_Tools_Reference_Guide.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Hibernate_Tools_Reference_Guide.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -5,11 +5,12 @@ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> -<xi:include href="setup.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> + <xi:include href="codegenarchitecture.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="plugins.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="ant.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="reverseengineering.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="codegen.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/hibernatetools/docs/reference/en-US/Preface.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Preface.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Preface.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -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.html">Red Hat Documentation</ulink> website under the <guilabel>JBoss Developer Studio</guilabel> section. </para> -  </preface> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Revision_History.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Revision_History.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/Revision_History.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -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</surname><email>irooskov(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>General updates</member> - </simplelist> - </revdescription> - </revision> - <revision> - <revnumber>0</revnumber><date>Fri Nov 20 2009</date> - <author> - <firstname>Isaac</firstname><surname>Rooskov</surname><email>irooskov(a)redhat.com</email> - </author> - <revdescription> - <simplelist> - <member>Initial creation of book by publican</member> - </simplelist> - </revdescription> - </revision> - </revhistory> - </simpara> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>2-0</revnumber> + <date>Fri Jan 21 2011</date> + <author> + <firstname>JBoss Tools</firstname> + <surname>Documentation Team</surname> + <email>mcaspers(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>General updates</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>irooskov(a)redhat.com</email> + </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>irooskov(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>Initial creation of book by publican</member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </simpara> </appendix> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/ant.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/ant.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/ant.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -2,42 +2,30 @@ <chapter id="ant"> <title>Ant Tools</title> - <para>Maybe somebody will find it more preferable to use Ant for generation purposes. Thus, this - chapter is intended to get you ready to start using Hibernate Tools via Ant tasks.</para> + <para>This chapter demonstrates how to use Hibernate Tools via Ant tasks.</para> <section> <title>Introduction</title> - <para>The <emphasis> - <property>hibernate-tools.jar</property> - </emphasis> contains the core for the <property>Hibernate Tools</property>. It is used as the - basis for both the Ant tasks described in this document and the eclipse plugins both available - from tools.hibernate.org. The <emphasis> - <property>hibernate-tools.jar</property> - </emphasis> is located in your eclipse plugins directory at <emphasis> - <property>/plugins/org.hibernate.eclipse.x.x.x/lib/tools/hibernate-tools.jar</property>.</emphasis></para> - <para>This jar is 100% independent from the eclipse platform and can thus be used independently - of eclipse.</para> + <para> + The <filename>hibernate-tools.jar</filename> file, available from <ulink url="http://www.hibernate.org/subprojects/tools.html">tools.hibernate.org</ulink>, contains the core code for <productname>Hibernate Tools</productname>. It is used as the basis for both the Ant tasks described in this document and the Eclipse plugins available as part of JBoss Developer Studio. The <filename>hibernate-tools.jar</filename> file is located in your Eclipse plugins directory at <filename>/plugins/org.hibernate.eclipse.x.x.x/lib/tools/hibernate-tools.jar</filename>. + </para> + <para>This jar is 100% independent from the Eclipse platform and can thus be used independently of Eclipse.</para> <note> <title>Note:</title> - <para>There might be incompatibilities with respect to the Hibernate3.jar bundled with the - tools and your own jar. Thus to avoid any confusion it is recommended to use the - hibernate3.jar and hibernate-annotations.jar bundled with the tools when you want to use the - Ant tasks. Do not worry about using e.g. Hibernate 3.2 jar's with e.g. a Hibernate 3.1 - project since the output generated will work with previous Hibernate 3 versions. </para> + <para> + There may be incompatibilities with respect to the <filename>hibernate3.jar</filename> bundled with the tools and your own JAR. To avoid any confusion it is recommended that you use the <filename>hibernate3.jar</filename> and <filename>hibernate-annotations.jar</filename> files bundled with the tools when you want to use the Ant tasks. Do not worry about using the JAR's from a later version of Hibernate (e.g. Hibernate 3.2) with a project using an earlier version of Hibernate (e.g. a Hibernate 3.1) since the generated output will work with previous Hibernate 3 versions. + </para> </note> </section> <section> <title>The <hibernatetool> Ant Task</title> - <para>To use the ant tasks you need to have the <emphasis> - <property>hibernatetool</property> - </emphasis> task defined. That is done in your <emphasis> - <property>build.xml</property> - </emphasis> by inserting the following xml (assuming the jars are in the - <literal>lib</literal> directory): </para> + <para> + To use the Ant tasks you need to have the <code>hibernatetool</code> task defined. That is done in your <filename>build.xml</filename> file by inserting the following XML (assuming the JARs are located in the <filename>lib</filename> directory): + </para> <programlisting role="XML"><![CDATA[<path id="toolslib"> <path location="lib/hibernate-tools.jar" /> @@ -51,23 +39,17 @@ classpathref="toolslib" /> ]]></programlisting> - <para>This - <code><taskdef></code> - defines an Ant task called <emphasis> - <property> hibernatetool </property> - </emphasis> which now can be used anywhere in your ant <emphasis> - <property>build.xml</property> - </emphasis> files. It is important to include all the <property>Hibernate Tools</property> - dependencies as well as the jdbc driver.</para> + <para> + This <code><taskdef></code> defines an Ant task called <code> hibernatetool </code> which now can be used anywhere in your Ant <filename>build.xml</filename> files. It is important to include all the <productname>Hibernate Tools</productname> dependencies as well as the JDBC driver. + </para> - <para>Notice that to use the annotation based Configuration you must <ulink - url="http://annotations.hibernate.org">get a release</ulink>. </para> + <para> + Notice that to use the annotation based Configuration you must <ulink url="http://www.hibernate.org/">get a release</ulink>. + </para> <para/> - <para>When using the <emphasis> - <property> hibernatetool </property> - </emphasis> task you have to specify one or more of the following:</para> + <para>When using the <code>hibernatetool</code> task you have to specify one or more of the following:</para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="defaultDestinationDirectory" @@ -110,7 +92,7 @@ </entry> <entry> - <para>Destination directory for files generated with exporters</para> + <para>Destination directory for files generated with the exporters</para> </entry> <entry> @@ -124,7 +106,7 @@ </entry> <entry> - <para>A path to be used to look up user-edited templates</para> + <para>A path used for looking up user-edited templates</para> </entry> <entry> @@ -138,8 +120,7 @@ </entry> <entry> - <para>A classpath to be used to resolve resources, such as mappings and - usertypes</para> + <para>A classpath to be used to resolve resources, such as mappings and user types</para> </entry> <entry> @@ -154,8 +135,7 @@ </entry> <entry> - <para>Used to set properties to control the exporters. Mostly relevant for providing - custom properties to user defined templates</para> + <para>Used to set properties that control the exporters. Mostly relevant for providing custom properties to user defined templates</para> </entry> <entry> @@ -165,13 +145,11 @@ <row> <entry> - <para>configuration (annotationconfiguration, jpaconfiguration, - jdbcconfiguration)</para> + <para>configuration (annotationconfiguration, jpaconfiguration, jdbcconfiguration)</para> </entry> <entry> - <para>One of four different ways of configuring the Hibernate Meta Model must be - specified</para> + <para>One of four different ways of configuring the Hibernate Meta Model must be specified</para> </entry> <entry> @@ -201,12 +179,9 @@ <section> <title>Basic examples</title> - <para>The following example shows the most basic setup for generating pojo's via <code><hbm2java></code> from a normal <emphasis> - <property> - <literal>hibernate.cfg.xml</literal> - </property>. </emphasis> The output will be put in the <emphasis> - <property>${build.dir}/generated</property> - </emphasis> directory.</para> + <para> + The following example shows the most basic setup for generating POJOs via <code><hbm2java></code> from a normal <filename>hibernate.cfg.xml</filename> file. The output will be placed in the <filename>${build.dir}/generated</filename> directory. + </para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> <classpath> @@ -218,17 +193,13 @@ </hibernatetool>]]></programlisting> - <para>The following example is similar, but now we are performing multiple exports from the - same configuration. We are exporting the schema via <code><hbm2dll></code>, generates some DAO code via <code><hbm2dao></code> - and finally runs a custom code generation via <code><hbmtemplate></code>. This is again from a normal <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis> and the output is still put in the <emphasis> - <property> - <literal>${build.dir}/generated</literal> - </property> - </emphasis> directory. Furthermore the example also shows where a classpath is specified - when you e.g. have custom usertypes or some mappings that is needed to be looked up as a - classpath resource.</para> + <para> + The following example is similar, but now we are performing multiple exports from the same configuration. We are exporting the schema via <code><hbm2dll></code>, generating some DAO code via <code><hbm2dao></code>, and finally running some custom code generation via <code><hbmtemplate></code>. This is again from a normal <filename>hibernate.cfg.xml</filename> file, and the output is still placed in the <filename>${build.dir}/generated</filename> directory. + </para> + + <para> + The example also shows how a classpath is specified, which is useful when you have custom user types or some mappings that are required to be looked up as a classpath resource. + </para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> <classpath> @@ -251,36 +222,29 @@ <section> <title>Hibernate Configurations</title> - <para><emphasis>Hibernatetool</emphasis> supports four different Hibernate configurations: A - standard Hibernate configuration - (<code><configuration></code>), Annotation based - configuration (<code><annotationconfiguration></code>), - JPA persistence based configuration - (<code><jpaconfiguration></code>) and a JDBC based - configuration (<code><jdbcconfiguration></code>) - for use when reverse engineering.</para> + <para> + <productname>Hibernatetool</productname> supports four different Hibernate configurations: A standard Hibernate configuration (<code><configuration></code>), Annotation based configuration (<code><annotationconfiguration></code>), JPA persistence based configuration (<code><jpaconfiguration></code>) and a JDBC based configuration (<code><jdbcconfiguration></code>) used when reverse engineering. + </para> - <para>Each have in common that they are able to build up a Hibernate Configuration object from - which a set of exporters can be run to generate various output. </para> + <para> + Each can be used to build a Hibernate Configuration object, from which a set of exporters can be run in order to generate various output formats. + </para> <note> <title>Note:</title> - <para>Output can be anything, e.g. specific files, statements execution against a database, - error reporting or anything else that can be done in java code.</para> + <para> + Output can be anything, e.g. specific files, statements execution against a database, error reporting or anything else that can be done in Java code. + </para> </note> - <para>The following sections describe what the various configurations can do, plus lists the - individual settings they have.</para> + <para>The following sections describe what the various configurations can do, as well as listing their individual settings.</para> <section> <title>Standard Hibernate Configuration (<configuration>)</title> - <para>A - <code><configuration></code> - is used to define a standard Hibernate configuration. A standard Hibernate - configuration reads the mappings from a <emphasis> - <property>cfg.xml</property> - </emphasis> and/or a fileset.</para> + <para> + A <code><configuration></code> tag is used to define a standard Hibernate configuration. A standard Hibernate configuration reads the mappings from a <filename>cfg.xml</filename> file and/or a fileset. + </para> <programlisting role="XML"><![CDATA[<configuration configurationfile="hibernate.cfg.xml" @@ -321,7 +285,7 @@ </entry> <entry> - <para>The name of a Hibernate configuration file, e.g. "hibernate.cfg.xml"</para> + <para>The name of a Hibernate configuration file, e.g. <filename>hibernate.cfg.xml</filename>.</para> </entry> <entry> @@ -335,7 +299,7 @@ </entry> <entry> - <para>The name of a property file, e.g. "hibernate.properties"</para> + <para>The name of a property file, e.g. <filename>hibernate.properties</filename>.</para> </entry> <entry> @@ -349,8 +313,7 @@ </entry> <entry> - <para>Name of a class that implements org.xml.sax.EntityResolver. Used if the - mapping files require custom entity resolver</para> + <para>Name of a class that implements <code>org.xml.sax.EntityResolver</code>. Used if the mapping files require custom entity resolver.</para> </entry> <entry> @@ -365,9 +328,9 @@ </entry> <entry> - <para>Name of a class that implements org.hibernate.cfg.NamingStrategy. Used for - setting up the naming strategy in Hibernate which controls the automatic naming of - tables and columns.In JPA projects naming strategy is supported for default Name/Columns mapping</para> + <para> + Name of a class that implements <code>org.hibernate.cfg.NamingStrategy</code>. Used for setting up the naming strategy in Hibernate which controls the automatic naming of tables and columns. In JPA projects naming strategy is supported for default Name/Columns mapping. + </para> </entry> <entry> @@ -381,9 +344,9 @@ </entry> <entry> - <para>A standard Ant fileset. Used to include hibernate mapping files. Remember that - if mappings are already specified in the hibernate.cfg.xml then it should not be - included via the fileset as it will result in duplicate import exceptions.</para> + <para> + A standard Ant fileset. Used to include hibernate mapping files. Remember that if mappings are already specified in the <filename>hibernate.cfg.xml</filename> then it should not be included via the fileset as it will result in duplicate import exceptions. + </para> </entry> <entry> @@ -399,20 +362,15 @@ <section> <title>Example</title> - <para>This example shows an example where no <emphasis> - <property> - <literal>hibernate.cfg.xml</literal> - </property> - </emphasis> exists, and a <emphasis> - <property> hibernate.properties </property> - </emphasis> and fileset is used instead. </para> + <para> + This example shows an example where no <filename>hibernate.cfg.xml</filename> file exists, and a <filename>hibernate.properties</filename> file and fileset is used instead. + </para> <note> <title>Note:</title> - <para> Hibernate will still read any global <emphasis> - <property>hibernate.properties</property> - </emphasis> available in the classpath, but the specified properties file here will - override those values for any non-global property.</para> + <para> + Hibernate will still read any global <filename>hibernate.properties</filename> files available in the classpath, but the specified properties file here will override those values for any non-global property. + </para> </note> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> @@ -433,26 +391,18 @@ <section> <title>Annotation based Configuration (<annotationconfiguration>)</title> - <para>An - <code><annotationconfiguration></code> - is used when you want to read the metamodel from EJB3/Hibernate Annotations - based POJO's.</para> + <para>An <code><annotationconfiguration></code> tag is used when you want to read the metamodel from EJB3 or Hibernate Annotations based POJO's.</para> <important> <title>Important:</title> - <para>To use it remember to put the jar files needed for using hibernate annotations in the - classpath of the - <code><taskdef></code>, i. e. - hibernate-annotations.jar and hibernate-commons-annotations.jar.</para> + <para> + To use an <code><annotationconfiguration></code> tag remember to place the JAR files required to use Hibernate annotations in the classpath of the <code><taskdef></code>, i.e. <filename>hibernate-annotations.jar</filename> and <filename>hibernate-commons-annotations.jar</filename>. + </para> </important> - <para>The - <code><annotationconfiguration></code> - supports the same attributes as a - <code><configuration></code> - except that the configurationfile attribute is now required as that is from - where an <emphasis>AnnotationConfiguration</emphasis> gets the list of classes/packages it - should load.</para> + <para> + The <code><annotationconfiguration></code> tag supports the same attributes as the <code><configuration></code> tag, with the exception being that the <code>configurationfile</code> attribute is now required as that is where an <emphasis>AnnotationConfiguration</emphasis> gets the list of classes and packages it should load. + </para> <para>Thus the minimal usage is:</para> @@ -470,30 +420,21 @@ <section> <title>JPA based configuration (<jpaconfiguration>)</title> - <para>A <code><jpaconfiguration></code> - is used when you want to read the metamodel from JPA/Hibernate Annotation where - you want to use the auto-scan configuration as defined in the JPA spec (part of EJB3). In - other words, when you do not have a <emphasis> - <property>hibernate.cfg.xml</property>, </emphasis> but instead have a setup where you use - a <emphasis> - <property>persistence.xml</property> - </emphasis> packaged in a JPA compliant manner.</para> + <para> + A <code><jpaconfiguration></code> tag is used when you want to read the metamodel from JPA or Hibernate Annotation where you want to use the auto-scan configuration as defined in the JPA specification (part of EJB3). In other words, when you do not have a <filename>hibernate.cfg.xml</filename>, but instead have a setup where you use a <filename>persistence.xml</filename> file packaged in a JPA compliant manner. + </para> - <para>The <code><jpaconfiguration></code> - will simply just try and auto-configure it self based on the available - classpath, e.g. look for <emphasis> - <property>META-INF/persistence.xml</property>. </emphasis></para> + <para> + The <code><jpaconfiguration></code> tag will try and auto-configure it self based on the available classpath, e.g. look for the <filename>META-INF/persistence.xml</filename> file. + </para> - <para>The <emphasis> - <property>persistenceunit</property> - </emphasis> attribute can be used to select a specific persistence unit. If no <emphasis> - <property>persistenceunit</property> - </emphasis> is specified it will automatically search for one and if a unique one is found, - use it, but if multiple persistence units are available it will error.</para> + <para> + The <code>persistenceunit</code> attribute can be used to select a specific persistence unit. If no <code>persistenceunit</code> attribute is specified it will automatically search for one, and if a unique one is found, use it. However, having multiple persistence units will result in an error. + </para> - <para>To use a <code><jpaconfiguration></code> - you will need to specify some additional jars from Hibernate EntityManager in - the <code><taskdef></code> of the hibernatetool. The following shows a full setup:</para> + <para> + To use a <code><jpaconfiguration></code> tag you will need to specify some additional JARs from the Hibernate EntityManager in the <code><taskdef></code> section of the hibernatetool. The following demonstrates a full setup: + </para> <programlisting role="XML"><![CDATA[<path id="ejb3toolslib"> <path refid="jpatoolslib"/>  @@ -524,8 +465,9 @@ <note> <title>Note:</title> - <para>ejb3configuration was the name used in previous versions. It still works but will emit - a warning telling you to use <literal>jpaconfiguration</literal> instead.</para> + <para> + <literal>ejb3configuration</literal> was the name used in previous versions. It still works but will display a warning telling you to use <literal>jpaconfiguration</literal> instead. + </para> </note> </section> @@ -533,17 +475,15 @@ <section> <title>JDBC Configuration for reverse engineering (<jdbcconfiguration>)</title> - <para>A <code><jdbcconfiguration></code> is used to perform reverse engineering of the database from a JDBC connection.</para> + <para>A <code><jdbcconfiguration></code> tag is used to perform reverse engineering of a database from a JDBC connection.</para> - <para>This configuration works by reading the connection properties either from <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis> or <emphasis> - <property>hibernate.properties</property> - </emphasis> with a fileset.</para> + <para> + This configuration works by reading the connection properties either from a <filename>hibernate.cfg.xml</filename> file or a <filename>hibernate.properties</filename> file with a fileset. + </para> - <para>The <code><jdbcconfiguration></code> has the same attributes as a - <code><configuration></code> - plus the following additional attributes:</para> + <para> + The <code><jdbcconfiguration></code> tag has the same attributes as a <code><configuration></code> tag, plus the following additional attributes: + </para> <programlisting role="XML"><![CDATA[<jdbcconfiguration ... @@ -599,7 +539,7 @@ </entry> <entry> - <para>The name of a property file, e.g. "hibernate.properties"</para> + <para>The name of a property file, e.g. <filename>hibernate.properties</filename></para> </entry> <entry> @@ -613,11 +553,9 @@ </entry> <entry> - <para>Name of a class that implements org.hibernate.cfg.reveng.ReverseEngineeringStrategy. - Used for setting up the strategy the tools will use to control the reverse engineering, e.g. naming of - properties, which tables to include/exclude etc. Using a class instead of (or as - addition to) a reveng.xml file gives you full programmatic control of the reverse - engineering.</para> + <para> + Name of a class that implements <filename>org.hibernate.cfg.reveng.ReverseEngineeringStrategy</filename>. Used for setting up the strategy the tools will use to control the reverse engineering, e.g. naming of properties, which tables to include or exclude etc. Using a class instead of (or as addition to) a <filename>reveng.xml</filename> file gives you full programmatic control of the reverse engineering. + </para> </entry> <entry> @@ -632,9 +570,9 @@ </entry> <entry> - <para>If true, tables which are pure many-to-many link tables will be mapped as - such. A pure many-to-many table is one which primary-key contains exactly two - foreign-keys pointing to other entity tables and has no other columns.</para> + <para> + If true, tables which are pure many-to-many link tables will be mapped as such. A pure many-to-many table is one which primary-key contains exactly two foreign-keys pointing to other entity tables and has no other columns. + </para> </entry> <entry> @@ -648,9 +586,10 @@ </entry> <entry> - <para>If true, columns named VERSION or TIMESTAMP with appropriate types will be - mapped with the appropriate optimistic locking corresponding to - <code><version></code> or <code><timestamp></code>.</para> + <para> + If true, columns named VERSION or TIMESTAMP with appropriate types will be mapped with the appropriate optimistic locking corresponding to + <code><version></code> or <code><timestamp></code>. + </para> </entry> <entry> @@ -666,12 +605,9 @@ <section> <title>Example</title> - <para>Here is an example of using <code><jdbcconfiguration></code> to generate Hibernate xml mappings via - <code><hbm2hbmxml></code>. The connection settings here - is read from a <emphasis> - <property> hibernate.properties </property> - </emphasis> file but could just as well have been read from a <emphasis> - <property>hibernate.cfg.xml</property>. </emphasis></para> + <para> + Here is an example using a <code><jdbcconfiguration></code> tag to generate Hibernate XML mappings via <code><hbm2hbmxml></code>. The connection settings used here are read from a <filename>hibernate.properties</filename> file, but they could also have been defined in a <filename>hibernate.cfg.xml</filename> file. + </para> <programlisting role="XML"><![CDATA[<hibernatetool> <jdbcconfiguration propertyfile="etc/hibernate.properties" /> @@ -685,20 +621,16 @@ <section> <title>Exporters</title> - <para>Exporters are the parts that do the actual job of converting the hibernate metamodel into - various artifacts, mainly code. The following section describes the current supported set of - exporters in the <property>Hibernate Tool</property> distribution. It is also possible for - userdefined exporters, that is done through the - <code><hbmtemplate></code> - exporter.</para> + <para> + Exporters do the actual job of converting the Hibernate metamodel into various artifacts, mainly code. The following section describes the current supported set of exporters in the <productname>Hibernate Tool</productname> distribution. It is also possible to implement user defined exporters, which is done through the <code><hbmtemplate></code> exporter. + </para> <section> <title>Database schema exporter (<hbm2ddl>)</title> - <para><code><hbm2ddl></code> lets you run schemaexport and schemaupdate which generates the appropriate SQL - DDL and allow you to store the result in a file or export it directly to the database. - Remember that if a custom naming strategy is needed it is placed on the configuration - element.</para> + <para> + <code><hbm2ddl></code> lets you run schemaexport and schemaupdate which generates the appropriate SQL DDL and allow you to store the result in a file or export it directly to the database. Remember that if a custom naming strategy is needed it is defined in the configuration element. + </para> <programlisting role="XML"><![CDATA[<hbm2ddl export="true|false" @@ -754,11 +686,9 @@ </entry> <entry> - <para>Try and create an update script representing the "delta" - between what is in the database and what the mappings specify. Ignores - create/update attributes. (<emphasis>Do *not* use against production databases, no - guarantees at all that the proper delta can be generated nor that the underlying - database can actually execute the needed operations</emphasis>).</para> + <para> + Try and create an update script representing the "delta" that is, between what is in the database and what the mappings specify. Ignores create and update attributes. (<emphasis>Do *not* use against production databases, as there are no guarantees that the proper delta can be generated, nor that the underlying database can actually execute the required operations</emphasis>). + </para> </entry> <entry> @@ -772,8 +702,7 @@ </entry> <entry> - <para>Output will contain drop statements for the tables, indices and - constraints</para> + <para>Output will contain drop statements for the tables, indices and constraints</para> </entry> <entry> @@ -788,8 +717,7 @@ </entry> <entry> - <para>Output will contain create statements for the tables, indices and - constraints</para> + <para>Output will contain create statements for the tables, indices and constraints</para> </entry> <entry> @@ -860,9 +788,9 @@ <section> <title>Example</title> - <para>Basic example of using <code><hbm2ddl></code>, which does not export to the - database but simply dumps the sql to a file named <emphasis> - <property>sql.ddl</property>. </emphasis></para> + <para> + Below is a basic example of using <code><hbm2ddl></code>, which does not export to the database but simply dumps the SQL to a file named <filename>sql.ddl</filename>. + </para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> <configuration configurationfile="hibernate.cfg.xml"/> @@ -874,8 +802,9 @@ <section> <title>POJO java code exporter (<hbm2java>)</title> - <para><code><hbm2java></code> is a java codegenerator. Options for controlling whether JDK 5 syntax can be - used and whether the POJO should be annotated with EJB3/Hibernate Annotations.</para> + <para> + <code><hbm2java></code> is a Java code generator. Options for controlling whether JDK 5 syntax can be used and whether the POJO should be annotated with EJB3/Hibernate Annotations. + </para> <programlisting role="XML"><![CDATA[<hbm2java jdk5="true|false" @@ -925,8 +854,9 @@ </entry> <entry> - <para>Code will contain EJB 3 features, e.g. using annotations from - javax.persistence and org.hibernate.annotations</para> + <para> + Code will contain EJB 3 features, e.g. using annotations from <code>javax.persistence</code> and <code>org.hibernate.annotations</code> + </para> </entry> <entry> @@ -942,7 +872,7 @@ <section> <title>Example</title> - <para>Basic example of using <code><hbm2java></code> to generate POJO's that utilize jdk5 constructs.</para> + <para>Here is a basic example using <code><hbm2java></code> to generate POJO's that utilize JDK5 constructs.</para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> <configuration configurationfile="hibernate.cfg.xml"/> @@ -954,16 +884,15 @@ <section> <title>Hibernate Mapping files exporter (<hbm2hbmxml>)</title> - <para><code><hbm2hbmxml></code> generates a set of .hbm files. Intended to be used together with a - <code><jdbcconfiguration></code> - when performing reverse engineering, but can be used with any kind of - configuration. e.g. to convert from annotation based pojo's to <emphasis> - <property>hbm.xml</property>. </emphasis></para> + <para> + <code><hbm2hbmxml></code> generates a set of <filename>.hbm</filename> files. It is intended to be used together with a <code><jdbcconfiguration></code> when performing reverse engineering, but can be used with any kind of configuration e.g. to convert from annotation based POJO's to a <filename>hbm.xml</filename> file. + </para> <note> <title>Note:</title> - <para>Not every possible mapping transformation is possible/implemented (contributions - welcome) so some hand editing might be necessary.</para> + <para> + Not every possible mapping transformation is possible/implemented (contributions welcome) so some hand editing might be required. + </para> </note> <programlisting role="XML"><![CDATA[<hbm2hbmxml/>]]></programlisting> @@ -978,15 +907,13 @@ <hbm2hbmxml/> </hibernatetool>]]></programlisting> - <para><code><hbm2hbmxml></code> is normally used with a <code><jdbcconfiguration></code> like in the above example, but any other configuration can also be used to - convert between the different ways of performing mappings. Here is an example of that, - using an <code><annotationconfiguration></code> - .</para> + <para> + <code><hbm2hbmxml></code> is normally used with a <code><jdbcconfiguration></code> like in the above example, but any other configuration can also be used to convert between the different ways of performing mappings. Here is an example of that, using an <code><annotationconfiguration></code>. + </para> <note> <title>Note:</title> - <para>Not all conversions are implemented (contributions welcome), so some hand editing - might be necessary.</para> + <para>Not all conversions are implemented (contributions welcome), so some hand editing might be necessary.</para> </note> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> @@ -999,10 +926,9 @@ <section> <title>Hibernate Configuration file exporter (<hbm2cfgxml>)</title> - <para><code><hbm2cfgxml></code> generates a <emphasis> - <property>hibernate.cfg.xml</property>. </emphasis> Intended to be used together with a <code><jdbcconfiguration></code> - when performing reverse engineering, but it can be used with any kind of - configuration. The <code><hbm2cfgxml></code> will contain the properties used and adds mapping entries for each mapped class.</para> + <para> + <code><hbm2cfgxml></code> generates a <filename>hibernate.cfg.xml</filename> file. It is intended to be used together with a <code><jdbcconfiguration></code> when performing reverse engineering, but it can be used with any kind of configuration. The <code><hbm2cfgxml></code> will contain the properties that are used and adds mapping entries for each mapped class. + </para> <programlisting role="XML"><![CDATA[<hbm2cfgxml ejb3="true|false" @@ -1039,8 +965,9 @@ </entry> <entry> - <para>The generated cfg.xml will have <mapping class=".."/>, opposed - to <mapping resource="..."/> for each mapping.</para> + <para> + The generated <filename>cfg.xml</filename> will have <mapping class=".."/>, opposed to <mapping resource="..."/> for each mapping. + </para> </entry> <entry> @@ -1058,8 +985,7 @@ <section> <title>Documentation exporter (<hbm2doc>)</title> - <para><code><hbm2doc></code> - generates html documentation a'la javadoc for the database schema et.al.</para> + <para><code><hbm2doc></code> generates HTML documentation similar to Javadoc for the database schema et.al.</para> <programlisting role="XML"><![CDATA[<hbm2doc/>]]></programlisting> </section> @@ -1067,8 +993,9 @@ <section> <title>Query exporter (<query>)</title> - <para><code><query></code> is used to execute a HQL query statements and optionally sends the output to a - file. It can be used for verifying the mappings and for basic data extraction.</para> + <para> + <code><query></code> is used to execute HQL query statements and optionally redirects the output to a file. It can be used for verifying the mappings and for basic data extraction. + </para> <programlisting role="XML"><![CDATA[<query destfile="filename"> @@ -1076,30 +1003,31 @@ </query> ]]></programlisting> - <para>Currently one session is opened and used for all queries and the query is executed via - the list() method. In the future more options might become available, like performing - executeUpdate(), use named queries and etc.</para> + <para> + Currently one session is opened and used for all queries, which are executed via the <code>list()</code> method. In the future more options might become available, like executing <code>executeUpdate()</code>, use named queries and etc. + </para> <para/> <section> <title>Examples</title> - <para>The simplest usage of <code><query></code> will just execute the query without dumping to a file. This can be used to - verify that queries can actually be performed.</para> + <para> + The simplest usage of <code><query></code> will execute the query without dumping to a file. This can be used to verify that queries can be performed successfully. + </para> <programlisting role="XML"><![CDATA[<hibernatetool> <configuration configurationfile="hibernate.cfg.xml"/> <query>from java.lang.Object</query> </hibernatetool>]]></programlisting> - <para>Multiple queries can be executed by nested <code><hql></code> elements. - In this example we also let the output be dumped to <emphasis> - <property>queryresult.txt</property>. </emphasis></para> + <para> + Multiple queries can be executed by nested <code><hql></code> elements. In this example we also let the output be dumped to the <filename>queryresult.txt</filename> file. + </para> <note> <title>Note:</title> - <para> Currently the dump is simply a call to toString on each element.</para> + <para> Currently the dump is performed by calling the <code>toString()</code> function on each element.</para> </note> <programlisting role="XML"><![CDATA[<hibernatetool> @@ -1115,7 +1043,7 @@ <section id="hbmtemplate"> <title>Generic Hibernate metamodel exporter (<hbmtemplate>)</title> - <para>Generic exporter that can be controlled by a user provides a template or class.</para> + <para>Below is an example of a generic exporter that can be controlled by a user provided template or class.</para> <programlisting role="XML"><![CDATA[<hbmtemplate filepattern="{package-name}/{class-name}.ftl" @@ -1125,16 +1053,16 @@ <note> <title>Note:</title> - <para>Previous versions of the tools used Velocity. We are now using Freemarker which - provides us much better exception and error handling.</para> + <para>Previous versions of the tools used <productname>Velocity</productname>. We are now using <productname>Freemarker</productname>, which provides much better exception and error handling. + </para> </note> <section> <title>Exporter via <hbmtemplate></title> - <para>The following is an example of reverse engineering via - <code><jdbcconfiguration></code> and usage of a custom Exporter via the - <code><hbmtemplate></code>.</para> + <para> + The following is an example of reverse engineering via a <code><jdbcconfiguration></code> tag and the use of a custom Exporter via the <code><hbmtemplate></code> tag. + </para> <programlisting role="XML"><![CDATA[ <hibernatetool destdir="${destdir}"> <jdbcconfiguration @@ -1156,11 +1084,9 @@ <section> <title>Relevant Resources Links</title> - <para>Read more about <ulink url="http://velocity.apache.org/">Velocity</ulink> and <ulink - url="http://freemarker.org/">Freemarker</ulink> to find out why using the last is better - or refer to Max Andersen discussion on the topic in <ulink - url="http://in.relation.to/2110.lace;jsessionid=3462F47B17556604C15DF1B96572E940" - >"A story about FreeMarker and Velocity"</ulink>.</para> + <para> + You can read more about <ulink url="http://velocity.apache.org/">Velocity</ulink> and <ulink url="http://freemarker.org/">Freemarker</ulink> to find out why using the latter is better or refer to Max Andersens discussion on the topic in <ulink url="http://in.relation.to/2110.lace;jsessionid=3462F47B17556604C15DF1B96572E940">"A story about FreeMarker and Velocity"</ulink>. + </para> </section> </section> </section> @@ -1170,57 +1096,44 @@ <section> <title>Using properties to configure Exporters</title> - <para>Exporters can be controlled by user properties. The user properties are specified via - <code><property></code> - or - <code><propertyset></code> - and each exporter will have access to them directly in the templates and via - <property>Exporter.setProperties()</property>.</para> + <para> + Exporters can be controlled by user properties. These user properties are specified via a <code><property></code> or <code><propertyset></code> tag, and each exporter will have access to them directly in the templates and via <code>Exporter.setProperties()</code>. + </para> <section> - <title><property> and - <propertyset></title> + <title><property> and <propertyset></title> - <para>The <code><property></code> - allows you bind a string value to a key. The value will be available in the - templates via <code>$<key></code>. - The following example will assign the string value - <code>"true"</code> - to the variable - <code>$descriptors</code> - .</para> + <para> + The <code><property></code> tag allows you bind a string value to a key. The value will be available in the templates via the <code>$<key></code> tag. The following example will assign the string value <code>"true"</code> to the variable <code>$descriptors</code>. + </para> <programlisting role="XML"><![CDATA[<property key="descriptors" value="true"/>]]></programlisting> - <para>Most times using <code><property></code> is enough for specifying the properties needed for the exporters. Still the ant - tools supports the notion of <code><propertyset></code> that is used for grouping a set of properties. More about the functionality of <code><propertyset></code> - is explained in detail in the <ulink url="http://ant.apache.org/manual/">Ant - manual</ulink>.</para> + <para> + Usually using the <code><property></code> tag is enough when specifying the properties required by the exporters. Still, the Ant tools supports the notion of a <code><propertyset></code> which is used for grouping a set of properties. More about the functionality of <code><propertyset></code> is can be found in the <ulink url="http://ant.apache.org/manual/">Ant manual</ulink>. + </para> </section> <section> <title>Getting access to user specific classes</title> - <para>If the templates need to access some user class it becomes possible by specifying a <code> - "toolclass"</code> in the properties.</para> + <para>It is possible for the templates to access user classes by specifying a <code>"toolclass"</code> in the properties.</para> - <programlisting role="XML"><![CDATA[<property key="hibernatetool.sometool.toolclass" value="x.y.z.NameOfToolClass"/> -]]></programlisting> + <programlisting role="XML"><![CDATA[<property key="hibernatetool.sometool.toolclass" value="x.y.z.NameOfToolClass"/>]]></programlisting> - <para>Placing the above <code><property></code> tag in <code><hibernatetool></code> - or inside any exporter will automatically create an instance of - <literal>x.y.z.NameOfToolClass</literal> and it will be available in the templates as - <literal>$sometool</literal>. This is useful to delegate logic and code generation to java - code instead of placing such logic in the templates.</para> + <para> + Placing the above <code><property></code> tag in the <code><hibernatetool></code> tag or inside any exporter will automatically create an instance of <code>x.y.z.NameOfToolClass</code> which will be available in the templates as <code>$sometool</code>. This is useful to delegate logic and code generation to Java code instead of placing such logic in the templates. + </para> <section> <title>Example</title> - <para>Here is an example that uses <code><hbmtemplate></code> - together with <code><property></code> which will be available to the templates/exporter. </para> + <para> + Here is an example that uses the <code><hbmtemplate></code> tag together with the <code><property></code> tag, which will be available to the templates and exporter. + </para> <note> <title>Note:</title> - <para> This example actually simulates what <code><hbm2java></code> actually does.</para> + <para> This example actually simulates what the <code><hbm2java></code> tag does.</para> </note> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/codegen.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/codegen.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/codegen.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -2,28 +2,22 @@ <chapter id="codegen"> <title>Controlling POJO code generation</title> - <para>When using <code><hbm2java></code> or the eclipse plugin to generate POJO java code you have the possibility to control - certain aspects of the code generation. This is primarily done with the <code><meta></code> - tag in the mapping files. The following section describes the possible <code> - <meta> - </code> tags and their use.</para> + <para> + When using the <code><hbm2java></code> tag or the Eclipse plugin to generate POJO Java code you have the ability to control certain aspects of the code generation process. This is primarily done with the <code><meta></code> tag in the mapping files. The following section describes the possible <code><meta></code> tags and their use. + </para> <section> <title>The <meta> attribute</title> - <para>The <code><meta></code> tag is a simple way of annotating the <emphasis> - <property>hbm.xml</property> - </emphasis> with information, so tools have a natural place to store/read information that is - not directly related to the Hibernate core.</para> + <para> + The <code><meta></code> tag is a simple way of annotating the <filename>hbm.xml</filename> file with information, so tools have a natural place to store and read information that is not directly related to the Hibernate core. + </para> - <para>You can use the <code><meta></code> tag to e.g. tell <code><hbm2java></code> - to only generate <emphasis> - <property>"protected"</property> - </emphasis> setters, have classes always implement a certain set of interfaces or even have - them extend a certain base class and even more.</para> + <para> + As an example, you can use the <code><meta></code> tag to tell the <code><hbm2java></code> tag to only generate <code>"protected"</code> setters, have classes always implement a certain set of interfaces, have them extend a certain base class and more. + </para> - <para>The following example shows how to use various <code><meta></code> - attributes and the resulting java code.</para> + <para>The following example shows how to use various <code><meta></code> attributes and the resulting Java code.</para> <programlisting role="XML"><![CDATA[<class name="Person"> <meta attribute="class-description"> @@ -40,10 +34,9 @@ </property> </class>]]></programlisting> - <para>The above <emphasis> - <property>hbm.xml</property> - </emphasis> will produce something like the following (code shortened for better - understanding). Notice the Javadoc comment and the protected set methods:</para> + <para> + The above <filename>hbm.xml</filename> file will produce something like the following (the code has been abbreviated for clarity). Notice the Javadoc comment and the protected set methods: + </para> <programlisting role="JAVA"><![CDATA[// default package @@ -112,7 +105,7 @@ <literal>class-description</literal> </entry> - <entry>inserted into the javadoc for classes</entry> + <entry>inserted into the Javadoc for classes</entry> </row> <row> @@ -120,7 +113,7 @@ <literal>field-description</literal> </entry> - <entry>inserted into the javadoc for fields/properties</entry> + <entry>inserted into the Javadoc for fields and properties</entry> </row> <row> @@ -192,7 +185,7 @@ <literal>default-value</literal> </entry> - <entry>default initialization value for a field</entry> + <entry>Default initialization value for a field.</entry> </row> <row> @@ -200,7 +193,7 @@ <literal>use-in-tostring</literal> </entry> - <entry>include this property in the <literal>toString()</literal></entry> + <entry>Include this property in the <code>toString()</code> method.</entry> </row> <row> @@ -208,9 +201,9 @@ <literal>use-in-equals</literal> </entry> - <entry>include this property in the <literal>equals()</literal> and - <literal>hashCode()</literal> method. If no use-in-equals is specified, no - equals/hashcode will be generated.</entry> + <entry> + Include this property in the <code>equals()</code> and <code>hashCode()</code> methods. If no use-in-equals is specified, no equals or hashcode method will be generated. + </entry> </row> <row> @@ -218,7 +211,7 @@ <literal>gen-property</literal> </entry> - <entry>property will not be generated if false (use with care)</entry> + <entry>Property will not be generated if false (use with care).</entry> </row> <row> @@ -226,8 +219,7 @@ <literal>property-type</literal> </entry> - <entry>Overrides the default type of property. Use this with any tag's to specify the - concrete type instead of just Object.</entry> + <entry>Overrides the default type of property. Use this with any tag's to specify the concrete type instead of just <code>Object</code>.</entry> </row> <row> @@ -249,56 +241,36 @@ </tgroup> </table> - <para>Attributes declared via the <code><meta></code> - tag are per default <emphasis> - <property>"inherited"</property> - </emphasis> inside an <emphasis> - <property>hbm.xml</property> - </emphasis> file.</para> + <para> + Attributes declared via the <code><meta></code> tag <code>"inherited"</code> inside an <code>hbm.xml</code> file by default. + </para> - <para>What does that mean? It means that if you e.g want to have all your classes implement - <property>IAuditable</property> then you just add an <code> <meta - attribute="implements">IAuditable</meta></code> in the top of the <emphasis> - <property>hbm.xml</property> - </emphasis> file, just after <code><hibernate-mapping></code>. Now all classes defined - in that <emphasis> - <property>hbm.xml</property> - </emphasis> file will implement <property>IAuditable</property>!</para> + <para> + What does that mean? As an example if you want to have all your classes implement <code>IAuditable</code> then you just add <code> <meta attribute="implements">IAuditable</meta></code> in the top of the <filename>hbm.xml</filename> file, just after <code><hibernate-mapping></code>. Now all classes defined in that <filename>hbm.xml</filename> file will implement <code>IAuditable</code>. + </para> <note> <title>Note:</title> - <para>This applies to <emphasis>all</emphasis> - <code><meta></code>-tags. Thus it can also e.g. be used to specify that - all fields should be declare protected, instead of the default private. This is done by - adding <code><meta - attribute="scope-field">protected</meta></code> at e.g. just under - the <code><class></code> tag and all fields of that class will be - protected.</para> + <para> + This applies to <emphasis>all</emphasis> <code><meta></code>-tags. Thus it can also be used to specify that all fields should be declare <code>protected</code>, instead of the default <code>private</code>. This is done by adding <code><meta attribute="scope-field">protected</meta></code> just under the <code><class></code> tag, and all fields of that class will be <code>protected</code>. + </para> </note> - <para>To avoid having a <code><meta></code> - tag inherited then you can simply specify <code> inherit = "false"</code> - for the attribute, e.g. <code> <meta attribute = "scope-class" inherit = - "false">public abstract</meta></code> will restrict the <emphasis> - <property>"class-scope"</property> - </emphasis> to the current class, not the subclasses.</para> + <para> + To avoid having a <code><meta></code> tag inherited then you can specify <code> inherit = "false"</code> for the attribute. For example <code> <meta attribute = "scope-class" inherit = "false">public abstract</meta></code> will restrict the <code>"class-scope"</code> to the current class, not the subclasses. + </para> <section> <title>Recommendations</title> - <para>The following are some good practices when using - <code><meta></code> - attributes.</para> + <para>The following are some good practices to employ when using <code><meta></code> attributes.</para> <section> - <title>Dangers of a class level <property>use-in-string and use-in-equals</property> meta - attributes when having bi-directional associations</title> + <title>Dangers of a class level <property>use-in-string and use-in-equals</property> meta attributes when using bi-directional associations</title> - <para>If we have two entities with a bi-directional association between them and define at - class scope level the meta attributes: <emphasis> - <property>use-in-string</property>, </emphasis> - <emphasis> - <property>use-in-equals</property>: </emphasis></para> + <para> + In the following example we have two entities with a bi-directional association between them and define the <code>use-in-string</code> and <code>use-in-equals</code> meta attributes at the class scope level the meta attributes: + </para> <programlisting role="XML"><![CDATA[<hibernate-mapping> <class name="Person"> @@ -308,9 +280,7 @@ </class> </hibernate-mapping>]]></programlisting> - <para>And for <emphasis> - <property>Event.hbm</property> - </emphasis> file:</para> + <para>Here is the <filename>Event.hbm</filename> file:</para> <programlisting role="XML"><![CDATA[<hibernate-mapping> <class name="events.Event" table="EVENTS"> @@ -328,21 +298,15 @@ </class> </hibernate-mapping>]]></programlisting> - <para>Then <code><hbm2java></code> - will assume you want to include all properties and collections in the - <code>toString()/equals()</code> methods and this can result in infinite - recursive calls.</para> + <para> + In this situation the <code><hbm2java></code> tag will assume you want to include all properties and collections in the <code>toString()</code> and <code>equals()</code> methods. This can result in infinite recursive calls. + </para> - <para>To remedy this you have to decide which side of the association will include the other - part (if at all) in the <code>toString()/equals()</code> methods. Therefore it is - not a good practice to put at class scope such <emphasis> - <property>meta</property> - </emphasis> attributes, unless you are defining a class without bi-directional - associations.</para> + <para> + To remedy this you have to decide which side of the association will include the other part (if at all) in the <code>toString()</code> and <code>equals()</code> methods. Therefore it is not a good practice to define these <code>meta</code> attributes at the class scope, unless you are defining a class without bi-directional associations. + </para> - <para>We recommend instead to add the <emphasis> - <property>meta</property> - </emphasis> attributes at the property level:</para> + <para>Instead it is recommended that the <code>meta</code> attributes are defined at the property level, like so:</para> <programlisting role="XML"><![CDATA[<hibernate-mapping> <class name="events.Event" table="EVENTS"> @@ -362,7 +326,7 @@ </class> </hibernate-mapping>]]></programlisting> - <para>and now for <property>Person</property>:</para> + <para>and for <code>Person</code>:</para> <programlisting role="XML"><![CDATA[<hibernate-mapping> <class name="Person"> @@ -385,70 +349,53 @@ </section> <section> - <title>Be aware of putting at class scope level <meta> - attributeuse-in-equals</title> + <title>Be aware of putting at class scope level <meta> attributeuse-in-equals</title> - <para>For <code>equal()/hashCode()</code> method generation, you have to take into - account that the attributes that participate on such method definition, should take into - account only attributes with business meaning (the name, social security number, etc, but - no generated id's, for example).</para> + <para> + Only attributes with business meaning (e.g. the name, social security number, etc, but no generated id's) should be referenced when calculating the return value for the <code>equal()</code> and <code>hashCode()</code> methods. + </para> - <para>This is important because Java's hashbased collections, such as - <property>java.util.Set</property> relies on <property>equals()</property> and - <property>hashcode()</property> to be correct and not change for objects in the set; - this can be a problem if the id gets assigned for an object after you inserted it into a - set.</para> + <para> + This is important because Java's hashbased collections, such as <code>java.util.Set</code>, rely on <code>equals()</code> and <code>hashcode()</code> being correct and not changing for objects in the set; this can be a problem if the id gets assigned for an object after you inserted it into a set. + </para> - <para>Therefore automatically configuration of the generation of - <property>equals()/hashCode()</property> methods specifying at class scope level the <code><meta></code> attribute <emphasis> - <property>use-in-equals</property> - </emphasis> could be a dangerous decision that could produce non expected - side-effect.</para> + <para> + Therefore automatically configuration of the generation of <code>equals()</code> and <code>hashCode()</code> methods specifying the <code><meta></code> attribute <code>use-in-equals</code> at class scope level could be a dangerous decision that could produce unexpected side-effects. + </para> - <para><ulink url="http://www.hibernate.org/109.html">On www.hibernate.org </ulink> you can get more in-depth - explanation on the subject of <property>equals()</property> and - <property>hashcode()</property>.</para> + <para> + On <ulink url="http://www.hibernate.org/109.html">www.hibernate.org </ulink> you can find more in-depth explanation on the subject of <code>equals()</code> and <code>hashcode()</code> methods. + </para> </section> </section> <section> <title>Advanced <meta> attribute examples</title> - <para>This section shows an example for using meta attributes (including userspecific - attributes) together with the code generation features in <property>Hibernate - Tools</property>.</para> + <para> + This section shows an example for using meta attributes (including user specific attributes) together with the code generation features in <productname>Hibernate Tools</productname>. + </para> - <para>The usecase being implemented is to automatically insert some pre- and post-conditions - into the getter and setters of the generated POJO. </para> + <para>The example shown below automatically inserts some pre and post conditions into the getter and setter methods of the generated POJO. </para> <section> <title>Generate pre/post-conditions for methods</title> - <para>With a <code> <meta attribute="class-code"></code>, you can add - additional methods on a given class, nevertheless such <code><meta></code> - attribute can not be used at a property scope level and <property>Hibernate - Tools</property> does not provide such <code> - ><meta> - </code> attributes.</para> + <para> + With <code> <meta attribute="class-code"></code> you can add additional methods on a given class. However, such <code><meta></code> attributes can not be used at a property scope level and <property>Hibernate Tools</property> does not provide such <code><meta></code> attributes. + </para> - <para>A possible solution for this is to modify the freemarker templates responsible for - generating the POJO's. If you look inside <emphasis> - <property>hibernate-tools.jar</property>, </emphasis> you can find the template: <emphasis> - <property>pojo/PojoPropertyAccessor.ftl</property> - </emphasis></para> + <para> + A possible solution for this is to modify the Freemarker templates responsible for generating the POJOs. If you look inside the <filename>hibernate-tools.jar</filename> archive, you can find the template <filename>pojo/PojoPropertyAccessor.ftl</filename>. + </para> - <para>This file is as the name indicates used to generate property accessors for - pojo's.</para> + <para>As its name indicates, this file is used to generate property accessors for POJOs.</para> - <para>Extract the <emphasis> - <property>PojoPropertyAccessor.ftl</property> - </emphasis> into a local folder i.e. <emphasis> - <property>${hbm.template.path}</property>, </emphasis> respecting the whole path, for - example: <emphasis> - <property>${hbm.template.path}/pojo/PojoPropertyAccessor.ftl</property> - </emphasis></para> + <para> + Extract the <filename>PojoPropertyAccessor.ftl</filename> file into a local folder e.g. <filename>${hbm.template.path}</filename>, respecting the whole path, for example: <filename>${hbm.template.path}/pojo/PojoPropertyAccessor.ftl</filename>. + </para> - <para>The contents of the file is something like this:</para> + <para>The contents of the file will be something like this:</para> <programlisting role="XML"><![CDATA[<#foreach property in pojo.getAllPropertiesIterator()> ${pojo.getPropertyGetModifiers(property)} @@ -464,8 +411,9 @@ } </#foreach>]]></programlisting> - <para>We can add conditionally pre/post-conditions on our <literal>set</literal> method - generation just adding a little Freemarker syntax to the above source code:</para> + <para> + We can add pre and post conditions on our <code>set</code> method generation just by adding a little Freemarker syntax to the above source code: + </para> <programlisting role="XML"><![CDATA[<#foreach property in pojo.getAllPropertiesIterator()> ${pojo.getPropertyGetModifiers(property)} @@ -489,19 +437,13 @@ </#foreach>]]> </programlisting> - <para>Now if in any <emphasis> - <property>.hbm.xml</property> - </emphasis> file we define the <emphasis> - <property><meta></property> - </emphasis> attributes: <code>pre-cond</code> or <code>post-cond</code>, their - contents will be generated into the body of the relevant <literal>set</literal> - method.</para> + <para> + Now if in any <filename>.hbm.xml</filename> file we define the <code><meta></code> attributes: <code>pre-cond</code> or <code>post-cond</code>, and their contents will be generated into the body of the relevant <code>set</code> method. + </para> - <para>As an example let us add a pre-condition for property <code>name</code> - preventing no <property>Person</property> can have an empty name. Hence we have to modify - the <emphasis> - <property>Person.hbm.xml</property> - </emphasis> file like this:</para> + <para> + As an example let us add a pre-condition for the <code>name</code> property which will prevent the <code>Person</code> class from having an empty name. To achieve this we have to modify the <filename>Person.hbm.xml</filename> file like so: + </para> <programlisting role="XML"><![CDATA[<hibernate-mapping> <class name="Person"> @@ -520,18 +462,15 @@ <note> <title>Note:</title> - <para>I) To escape the & symbol we put &amp;. You can use - <code> <![CDATA[]]></code> instead.</para> - <para>II) Note that we are referring to "firstName" directly and this is the parameter - name not the actual field name. If you want to refer the field you have to use - "this.firstName" instead. </para> + <para>I) To escape the <code>&</code> symbol we put <code>&</code><code>amp</code><code>;</code>. You could use <code> <![CDATA[]]></code> instead.</para> + <para> + II) Note that we are referring to <code>firstName</code> directly and this is the parameter name not the actual field name. If you want to refer the field you have to use <code>this.firstName</code> instead. + </para> </note> - <para>Finally we have to generate the <emphasis> - <property>Person.java</property> - </emphasis> class, for this we can use both Eclipse and Ant as long as you remember to set - or fill in the templatepath setting. For Ant we configure <code><hibernatetool></code> - task via <literal>the templatepath</literal> attribute as in:</para> + <para> + Finally we have to generate the <filename>Person.java</filename> class. For this we can use either Eclipse or Ant, as long as you remember to set or fill in the <code>templatepath</code> setting. For Ant we configure the <code><hibernatetool></code> task via the <code>templatepath</code> attribute as in: + </para> <programlisting role="XML"><![CDATA[ <target name="hbm2java"> @@ -552,12 +491,9 @@ </hibernatetool> </target>]]></programlisting> - <para>Invoking the target <code><hbm2java></code> - will generate on the <emphasis> - <property>${hbm2java.dest.dir}</property> - </emphasis> the file <emphasis> - <property>Person.java</property> - </emphasis>:</para> + <para> + Invoking the target <code><hbm2java></code> will generate file <filename>Person.java</filename> in <filename>${hbm2java.dest.dir}</filename>: + </para> <programlisting role="JAVA"><![CDATA[// default package import java.io.Serializable; @@ -594,22 +530,19 @@ } }]]></programlisting> - <para>In conclusion, this document is intended to introduce you to Hibernate plugin specific - features related to tools bath for the Eclipse and Ant tasks.</para> + <para> + In conclusion, this document is intended to introduce you to Hibernate plugin specific features related to tools both for the Eclipse and Ant tasks. + </para> - <para>In the <xref linkend="plugins"/> chapter you've learnt - about a set of wizards for creating Mapping files, Configuration file, Console - Configuration, got familiar with Mapping and Configuration files editors, tooling for - organizing and controlling Reverse Engineering, Hibernate Console and Mapping diagram as - well.</para> + <para> + In <xref linkend="plugins"/> you've learned about a set of wizards for creating Mapping files, Configuration files, Console Configurations, become familiar with Mapping and Configuration files editors, tooling for organizing and controlling Reverse Engineering, Hibernate Console and Mapping diagrams. + </para> - <para>The rest chapters have shown the aspects of using the <property>Hibernate - Tools</property> via Ant tasks.</para> + <para>The rest chapters have explored the use of the <productname>Hibernate Tools</productname> via Ant tasks.</para> - <para>Please, visit <ulink - url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss - Tools Users Forum</ulink> to leave questions or/and suggestions on the topic. Your - feedback is always appreciated.</para> + <para> + Please visit <ulink url="http://www.jboss.com/index.html?module=bb&op=viewforum&f=201">JBoss Tools Users Forum</ulink> to leave questions or/and suggestions on the topic. Your feedback is always appreciated. + </para> </section> </section> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/codegenarchitecture.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/codegenarchitecture.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/codegenarchitecture.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -1,112 +1,92 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="codegenarchitecture"> - <title>Code generation architecture</title> + <title>Code generation architecture</title> - <para>The code generation mechanism in the <property>Hibernate Tools</property> consists of a few - core concepts. This section explains their overall structure which are the same for the Ant and - Eclipse tools.</para> + <para> + The code generation mechanism in <productname>Hibernate Tools</productname> consists of a few core concepts. This section explains their overall structure, which is the same for the <productname>Ant</productname> and <productname>Eclipse</productname> tools. + </para> - <section> - <title>Hibernate Meta Model</title> + <section> + <title>Hibernate Meta Model</title> - <para>The meta model is the model used by Hibernate Core to perform its object relational - mapping. The model includes information about tables, columns, classes, properties, - components, values, collections etc. The API is in <literal>org.hibernate.mapping</literal> - and its main entry point is the <property>Configuration</property> class, the same class that is - used to build a session factory.</para> + <para> + The meta model is the model used by <productname>Hibernate Core</productname> to perform its object relational mapping. The model includes information about tables, columns, classes, properties, components, values, collections etc. The API is in the <code>org.hibernate.mapping</code> package and its main entry point is the <code>Configuration</code> class: the same class that is used to build a session factory. + </para> - <para>The model represented by the <property>Configuration</property> class can be build in many - ways. The following list the currently supported ones in <property>Hibernate Tools</property>. </para> + <para> + The model represented by the <code>Configuration</code> class can be built in many ways: + </para> - <para> - <itemizedlist> - <listitem> - <para>A Core configuration uses Hibernate Core and supports reading <emphasis> - <property>hbm.xml</property> - </emphasis> files, requires a <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis>. Named core in Eclipse and - <code><configuration></code> - in ant.</para> - </listitem> + <para> + <itemizedlist> + <listitem> + <para> + A Core configuration uses <productname>Hibernate Core</productname> and supports reading <filename>hbm.xml</filename> files, and requires a <filename>hibernate.cfg.xml</filename> file. This is referred to as <emphasis>Core</emphasis> in Eclipse and <code><configuration></code> in Ant. + </para> + </listitem> - <listitem> - <para>An Annotation configuration uses Hibernate Annotations and supports <emphasis> - <property>hbm.xml</property> - </emphasis> and annotated classes, requires a <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis>. Named annotations in Eclipse and - <code><annotationconfiguration></code> - in ant.</para> - </listitem> + <listitem> + <para> + An Annotation configuration uses <productname>Hibernate Annotations</productname>, supports <filename>hbm.xml</filename> files and annotated classes, and requires a <filename>hibernate.cfg.xml</filename> file. This is referred to as <emphasis>Annotations</emphasis> in Eclipse and <code><annotationconfiguration></code> in Ant.</para> + </listitem> - <listitem> - <para>A JPA configuration uses a Hibernate EntityManager and supports <emphasis> - <property>hbm.xml</property> - </emphasis> and annotated classes requires that the project has a <emphasis> - <property>META-INF/persistence.xml</property> - </emphasis> in its classpath. Named JPA in Eclipse and - <code><jpaconfiguration></code> - in ant.</para> - </listitem> + <listitem> + <para> + A JPA configuration uses a <productname>Hibernate EntityManager</productname> and supports <filename>hbm.xml</filename> files and annotated classes, and requires that the project has a <filename>META-INF/persistence.xml</filename> file in its classpath. This is referred to as <emphasis>JPA</emphasis> in Eclipse and <code><jpaconfiguration></code> in Ant.</para> + </listitem> - <listitem> - <para>A JDBC configuration uses <property>Hibernate Tools</property> reverse engineering - and reads its mappings via JDBC metadata + additional reverse engineering files - (reveng.xml). Automatically used in Eclipse when doing reverse engineering from JDBC and - named - <code><jdbcconfiguration></code> - in ant.</para> - </listitem> - </itemizedlist> - </para> + <listitem> + <para> + A JDBC configuration uses <property>Hibernate Tools</property> reverse engineering and reads its mappings via JDBC metadata + additional reverse engineering files (<filename>reveng.xml</filename>). Automatically used in Eclipse when doing reverse engineering from JDBC and referred to as <code><jdbcconfiguration></code> in Ant.</para> + </listitem> + </itemizedlist> + </para> - <para>In most projects you will normally use only one of the Core, Annotation or JPA - configuration and possibly the JDBC configuration if you are using the reverse engineering - facilities of <property>Hibernate Tools</property>. </para> + <para> + In most projects you will normally use only one of the <emphasis>Core</emphasis>, <emphasis>Annotation</emphasis> or <emphasis>JPA</emphasis> configuration and possibly the JDBC configuration if you are using the reverse engineering facilities of <productname>Hibernate Tools</productname>. + </para> - <note> - <title>Note:</title> - <para>No matter which Hibernate Configuration type you are using <property>Hibernate - Tools</property> supports them.</para> - </note> + <note> + <title>Note:</title> + <para>Hibernate Tools has support for all kinds of Hibernate Configurations.</para> + </note> - <para>The following drawing illustrates the core concepts:</para> + <para>The following drawing illustrates the core concepts:</para> - <para> - <figure> - <title>Hibernate Core Concepts</title> - <mediaobject> - <imageobject role="fo"> - <imagedata fileref="images/code_generation/code_generation_1.png" format="PNG"/> - </imageobject> + <para> + <figure> + <title>Hibernate Core Concepts</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="images/code_generation/code_generation_1.png" format="PNG"/> + </imageobject> - <imageobject role="html"> + <imageobject role="html"> - <imagedata align="center" fileref="images/code_generation/code_generation_1.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - </para> + <imagedata align="center" fileref="images/code_generation/code_generation_1.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + </para> - <para>The code generation is done based on the Configuration model no matter which type of - configuration have been used to create the meta model, and thus the code generation is - independent on the source of the meta model and represented via Exporters.</para> - </section> + <para> + The code generation is performed based on the Configuration model no matter which type of configuration has been used to create the meta model, and thus the code generation is independent on the source of the meta model and represented via Exporters. + </para> + </section> - <section> - <title>Exporters</title> + <section> + <title>Exporters</title> - <para>Code generation is done in so called Exporters. An <code>Exporter</code> is handed a - Hibernate Meta Model represented as a <code>Configuration</code> instance and it is then - the job of the exporter to generate a set of code artifacts.</para> + <para> + Code generation is performed by an Exporters. An <emphasis>Exporter</emphasis> is handed a Hibernate Meta Model represented as a <code>Configuration</code> instance, and it is then the job of the exporter to generate a set of code artifacts. + </para> - <para>The tools provides a default set of Exporter's which can be used in both Ant and the - Eclipse UI. Documentation for these Exporters is in the <xref linkend="ant"/> - and <xref linkend="plugins"/> chapters.</para> + <para> + The tool provides a default set of Exporter's which can be used in both Ant and the Eclipse UI. Documentation for these Exporters can be found in <xref linkend="ant"/> and <xref linkend="plugins"/>. + </para> - <para>Users can provide their own customer Exporter's, either by custom classes implementing the - Exporter interface or simply be providing custom templates. This is documented at <xref - linkend="hbmtemplate"/></para> - </section> + <para> + Users can provide their own custom Exporter's, either through custom classes implementing the <code>Exporter</code> interface or simply through custom templates. This is documented at in <xref linkend="hbmtemplate"/>. + </para> + </section> </chapter> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property1.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property3.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property4.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/add_property5.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/annotations1.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/annotations1_a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/annotations2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/annotations3.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration1.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration10.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration11.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration3.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration4.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration5.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration7.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/dali_integration9.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/diagram1.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/diagram2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/diagramToolbar.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/map_diagram1.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/map_diagram2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/map_diagram3.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_0.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_0_a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_0_b.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_1.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_12.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_12_a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_12_b.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_13.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_14.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_15.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_16.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_17.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_17_a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_18.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_18_a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_18_b.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_18_g.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_19.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_19_b.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_19_c.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_19_d.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_2.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_20.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_21_a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_21_b.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_22.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_2_a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_3.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_4_a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_4_b.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_4_c.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_4_d.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_5.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_6.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_7.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_8.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_8a.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_8b.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/plugins_9.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/prototypingQueries.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/images/plugins/saveDiagram.png =================================================================== (Binary files differ) Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/introduction.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/introduction.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/introduction.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -1,163 +1,166 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="introduction"> - <title>Introduction</title> + <title>Introduction</title> - <para><property>Hibernate Tools</property> is a toolset for <ulink - url="http://www.hibernate.org/6.html">Hibernate 3</ulink> and <ulink - url="http://www.hibernate.org/27.html">related projects</ulink>. The tools provide Ant + <para> + <property>Hibernate Tools</property> is a collection of tools for <ulink url="http://www.hibernate.org/">Hibernate 3</ulink> and related projects. The tools provide Ant tasks and Eclipse plugins for performing reverse engineering, code generation, visualization and interaction with Hibernate.</para> - <section id="hibernate_key_features"> - <title>Key Features</title> + <section id="hibernate_key_features"> + <title>Key Features</title> - <para>First, we propose to look through the list of key features that you can benefit from - if you start using <property>Hibernate Tools</property>.</para> + <para>The table below lists the key features found in <property>Hibernate Tools</property>.</para> - <table> - <title>Key Functionality for Hibernate Tools</title> - <tgroup cols="3"> - - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="5*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - - <thead> - <row> - <entry>Feature</entry> - <entry>Benefit</entry> - <entry>Chapter</entry> - </row> - </thead> + <table> + <title>Key Functionality for Hibernate Tools</title> + <tgroup cols="3"> - <tbody> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="5*"/> + <colspec colnum="3" align="left" colwidth="1*"/> - <row> - <entry> - <para>Code Generation through Ant Task</para> - </entry> - <entry> - <para>Allows to execute mapping or Java code generation from reverse - engineering, schema generation and generation of other artifacts - during the build process.</para> - </entry> - <entry><xref linkend="ant"/></entry> - </row> + <thead> + <row> + <entry>Feature</entry> + <entry>Benefit</entry> + <entry>Chapter</entry> + </row> + </thead> - <row> - <entry> - <para>Wizards for creation - purposes and code - generation</para> - </entry> - <entry> - <para> A set of wizards are provided with the Hibernate Eclipse tools to - quickly create common Hibernate files such as configuration - (cfg.xml) files, mapping files and revenge.xml as well. Code - Generation wizard helps to generate a series of various artifacts, - there is even support for completely reverse engineer an existing - database schema.</para> - </entry> - <entry> <xref linkend="map_file_wizard"/> - <xref linkend="hib_config_file"/> - <xref linkend="code_gen"/> - </entry> - </row> + <tbody> + <row> + <entry> + <para>Code Generation through Ant Task</para> + </entry> + <entry> + <para> + Allows to generate mapping or Java code through reverse engineering, schema generation and generation of other artifacts during the build process. + </para> + </entry> + <entry> + <xref linkend="ant"/> + </entry> + </row> - <row> - <entry> - <para> - Mapping and Configuration files - Editors - </para> - </entry> - <entry> - <para>Support auto-completion and syntax highlighting. Editors also - support semantic auto-completion for class names and property/field - names, making it much more versatile than a normal XML - editor.</para> - </entry> - <entry> <xref linkend="map_config_editor"/></entry> - </row> + <row> + <entry> + <para>Wizards for creation purposes and code generation</para> + </entry> + <entry> + <para> + A set of wizards are provided with the <productname>Hibernate Eclipse Tools</productname> to quickly create common <productname>Hibernate</productname> files such as configuration (<filename>cfg.xml</filename>) files, mapping files and <filename>reveng.xml</filename> as well. The Code Generation wizard helps by generating a series of various artifacts, and there is even support for completely reverse engineering an existing database schema. + </para> + </entry> + <entry> + <xref linkend="map_file_wizard"/> + <xref linkend="hib_config_file"/> + <xref linkend="code_gen"/> + </entry> + </row> - <row> - <entry> - <para>Tools for organizing and controlling Reverse Engineering</para> - </entry> - <entry> - <para>Code Generation wizard provides powerful functionality for - generating a series of various artifacts like domain model classes, - mapping files, annotated EJB3 entity beans, etc. and reveng.xml file - editor allows to control this processes.</para> - </entry> - <entry><xref linkend="code_gen"/> - <xref linkend="rev_xml_editor"/></entry> - </row> - <row> - <entry> - <para>Hibernate Console</para> - </entry> - <entry> - <para>It is a new perspective in Eclipse which provides an overview of - your Hibernate Console configurations, were you also can get an - interactive view of your persistent classes and their relationships. - The console allows you to execute HQL queries against your database - and browse the result directly in Eclipse.</para> - </entry> - <entry><xref linkend="hib_console"/></entry> - </row> + <row> + <entry> + <para>Mapping and Configuration files Editors</para> + </entry> + <entry> + <para> + Support auto-completion and syntax highlighting. Editors also support semantic auto-completion for class names and property/field names, making it much more versatile than a normal XML editor. + </para> + </entry> + <entry> + <xref linkend="map_config_editor"/> + </entry> + </row> + + <row> + <entry> + <para>Tools for organizing and controlling Reverse Engineering</para> + </entry> + <entry> + <para> + The Code Generation wizard provides powerful functionality for generating a series of various artifacts such as domain model classes, mapping files, and annotated EJB3 entity beans, and the <filename>reveng.xml</filename> file editor provides control over this processes. + </para> + </entry> + <entry> + <xref linkend="code_gen"/> + <xref linkend="rev_xml_editor"/> + </entry> + </row> + + <row> + <entry> + <para>Hibernate Console</para> + </entry> + <entry> + <para> + It is a new perspective in Eclipse which provides an overview of your Hibernate Console configurations, and were you also can get an interactive view of your persistent classes and their relationships. The console allows you to execute HQL queries against your database and browse the result directly in Eclipse. + </para> + </entry> + <entry> + <xref linkend="hib_console"/> + </entry> + </row> - <row> - <entry> - <para>HQL Editor and Hibernate Criteria Editor</para> - </entry> - <entry> - <para>The editors are intended for writing, editing and executing HQL queries and criterias. They also support the functionality for generating - simple queries.</para> - </entry> - <entry><xref linkend="hql_and_criteria_editors"/></entry> - </row> + <row> + <entry> + <para>HQL Editor and Hibernate Criteria Editor</para> + </entry> + <entry> + <para> + The editors are provided for writing, editing and executing HQL queries and criterias. They also have the ability to generate simple queries. + </para> + </entry> + <entry> + <xref linkend="hql_and_criteria_editors"/> + </entry> + </row> - <row> - <entry> - <para>Functional Mapping Diagram</para> - </entry> - <entry> - <para>Makes possible to visualize structure of entities and - relationships between them.</para> - </entry> - <entry><xref linkend="map_diagram"/></entry> - </row> + <row> + <entry> + <para>Functional Mapping Diagram</para> + </entry> + <entry> + <para>Makes possible to visualize the structure of entities and the relationships between them.</para> + </entry> + <entry> + <xref linkend="map_diagram"/> + </entry> + </row> - <row> - <entry> - <para>Eclipse JDT integration</para> - </entry> - <entry> - <para>Hibernate Tools integrates into the Java code completion and build - support of Java in Eclipse. This gives you code completion of HQL - inside Java code. Additionally, Hibernate Tools will add problem - markers if your queries are not valid against the console - configuration associated with the project.</para> - </entry> - </row> + <row> + <entry> + <para>Eclipse JDT integration</para> + </entry> + <entry> + <para> + <productname>Hibernate Tools</productname> integrates into the Java code completion and build support for Java in Eclipse. This gives you HQL code completion inside Java code. Additionally, <productname>Hibernate Tools</productname> will display problem markers if your queries are not valid against the console configuration associated with the project. + </para> + </entry> + </row> - </tbody> - </tgroup> - </table> - </section> - - <section> - <title>Other relevant resources on the topic</title> + </tbody> + </tgroup> + </table> + </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/tools</ulink> in the corresponding release directory.</para> - <para>There is some extra information about Hidernate on <ulink url="http://www.jboss.org/community/wiki/JBossHibernate3">JBoss Wiki page. </ulink></para> - <para>The latest documentation builds are available at <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">http://download.jboss.org/jbosstools/nightly-docs</ulink>.</para> - </section> + <para>The <productname>Hibernate Tools</productname> page on <ulink url="http://www.hibernate.org/subprojects/tools.html">hibernate.org</ulink>.</para> + <para> + All <productname>JBDS</productname> release documentation can be found on the <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/index.html">RedHat Documentation</ulink> website. + </para> + <para> + There is some additional information on <productname>Hibernate</productname> on the <ulink url="http://www.jboss.org/community/wiki/JBossHibernate3">JBoss Wiki</ulink> page. + </para> + <para> + Nightly documentation builds are available <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">here</ulink>. + </para> + </section> </chapter> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/master.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/master.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/master.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -60,12 +60,12 @@ </imageobject> </mediaobject> -<abstract> + </bookinfo> <toc/> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/plugins.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/plugins.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/plugins.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -1,2674 +1,2373 @@ <?xml version="1.0" encoding="UTF-8"?> <chapter id="plugins" role="updated"> - <title>Eclipse Plugins</title> - <para>This chapter will introduce you to the functionality that <property>Hibernate - Tools</property> provide within Eclipse. That is a set of wizards and editors for simplifying - the work with <property>Hibernate</property>.</para> - <section> - <title>Introduction</title> - <para>Hibernate Eclipse Tools include wizards for creating Hibernate mapping files, - configuration files (.cfg.xml), revenge.xml as well as wizards for adjusting Console - Configuration and Code Generation. Special structured and XML editors, editors for executing - HQL and Criteria queries are also provided in Hibernate Console. Refer to <xref - linkend="hibernate_key_features"/> section to find all benefits that you - can take advantage of while using the tools within Eclipse.</para> - <note> - <title>Note:</title> - <para>Please note that these tools do not try to hide any functionality of <property - >Hibernate</property>. The tools make working with <property>Hibernate</property> easier, - but you are still encouraged/required to read the <ulink - url="http://www.hibernate.org/5.html">Hibernate Documentation</ulink> to fully utilize - <property>Hibernate Tools</property> and especially <property>Hibernate</property> it - self.</para> - </note> - <section id="download_base_project"> - <title>Download base project</title> - <para>You can download example projects which are used for this chapter.</para> - <para><property>JPA base project</property> is available on <ulink - url="http://docs.jboss.org/tools/resources/">documentation resources page </ulink> - together with <ulink - url="http://docs.jboss.org/tools/resources/TestHibernateproject_for_hibernate_..." - >base Java project</ulink>.</para> - <para>Also you need start <ulink url="http://docs.jboss.org/tools/resources/GSG_database.zip" - >database</ulink>.</para> - <note> - <title>Note:</title> - <para>How to run database you can know in <ulink - url="http://docs.jboss.org/tools/3.0.1.GA/en/GettingStartedGuide/html/first_se..." - >Getting Started Guide</ulink>.</para> - </note> - </section> - </section> - <section id="map_file_wizard"> - <title>Creating a Hibernate Mapping File</title> - <para>Hibernate mapping files are used to specify how your objects are related to database - tables.</para> - <para>To create basic mappings for properties and associations, i. e. generate <emphasis> - <property>.hbm.xml</property> - </emphasis> files, Hibernate Tools provide a basic wizard which you can bring up by navigating - <emphasis> - <property>New > Hibernate XML mapping file</property>.</emphasis></para> - <para>At first you'll be asked to select a package or multiple individual classes to map. - It's also possible to create an empty file, don't select any packages or classes and an - empty .hbm will be created in the specified location</para> - <para id="depth_control">With <property>depth control</property> option you can define - dependences depth for choosing classes (it means to set level of references which is used to - collect linked classes to the selection). </para> - <figure> - <title>Hibernate XML Mapping File Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_0.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The next wizard page lists the mappings to be generated. As you see <property - >Customers</property>, <property>Orders</property>, <property>Productlines</property> and - <property>Products</property> classes added under <property>depth control</property> - driving. </para> - <figure> - <title>Mappings to be generated</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_0_a.png"/> - </imageobject> - </mediaobject> - </figure> - <para>This wizard page outputs a generated .hbm files preview.</para> - <figure> - <title>Preview Generated Mapping Files</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_0_b.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Pressing <property>Finish</property> creates the files.</para> - </section> - <section id="hib_config_file"> - <title>Creating a Hibernate Configuration File</title> - <para>To be able to reverse engineer, prototype queries, and of course to simply use <property - >Hibernate Core</property> a <emphasis> - <property>hibernate.properties</property> - </emphasis> or <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis> file is needed. The <property>Hibernate Tools</property> provide a wizard for - generating the <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis> file if you do not already have such one.</para> - <para>Start the wizard by clicking <emphasis> - <property>New > Other (Ctrl+N)</property> - </emphasis>, then <emphasis> - <property>Hibernate > Hibernate Configuration File (cfg.xml)</property> - </emphasis> and press <emphasis> - <property>Next</property> - </emphasis> or on a web Seam project in the <property>Web Projects</property> view <emphasis> - <property> WebContent -> New -> File -> Hibernate Configuration 3.0</property> - </emphasis>. After selecting the wanted location for the <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis> file, you will see the following page:</para> - <figure> - <title>Hibernate Configuration File Wizard</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" fileref="images/plugins/plugins_1.png" format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_1.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <note> - <title>Note:</title> - <para>The contents in the combo boxes for the JDBC driver class and JDBC URL change - automatically, depending on the Dialect and actual driver you have chosen.</para> - </note> - <para>Enter your configuration information in this dialog. Details about the configuration - options can be found in <ulink - url="http://docs.jboss.org/ejb3/app-server/Hibernate3/reference/en/html_single">Hibernate - Reference Documentation</ulink>.</para> - <para>Press <emphasis> - <property>Finish</property> - </emphasis> to create the configuration file, after optionally creating a Console - configuration, the <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis> will be automatically opened in an editor. The last option <emphasis> - <property>Create Console Configuration</property> - </emphasis> is enabled by default and when enabled, it will automatically use the <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis> for the basis of a Console configuration.</para> - </section> - <section id="console_conf"> - <title>Hibernate Console Configuration</title> - <para>A Console configuration describes how the <property>Hibernate plugin</property> should - configure <property>Hibernate</property> and what configuration files, including which - classpath are needed to load the POJO's, JDBC drivers etc. It is required to make usage of - query prototyping, reverse engineering and code generation. You can have multiple named - console configurations. Normally you would just need one per project, but more is definitely - possible if your project requires this.</para> - <section id="creat_console_conf"> - <title>Creating a Hibernate Console Configuration</title> - <para>You can create a console configuration by running the <property>Console Configuration - Wizard</property>, shown in the following screenshot. The same wizard will also be used if - you are coming from the <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis> wizard and had enabled <emphasis> - <property>Create Console Configuration</property> - </emphasis>.</para> - <note> - <title>Note:</title> - <para>The wizard will look at the current selection in the IDE and try and auto-detect the - settings which you then can just approve or modify to suit your needs.</para> - </note> - <para/> - <para>The dialog consists of five tabs: </para> - <itemizedlist> - <listitem> - <para><emphasis> - <property>Main</property> - </emphasis> for the basic/required settings</para> - </listitem> - </itemizedlist> - <figure> - <title> Creating Hibernate Console Configuration</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" fileref="images/plugins/plugins_2.png" format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_2.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>The following table describes the available settings on the <emphasis> - <property>Main</property> - </emphasis> tab. The wizard can automatically detect the default values for most of them if - you started the wizard with the relevant java project or resource selected.</para> - <table> - <title>Hibernate Console Configuration Parameters</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - <thead> - <row> - <entry align="center"> - <para>Parameter</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - <entry align="center"> - <para>Auto detected value</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para>Name</para> - </entry> - <entry> - <para>The unique name of the console configuration</para> - </entry> - <entry> - <para>Name of the selected project</para> - </entry> - </row> - <row> - <entry> - <para>Type</para> - </entry> - <entry> - <para>Choose between "Core", "Annotations" and "JPA". - Note that the two latter requires running Eclipse IDE with a JDK 5 runtime, - otherwise you will get classloading and/or version errors.</para> - </entry> - <entry> - <para>No default value</para> - </entry> - </row> - <row> - <entry> - <para>Project</para> - </entry> - <entry> - <para>The name of a java project which classpath should be used in the console - configuration</para> - </entry> - <entry> - <para>Name of the selected project</para> - </entry> - </row> - <row> - <entry> - <para>Database connection</para> - </entry> - <entry> - <para>DTP provided connection that you can use instead of what is in cfg.xml and jpa - persistence.xml. It's possible to use either already configured hibernate or - JPA connection or specify a new one here.</para> - </entry> - <entry> - <para>[Hibernate Configured connection]</para> - </entry> - </row> - <row> - <entry> - <para>Property file</para> - </entry> - <entry> - <para>Path to a hibernate.properties file</para> - </entry> - <entry> - <para>First hibernate.properties file found in the selected project</para> - </entry> - </row> - <row> - <entry> - <para>Configuration file</para> - </entry> - <entry> - <para>Path to a hibernate.cfg.xml file</para> - </entry> - <entry> - <para>First hibernate.cfg.xml file found in the selected project</para> - </entry> - </row> - <row> - <entry> - <para>Persistence unit</para> - </entry> - <entry> - <para>Name of the persistence unit to use</para> - </entry> - <entry> - <para>No default value (let Hibernate Entity Manager find the persistence unit or it - can be defined manually using Browse button)</para> - </entry> - </row> - </tbody> - </tgroup> - </table> - <note> - <title>Tip:</title> - <para>The two latter settings are usually not required if you specify a project and it has - <emphasis> - <property> - <literal> /hibernate.cfg.xml </literal> - </property> - </emphasis> or <emphasis> - <property> - <literal>/META-INF/persistence.xml</literal> - </property> - </emphasis> in its project classpath.</para> - </note> - <itemizedlist> - <listitem> - <para> - <emphasis> - <property>Options</property> - </emphasis> for the additional/optional settings</para> - </listitem> - </itemizedlist> - <figure> - <title>Options Tab of the Console Configuration Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_2_a.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The next table describes Hibernate Console Configuration options available on the - <emphasis> - <property>Options</property> - </emphasis> tab.</para> - <table> - <title>Hibernate Console Configuration Options</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - <thead> - <row> - <entry align="center"> - <para>Parameter</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - <entry align="center"> - <para>Auto detected value</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para>Database dialect</para> - </entry> - <entry> - <para>Define a database dialect. It's possible either to write your value or - choose from list. </para> - </entry> - <entry> - <para>No default value</para> - </entry> - </row> - <row> - <entry> - <para>Naming strategy</para> - </entry> - <entry> - <para>Fully qualified classname of a custom NamingStrategy. Only required if you use - a special naming strategy.</para> - </entry> - <entry> - <para>No default value</para> - </entry> - </row> - <row> - <entry> - <para>Entity resolver</para> - </entry> - <entry> - <para>Fully qualified classname of a custom EntityResolver. Only required if you - have special xml entity includes in your mapping files.</para> - </entry> - <entry> - <para>No default value</para> - </entry> - </row> - </tbody> - </tgroup> - </table> - <itemizedlist> - <listitem> - <para><emphasis> - <property>Classpath</property> - </emphasis> for classpath</para> - </listitem> - </itemizedlist> - <figure> - <title>Specifying Classpath in Hibernate Console Configuration</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" fileref="images/plugins/plugins_3.png" format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_3.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>The following table specifies the parameters of the Classpath tab of the wizard.</para> - <table> - <title>Hibernate Console Configuration Classpath</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - <colspec colnum="3" colwidth="1*"/> - <thead> - <row> - <entry align="center"> - <para>Parameter</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - <entry align="center"> - <para>Auto detected value</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para>Classpath</para> - </entry> - <entry> - <para>The classpath for loading POJO and JDBC drivers; only needed if the default - classpath of the Project does not contain the required classes. Do not add - Hibernate core libraries or dependencies, they are already included. If you get - ClassNotFound errors then check this list for possible missing or redundant - directories/jars.</para> - </entry> - <entry> - <para>Empty</para> - </entry> - </row> - <row> - <entry> - <para>Include default classpath from project</para> - </entry> - <entry> - <para>When enabled the project classpath will be appended to the classpath specified - above</para> - </entry> - <entry> - <para>Enabled</para> - </entry> - </row> - </tbody> - </tgroup> - </table> - <itemizedlist> - <listitem> - <para><emphasis> - <property>Mappings</property> - </emphasis> for additional mappings</para> - </listitem> - </itemizedlist> - <figure> - <title>Specifying additional Mappings in Hibernate Console Configuration</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" fileref="images/plugins/plugins_4.png" format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_4.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>Parameters of the Mappings tab of the <property>Hibernate Console Configuration - wizard</property> are explained below:</para> - <table> - <title>Hibernate Console Configuration Mappings</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - <colspec colnum="3" colwidth="1*"/> - <thead> - <row> - <entry align="center"> - <para>Parameter</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - <entry align="center"> - <para>Auto detected value</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para>Mapping files </para> - </entry> - <entry> - <para>List of additional mapping files that should be loaded. Note: A - hibernate.cfg.xml or persistence.xml can also contain mappings. Thus if these are - duplications here, you will get "Duplicate mapping" errors when using the console - configuration.</para> - </entry> - <entry> - <para>empty</para> - </entry> - </row> - </tbody> - </tgroup> - </table> - <itemizedlist> - <listitem> - <para>and the last tab <emphasis> - <property>Common</property> - </emphasis></para> - </listitem> - </itemizedlist> - <figure> - <title>Common Tab of the Console Configuration Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_4_a.png"/> - </imageobject> - </mediaobject> - </figure> - <para>It allows to define general aspects of the launch configuration including storage - location, console encoding and some others.</para> - <para>Clicking <emphasis> - <property>Finish</property> - </emphasis> creates the configuration and shows it in the <property>Hibernate Configurations - view</property>.</para> - <figure> - <title>Console Overview</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" fileref="images/plugins/plugins_5.png" format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_5.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section id="modif_console_conf"> - <title>Modifying a Hibernate Console Configuration </title> - <para>When you created a hibernate console configuration you can modify it in 2 ways: </para> - <itemizedlist> - <listitem> - <para>right-click on the configuration in <emphasis> - <property>Hibernate Configurations View->Edit Configuration </property> - </emphasis> or just double-click on <property>Console Configuration</property> - item.</para> - <figure> - <title>Opening Edit Configuration Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_4_c.png"/> - </imageobject> - </mediaobject> - </figure> - <para> After clicking you will see the Edit Configuration Wizard that is similar to - <emphasis> - <property>Create Console Configuration</property> - </emphasis>,described in <xref linkend="creat_console_conf"/>. </para> - </listitem> - <listitem> - <para>use Properties view for modifying some of Console Configuration properties.</para> - <figure> - <title>Properties View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_4_b.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The following table describes the available settings in the Properties view. Most - properties are changeable by left click but some are not. <table> - <title>Properties</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - <colspec colnum="3" align="left" colwidth="1*"/> - <thead> - <row> - <entry align="center"> - <para>Property</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - <entry align="center"> - <para>Is Changeable</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para>Additional mapping files </para> - </entry> - <entry> - <para>List of additional mapping files that should be loaded. </para> - </entry> - <entry> - <para>False</para> - </entry> - </row> - <row> - <entry> - <para>Configuration file</para> - </entry> - <entry> - <para>Path to a hibernate.cfg.xml file</para> - </entry> - <entry> - <para>False</para> - </entry> - </row> - <row> - <entry> - <para>Connection</para> - </entry> - <entry> - <para>DTP provided connection that you can use instead of what is in cfg.xml - and jpa persistence.xml. It's possible to use either already configured - hibernate or JPA connection or specify a new one here.</para> - </entry> - <entry> - <para>True</para> - </entry> - </row> - <row> - <entry> - <para>Name</para> - </entry> - <entry> - <para>The unique name of the console configuration</para> - </entry> - <entry> - <para>True</para> - </entry> - </row> - <row> - <entry> - <para>Project</para> - </entry> - <entry> - <para>The name of a java project which classpath should be used in the console - configuration</para> - </entry> - <entry> - <para>True</para> - </entry> - </row> - <row> - <entry> - <para>Properties file</para> - </entry> - <entry> - <para>Path to a hibernate.properties file</para> - </entry> - <entry> - <para>False</para> - </entry> - </row> - <row> - <entry> - <para>Type</para> - </entry> - <entry> - <para>Choose between "CORE", "ANNOTATIONS" and - "JPA" according to the method of relational mapping you want to - use. Note, the two latter requires running Eclipse IDE with a JDK 5 runtime, - otherwise you will get classloading and/or version errors.</para> - </entry> - <entry> - <para>True</para> - </entry> - </row> - </tbody> - </tgroup> - </table></para> - </listitem> - </itemizedlist> - </section> - <section id="closing_conf_config"> - <title>Closing Hibernate Console Configuration</title> - <para>To close <property>Hibernate Console Configuration</property> you need do right-click - your configuration and choose <property>Close Configuration</property> option </para> - <figure> - <title>Close Hibernate Console Configuration</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_4_d.png"/> - </imageobject> - </mediaobject> - </figure> - <para>While closing configuration the connection with database will be closed, jar libs will - be unlock (for Windows) and other resources will set as free. </para> - </section> - </section> - <section id="refeng_codegen" role="updated"> - <title>Reverse Engineering and Code Generation</title> - <para>A "click-and-generate" reverse engineering and code generation facility is - available. This facility allows you to generate a range of artifacts based on database or an - already existing Hibernate configuration, be that mapping files or annotated classes. Some of - these are POJO Java source file, Hibernate <emphasis> - <property>.hbm.xml</property> - </emphasis>, <emphasis> - <property>hibernate.cfg.xml</property> - </emphasis> generation and schema documentation.</para> - <para>To start working with this process, start the <property>Hibernate Code - Generation</property> which is available in the toolbar via the <property - >Hibernate</property> icon or via the <emphasis> - <property>Run > Hibernate Code Generation</property> - </emphasis> menu item.</para> - <section id="code_gen"> - <title>Code Generation Launcher</title> - <para>When you click on <emphasis> - <property>Open Hibernate Code Generation Dialog...</property> - </emphasis> the standard Eclipse launcher dialog will appear. In this dialog you can create, - edit and delete named Hibernate code generation "launchers".</para> - <figure id="hib_code_gen"> - <title>Getting Hibernate Code Generation Wizard</title> - <mediaobject> - <imageobject role="fo"> - <imagedata fileref="images/plugins/plugins_6.png" format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_6.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para/> - <figure> - <title>Hibernate Code Generation Wizard</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_7.png" format="PNG" - /> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_7.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>The first time you create a code generation launcher you should give it a meaningful - name, otherwise the default prefix <emphasis> - <property>New_Generation</property> - </emphasis> will be used.</para> - <note> - <title>Tip:</title> - <para>The "At least one exporter option must be selected" is just a warning - stating that for this launch to work you need to select an exporter on the Exporter tab. - When an exporter has been selected the warning will disappear.</para> - </note> - <para>The dialog also have the standard tabs <emphasis> - <property>Refresh</property> - </emphasis> and <emphasis> - <property>Common</property> - </emphasis> that can be used to configure which directories should be automatically - refreshed and various general settings launchers, such as saving them in a project for - sharing the launcher within a team.</para> - <para>On the <emphasis> - <property>Main</property> - </emphasis> tab you see the following fields:</para> - <table> - <title>Code generation "Main" tab fields</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - <colspec colnum="3" colwidth="0.5*"/> - <thead> - <row> - <entry align="center"> - <para>Field</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para>Console Configuration</para> - </entry> - <entry> - <para>The name of the console configuration which should be used when code - generating</para> - </entry> - </row> - <row> - <entry> - <para>Output directory</para> - </entry> - <entry> - <para>Path to a directory where all output will be written by default. It's possible - to enter absolute directory path, for example - "d:/temp". Be aware that existing - files will be overwritten, so be sure to specify the correct directory.</para> - </entry> - </row> - <row> - <entry> - <para>Reverse engineer from JDBC Connection</para> - </entry> - <entry> - <para>If enabled, the tools will reverse engineer the database available via the - connection information in the selected Hibernate Console Configuration and - generate code based on the database schema. If not enabled, the code generation - will just be based on the mappings already specified in the Hibernate Console - configuration.</para> - </entry> - </row> - <row> - <entry> - <para>Package</para> - </entry> - <entry> - <para>The package name here is used as the default package name for any entities - found when reverse engineering</para> - </entry> - </row> - <row> - <entry> - <para>reveng.xml</para> - </entry> - <entry> - <para>Path to a reveng.xml file. A reveng.xml file allows you to control certain - aspects of the reverse engineering. e.g. how jdbc types are mapped to hibernate - types and especially important which tables are included/excluded from the - process. Clicking "setup" allows you to select an existing reveng.xml file or - create a new one. See more details about the reveng.xml file in <xref - linkend="reverseengineering"/>.</para> - </entry> - </row> - <row> - <entry> - <para>reveng. strategy</para> - </entry> - <entry> - <para>If reveng.xml does not provide enough customization you can provide your own - implementation of an ReverseEngineeringStrategy. The class needs to be in the - classpath of the Console Configuration, otherwise you will get class not found - exceptions. See <xref linkend="custom-reveng-strategy"/> for details and an - example of a custom strategy.</para> - </entry> - </row> - <row> - <entry> - <para>Generate basic typed composite ids</para> - </entry> - <entry> - <para>A table that has a multi-column primary key a <composite-id> mapping - will always be created. If this option is enabled and there are matching - foreign-keys each key column is still considered a 'basic' scalar (string, long, - etc.) instead of a reference to an entity. If you disable this option a - <code><key-many-to-one></code> instead. Note: a - <code><many-to-one></code> property is still created, but is simply marked - as non-updatable and non-insertable.</para> - </entry> - </row> - <row> - <entry> - <para>Detect optimistic lock columns</para> - </entry> - <entry> - <para>Automatically detect optimistic lock columns. Controllable via reveng. - strategy; the current default is to use columns named VERSION or TIMESTAMP.</para> - </entry> - </row> - <row> - <entry> - <para>Detect many-to-many tables</para> - </entry> - <entry> - <para>Automatically detect many-to-many tables. Controllable via reveng. - strategy.</para> - </entry> - </row> - <row> - <entry> - <para>Detect one-to-one associations</para> - </entry> - <entry> - <para> Reverse engineering detects one-to-one associations via primary key and both - hbm.xml and annotation generation generates the proper code for it. </para> - <para> The detection is enabled by default (except for Seam 1.2 and Seam 2.0) - reverse engineering. For Hibernate Tools generation there is a checkbox to disable - if not wanted. </para> - </entry> - </row> - <row> - <entry> - <para>Use custom templates</para> - </entry> - <entry> - <para>If enabled, the Template directory will be searched first when looking up the - templates, allowing you to redefine how the individual templates process the - hibernate mapping model.</para> - </entry> - </row> - <row> - <entry> - <para>Template directory</para> - </entry> - <entry> - <para>A path to a directory with custom templates</para> - </entry> - </row> - </tbody> - </tgroup> - </table> - </section> - <section id="exportes"> - <title>Exporters</title> - <para>The <emphasis> - <property>Exporters</property> - </emphasis> tab is used to specify which type of code that should be generated. Each - selection represents an Exporter that is responsible for generating the code, hence the - name.</para> - <figure> - <title>Selecting Exporters</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_8.png" format="PNG" - /> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_8.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>The following table describes in short the various exporters. Remember you can - add/remove any Exporters depending on your needs.</para> - <table> - <title>Code generation "Exporter" tab fields</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - <thead> - <row> - <entry align="center"> - <para>Field</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para>Domain code</para> - </entry> - <entry> - <para>Generates POJO's for all the persistent classes and components found in the - given Hibernate configuration.</para> - </entry> - </row> - <row> - <entry> - <para>DAO code</para> - </entry> - <entry> - <para>Generates a set of DAO's for each entity found.</para> - </entry> - </row> - <row> - <entry> - <para>Hibernate XML Mappings</para> - </entry> - <entry> - <para>Generate mapping (hbm.xml) files for each entity.</para> - </entry> - </row> - <row> - <entry> - <para>Hibernate XML Configuration</para> - </entry> - <entry> - <para>Generate a hibernate.cfg.xml file. Used to keep the hibernate.cfg.xml update - with any new found mapping files.</para> - </entry> - </row> - <row> - <entry> - <para>Schema Documentation (.html)</para> - </entry> - <entry> - <para>Generates a set of html pages that documents the database schema and some of - the mappings.</para> - </entry> - </row> - <row> - <entry> - <para>Generic Exporter (hbmtemplate)</para> - </entry> - <entry> - <para>Fully customizable exporter which can be used to perform custom - generation.</para> - </entry> - </row> - <row> - <entry> - <para>Schema Export (.ddl)</para> - </entry> - <entry> - <para>Generates the appropriate SQL DDL and allows you to store the result in a file - or export it directly to the database.</para> - </entry> - </row> - </tbody> - </tgroup> - </table> - <para>Each Exporter listens to certain properties and these can be setup in the <emphasis> - <property>Properties</property> - </emphasis> section where you can add/remove predefined or customer properties for each of - the exporters. The following table lists the time of writing predefined properties:</para> - <para> - <table> - <title>Exporter Properties</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" colwidth="3*"/> - <thead> - <row> - <entry align="center"> - <para>Name</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para>jdk5</para> - </entry> - <entry> - <para>Generate Java 5 syntax</para> - </entry> - </row> - <row> - <entry> - <para>ejb3</para> - </entry> - <entry> - <para>Generate EJB 3 annotations</para> - </entry> - </row> - <row> - <entry> - <para>for_each</para> - </entry> - <entry> - <para>Specifies for which type of model elements the exporter should create a file - and run through the templates. Possible values are: entity, component, - configuration</para> - </entry> - </row> - <row> - <entry> - <para>template_path</para> - </entry> - <entry> - <para>Custom template directory for this specific exporter. You can use Eclipse - variables.</para> - </entry> - </row> - <row> - <entry> - <para>template_name</para> - </entry> - <entry> - <para>Name for template relative to the template path</para> - </entry> - </row> - <row> - <entry> - <para>outputdir</para> - </entry> - <entry> - <para>Custom output directory for this specific exporter. You can use Eclipse - variables.</para> - </entry> - </row> - <row> - <entry> - <para>file_pattern</para> - </entry> - <entry> - <para>Pattern to use for the generated files, relatively for the output dir. - Example: {package-name}/{class-name}.java .</para> - </entry> - </row> - <row> - <entry> - <para>dot.executable</para> - </entry> - <entry> - <para>Executable to run GraphViz (only relevant, but optional for Schema - documentation)</para> - </entry> - </row> - <row> - <entry> - <para>drop</para> - </entry> - <entry> - <para>Output will contain drop statements for the tables, indices and - constraints</para> - </entry> - </row> - <row> - <entry> - <para>delimiter</para> - </entry> - <entry> - <para>If specified the statements will be dumped to this file</para> - </entry> - </row> - <row> - <entry> - <para>create</para> - </entry> - <entry> - <para>Output will contain create statements for the tables, indices and - constraints</para> - </entry> - </row> - <row> - <entry> - <para>scriptToConsole</para> - </entry> - <entry> - <para>The script will be output to Console</para> - </entry> - </row> - <row> - <entry> - <para>exportToDatabase</para> - </entry> - <entry> - <para>Executes the generated statements against the database</para> - </entry> - </row> - <row> - <entry> - <para>outputFileName</para> - </entry> - <entry> - <para>If specified the statements will be dumped to this file</para> - </entry> - </row> - <row> - <entry> - <para>haltOnError</para> - </entry> - <entry> - <para>Halts the build process if an error occurs</para> - </entry> - </row> - <row> - <entry> - <para>format</para> - </entry> - <entry> - <para>Applies basic formatting to the statements</para> - </entry> - </row> - <row> - <entry> - <para>schemaUpdate</para> - </entry> - <entry> - <para>Updates a schema</para> - </entry> - </row> - </tbody> - </tgroup> - </table> + <title>Eclipse Plugins</title> + <para> + This chapter will introduce you to the set of wizards and editors provided by <productname>Hibernate Tools</productname> within Eclipse, which are designed to simplify working with <productname>Hibernate</productname>. + </para> + <section> + <title>Introduction</title> + <para> + Hibernate Eclipse Tools includes wizards for creating Hibernate mapping files, configuration files (<filename>.cfg.xml</filename>), <filename>reveng.xml</filename> files as well as wizards for adjusting Console Configuration and Code Generation. Special structured and XML editors and editors for executing HQL and Criteria queries are also provided in Hibernate Console. Refer to <xref linkend="hibernate_key_features"/> to find all the benefits that are provided by these tools within Eclipse. + </para> + <note> + <title>Note:</title> + <para> + Please note that these tools do not try to hide any of <productname>Hibernates</productname> functionality; rather the tools make working with <productname>Hibernate</productname> easier. You are still encouraged to read the <ulink url="http://hibernate.org/docs">Hibernate Documentation</ulink> in order to be able to fully utilize <productname>Hibernate Tools</productname> and especially <productname>Hibernate</productname> itself. + </para> + </note> + <section id="download_base_project"> + <title>Download base project</title> + <para>You can download the example projects that are used in this chapter.</para> + <para> + A <property>JPA base project</property> is available on the <ulink url="http://docs.jboss.org/tools/resources/">documentation resources page</ulink> together with a <ulink url="http://docs.jboss.org/tools/resources/TestHibernateproject_for_hibernate_...">base Java project</ulink>. </para> - <para>To add a property to the chosen Exporter click the <emphasis> - <property>Add</property> - </emphasis> button in the <property>Properties</property> section. In the appeared dialog - you should select the property from the proposed list and the value for it.</para> - <figure> - <title>Adding the Property for Schema Export (.ddl)</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_8a.png"/> - </imageobject> - </mediaobject> - </figure> - <note> - <title>Tip:</title> - <para>If the property is a directory, it is possible to browse directories in the Value - field.</para> - </note> - <figure> - <title>Specifying the Property Value</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_8b.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - </section> - <section id="map_config_editor"> - <title>Hibernate Mapping and Configuration File Editor</title> - <para>The <property>Hibernate Mapping File editor</property> provides XML editing functionality - for the <emphasis> - <property>hbm.xml </property> - </emphasis> and <emphasis> - <property>cfg.xml</property> - </emphasis> files. The editor is based on the Eclipse WTP tools and extends its functionality - to provide Hibernate specific code completion.</para> - <figure> - <title>XML Editing Functionality</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_9.png" format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_9.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <section> - <title>Java property/class completion</title> - <para>Package, class, and field completion is enabled for relevant XML attributes. The - auto-completion detects its context and limits the completion for e.g. - <code><property></code> and only shows the properties/fields available in the - enclosing <code><class></code> , <code><subclass></code> etc. It is also - possible to navigate from the <emphasis> - <property>hbm.xml</property> - </emphasis> files to the relevant class/field in java code.</para> - <figure> - <title>Navigation Functionality</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" fileref="images/plugins/plugins_10.png" format="PNG" - scale="80"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_10.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>This is done via the standard hyperlink navigation functionality in Eclipse; per default - it is done by pressing F3 while the cursor is on a class/field or by pressing <emphasis> - <property>Ctrl</property> - </emphasis> and the mouse button to perform the same navigation.</para> - <para>For java completion and navigation to work the file needs to reside inside an Eclipse - Java project, otherwise no completion will occur.</para> - <note> - <title>Note:</title> - <para>Java completion does not require a Hibernate console configuration to be used.</para> - </note> - </section> - <section> - <title>Table/Column completion</title> - <para>Table and column completion is also available for all table and column attributes. </para> - <figure> - <title>Table and Column Completion</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_11.png" - format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_11.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <important> - <title>Important:</title> - <para>Table/Column completion requires a proper configured hibernate console configuration - and this configuration should be the default for the project where the <emphasis> - <property>hbm.xml</property> - </emphasis> resides.</para> - </important> - <para>You can check which console configuration is selected under the Properties of a project - and look under the <emphasis> - <property>Hibernate Settings</property> - </emphasis> page. When a proper configuration is selected it will be used to fetch the - table/column names in the background.</para> - <note> - <title>Note:</title> - <para>Currently it is not recommended to use this feature on large databases since it does - not fetch the information iteratively. It will be improved in future versions.</para> - </note> - </section> - <section> - <title>Configuration property completion</title> - <para>In <emphasis> - <property>cfg.xml</property> - </emphasis> code completion for the value of <code><property> name</code> attributes - is available.</para> - <figure> - <title>Property Completion</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_12.png" - format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_12.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - </section> - </section> - <section id="map_config_struct_editor"> - <title>Structured Hibernate Mapping and Configuration File Editor</title> - <para>The structured editor represents the file in the tree form. It also allows to modify the - structure of the file and its elements with the help of tables provided on the right-hand - area.</para> - <para>To open any mapping file in the editor, choose <emphasis> - <property>Open With > Hibernate 3.0 XML Editor</property> - </emphasis> option from the context menu of the file. The editor should look as - follows:</para> - <figure> - <title>Structured hbm.xml Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_12_a.png"/> - </imageobject> - </mediaobject> - </figure> - <para>For the configuration file you should choose <emphasis> - <property>Open With > Hibernate Configuration 3.0 XML Editor</property> - </emphasis>option.</para> - <figure> - <title>Structured cfg.xml Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_12_b.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section id="properties_editor"> - <title>JBoss Tools Properties Editor</title> - <para>The editor is meant for editing <literal>.properties</literal> files. It contains two - tabs: the <property>Properties</property> (UI) tab and the <property>Source</property> tab for - manual editing.</para> - <para>For <literal>hibernate.properties</literal> file <property>JBoss Tools Properties - Editor</property> provides content assist which is available both for hibernate properties - and property values. You can make use of the content assist while editing the file in the - Source view and in the Properties view of the editor.</para> - <para>To add the property in the <property>Properties</property> view, click the <emphasis> - <property>Add</property> - </emphasis> button.</para> - <figure> - <title>Adding the Property</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/add_property1.png"/> - </imageobject> - </mediaobject> - </figure> - <para>In the <emphasis> - <property>Name</property> - </emphasis> field press <emphasis> - <property>Ctrl+Space</property> - </emphasis> to invoke the content assist. It will suggest <emphasis> - <property>'hibernate.'</property> - </emphasis> which is the prefix for all hibernate properties. After selecting <emphasis> - <property>'hibernate.'</property> - </emphasis> and invoking the content assist again, other prefixes and properties are displayed - as the proposals with a description of each one.</para> - <figure> - <title>Content Assist for Properties Names</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/add_property2.png"/> - </imageobject> - </mediaobject> - </figure> - <para>When invoking the content assist in the <emphasis> - <property>Value</property> - </emphasis> field, it also provides a list of proposals.</para> - <figure> - <title>Content Assist for Properties Values</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/add_property3.png"/> - </imageobject> - </mediaobject> - </figure> - <para>In the <property>Source</property> view of the editor, content assist also could be - invoked both for properties names and values:</para> - <figure> - <title>Content Assist in the Source view</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/add_property4.png"/> - </imageobject> - </mediaobject> - </figure> - <figure> - <title>Content Assist in the Source view</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/add_property5.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section id="rev_xml_editor"> - <title>Reveng.xml Editor</title> - <para>A <emphasis> - <property>reveng.xml </property> - </emphasis> file is used to customize and control how reverse engineering is performed by the - tools. The plugins provide an editor to ease the editing of this file and hence used to - configure the reverse engineering process.</para> - <para>The editor is intended to allow easy definition of type mappings, table include/excludes - and specific override settings for columns, e.g. define an explicit name for a column when the - default naming rules are not applicable.</para> - <note> - <title>Note:</title> - <para> Not all the features of the <emphasis> - <property>.reveng.xml </property> - </emphasis> file are exposed or fully implemented in the editor, but the main functionality - is there. To understand the full flexibility of the <emphasis> - <property>reveng.xml</property> - </emphasis>, please see <xref linkend="hibernaterevengxmlfile"/> - </para> - </note> - <para>The editor is activated as soon as an <emphasis> - <property>.reveng.xml </property> - </emphasis> file is opened. To get an initial <emphasis> - <property>reveng.xml </property> - </emphasis> file the <property>Reverse Engineering File Wizard</property> can be started via - <emphasis> - <property>Ctrl+N</property> - </emphasis> and <emphasis> - <property>Hibernate > Hibernate Reverse Engineering File (reveng.xml)</property> - </emphasis> then.</para> - <figure> - <title>ChooseReverse Engineering File Wizard </title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_22.png" format="PNG" - /> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_22.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>Or you can get it via the <property>Code Generation Launcher</property> by checking the - proper section in the <emphasis> - <property>Main</property> - </emphasis> tab of the <xref linkend="hib_code_gen"/>.</para> - <para>The following screenshot shows the <emphasis> - <property>Overview</property> - </emphasis> page where the wanted console configuration is selected (auto-detected if - Hibernate 3 support is enabled for the project)</para> - <figure> - <title>Overview Page</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_13.png" format="PNG" - /> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_13.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>The <emphasis> - <property>Table Filter</property> - </emphasis> page allows you to specify which tables to include and exclude. Pressing - <emphasis> - <property>Refresh</property> - </emphasis> shows the tables from the database that have not yet been excluded.</para> - <figure> - <title>Table Filters Page</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_14.png" format="PNG" - /> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_14.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>The <emphasis> - <property>Type Mappings</property> - </emphasis> page is used for specifying type mappings from JBDC types to any Hibernate type - (including usertypes) if the default rules are not applicable. Here again to see the database - tables press <emphasis> - <property>Refresh</property> - </emphasis> button underneath. More about type mappings you can find further in the <xref - linkend="type_map"/> section.</para> - <figure> - <title>Type Mappings Page</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_15.png" format="PNG" - /> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_15.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>The <emphasis> - <property>Table and Columns</property> - </emphasis> page allows you to explicit set e.g. which hibernatetype and propertyname that - should be used in the reverse engineered model. For more details on how to configure the - tables while reverse engineering read the <xref linkend="tab_and_col"/> section.</para> - <figure> - <title>Table and Columns Page</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_16.png" format="PNG" - /> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_16.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>Now that you have configured all necessary parts, you can learn how to work with <property - >Hibernate Console Perspective</property>.</para> - </section> - <section id="hib_console"> - <title>Hibernate Console Perspective</title> - <para>The <property>Hibernate Console Perspective</property> combines a set of views which allow - you to see the structure of your mapped entities/classes, edit HQL queries, execute the - queries, and see the results. To use this perspective you need to create a <xref - linkend="console_conf"/>.</para> - <section> - <title>Viewing the entity structure</title> - <para>To view your new configuration and entity/class structure, switch to <property>Hibernate - Configurations View</property>. Expanding the tree allows you to browse the class/entity - structure and see the relationships.</para> - <figure> - <title>Hibernate Console Perspective</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_17.png"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_17.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The <property>Console Configuration</property> does not dynamically adjust to changes - done in mappings and java code. To reload the configuration select the configuration and - click the <emphasis> - <property>Reload</property> - </emphasis> button in the view toolbar or in the context menu.</para> - <para>Besides, it's possible to open source and mapping files for objects showed in - <property>Hibernate Configurations View</property>. Just bring up the context menu for a - necessary object and select <emphasis> - <property>Open Source File</property> - </emphasis> to see appropriate Java class or <emphasis> - <property>Open Mapping File</property> - </emphasis> to open a proper <emphasis> - <property>.hbm.xml</property>.</emphasis></para> - <figure> - <title>Opening Source for Objects</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_17_a.png"/> - </imageobject> - </mediaobject> - </figure> - <section id="map_diagram"> - <title>Mapping Diagram</title> - <para>In order to get a visual feel on how entities are related as well as view their - structures, a <property>Mapping Diagram</property> is provided. It is available by right - clicking on the entity you want a mapping diagram for and then choosing <emphasis> - <property>Mapping Diagram</property>.</emphasis></para> - <figure> - <title>Mapping Diagram</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_18.png"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_18.png"/> - </imageobject> - </mediaobject> - </figure> - <para>To make <property>Mapping Diagram</property> usage easier you can use <property - >Rules</property>, <property>Grid</property>,<property>Snap to Geometry</property> - checkboxes in the <emphasis> - <property>View</property> - </emphasis> menu. </para> - <figure> - <title>View menu</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/map_diagram1.png"/> - </imageobject> - </mediaobject> - </figure> - <para>If you will select <emphasis> - <property>Rules</property> - </emphasis> checkbox, the view print page scale will be added to the page. The numbers on - the scale show its size in inches.If you click on the scale a <emphasis> - <property>Ruler Guide</property> - </emphasis> will appear on the diagram. You can connect any diagram item to it.To connect - the items you should move their tops to the Ruler Guide. And while moving the ruler guide, - the items will be moved together with it as a whole.</para> - <figure> - <title>Moving the Ruler guide</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/map_diagram2.png"/> - </imageobject> - </mediaobject> - </figure> - <para>If you'll select <emphasis> - <property>Grid</property> - </emphasis> checkbox, the grid will appear on the diagram.</para> - <figure> - <title>Grid on Mapping diagram</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/map_diagram3.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The checkbox <emphasis> - <property>Snap to Geometry</property> - </emphasis> helps to put the items of the diagram into allineation with the grid.</para> - <para>For better navigating through the diagram use <property>Outline view</property> which - is available in the structural and graphical modes.</para> - <figure> - <title>Navigating in the Structural Mode</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_18_a.png"/> - </imageobject> - </mediaobject> - </figure> - <para>To switch over between the modes use the buttons in the top-right corner of the - <property>Outline view</property>.</para> - <figure> - <title>Navigating in the Graphical Mode</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_18_b.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The options in the context menu of the mapping diagram are listed in the next - table.</para> - <table> - <title>Context Menu Options of the Mapping Diagram</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" align="left" colwidth="1*"/> - <colspec colnum="3" align="left" colwidth="3*"/> - <thead> - <row> - <entry align="center"> - <para>Icon</para> - </entry> - <entry align="center"> - <para>Command</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/toggleConnections.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Show|Hide connections</para> - </entry> - <entry>Allows to select what types of connections should be shown on the diagram: <itemizedlist> + <para>Also you need start the <ulink url="http://docs.jboss.org/tools/resources/GSG_database.zip">database</ulink>.</para> + <note> + <title>Note:</title> + <para>The steps for running the database are documented in the <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html-single/...">Getting Started Guide</ulink>.</para> + </note> + </section> + </section> + <section id="map_file_wizard"> + <title>Creating a Hibernate Mapping File</title> + <para>Hibernate mapping files are used to specify how your objects relate to database tables.</para> + <para> + To create basic mappings for properties and associations, i. e. generate <filename>.hbm.xml</filename> files, Hibernate Tools provide a basic wizard which you can display by selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem> + <guimenuitem>Hibernate XML mapping file</guimenuitem> + </menuchoice>. + </para> + <para> + At first you will be asked to select a package or multiple individual classes to map. It is also possible to create an empty file: do not select any packages or classes and an empty <filename>.hbm</filename> file will be created in the specified location. + </para> + <para id="depth_control"> + Using the <property>depth control</property> option you can define the dependency depth used when choosing classes. + </para> + <figure> + <title>Hibernate XML Mapping File Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_0.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + The next wizard page lists the mappings to be generated. You can see the <guilabel>Customers</guilabel>, <guilabel>Orders</guilabel>, <guilabel>Productlines</guilabel> and <guilabel>Products</guilabel> classes added under <property>depth control</property> driving. + </para> + <figure> + <title>Mappings to be generated</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_0_a.png"/> + </imageobject> + </mediaobject> + </figure> + <para>This wizard page display a preview of the generated <filename>.hbm</filename> files.</para> + <figure> + <title>Preview Generated Mapping Files</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_0_b.png"/> + </imageobject> + </mediaobject> + </figure> + <para>Clicking the <guibutton>Finish</guibutton> button creates the files.</para> + </section> + <section id="hib_config_file"> + <title>Creating a Hibernate Configuration File</title> + <para> + To be able to perform reverse engineering, prototype queries, and of course to simply use <property>Hibernate Core</property> a <filename>hibernate.properties</filename> or <filename>hibernate.cfg.xml</filename> file is needed. <property>Hibernate Tools</property> provides a wizard for generating the <filename>hibernate.cfg.xml</filename> file if you do not already have one. + </para> + <para>Start the wizard by clicking <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem> + <guimenuitem>Other</guimenuitem> + </menuchoice> (<keycombo><keycap>Ctrl</keycap> + <keycap>N</keycap> + </keycombo>), then select + + <menuchoice><guimenuitem>Hibernate</guimenuitem> + <guimenuitem>Hibernate Configuration File (cfg.xml)</guimenuitem> + </menuchoice> and click the <guibutton>Next</guibutton> button.</para> + <figure> + <title>Hibernate Configuration File Wizard</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" fileref="images/plugins/plugins_1.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_1.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <note> + <title>Note:</title> + <para> + The contents in the comboboxes for the JDBC driver class and JDBC URL change automatically, depending on the Dialect and actual driver you have chosen. + </para> + </note> + <para> + Enter your configuration information in this dialog. Details about the configuration options can be found in <ulink url="http://docs.jboss.org/ejb3/app-server/Hibernate3/reference/en/html_single">Hibernate Reference Documentation</ulink>. + </para> + <para> + Click the <guibutton>Finish</guibutton> button to create the configuration file, and after optionally creating a Console configuration, the <filename>hibernate.cfg.xml</filename> file will be automatically opened in an editor. The last option, <guilabel>Create Console Configuration</guilabel>, is enabled by default and when enabled, it will automatically use the <filename>hibernate.cfg.xml</filename> file for the basis of a Console configuration. + </para> + </section> + <section id="console_conf"> + <title>Hibernate Console Configuration</title> + <para> + A Console configuration describes how the <property>Hibernate plugin</property> should configure <property>Hibernate</property> and what configuration files and classpaths are needed to load the POJO's, JDBC drivers etc. It is required to make use of query prototyping, reverse engineering and code generation. You can have multiple named console configurations. Normally you would just need one per project, but it is definitely possible to create more if required. + </para> + <section id="creat_console_conf"> + <title>Creating a Hibernate Console Configuration</title> + <para> + You can create a console configuration by running the <guilabel>Console Configuration Wizard</guilabel>, shown in the following screenshot. The same wizard will also be used if you are coming from the <filename>hibernate.cfg.xml</filename> wizard and had enabled the <guilabel>Create Console Configuration</guilabel> option. + </para> + <note> + <title>Note:</title> + <para> + The wizard will look at the current selection in the IDE and try to auto-detect the appropriate settings, which you then can approve or modify to suit your needs. + </para> + </note> + <para/> + <para>The dialog consists of five tabs: </para> + <itemizedlist> + <listitem> + <para> + <guilabel>Main</guilabel>, which displays the basic and required settings</para> + </listitem> + </itemizedlist> + <figure> + <title> Creating Hibernate Console Configuration</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" fileref="images/plugins/plugins_2.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_2.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + The following table describes the available settings on the <guilabel>Main</guilabel> tab. The wizard can automatically detect the default values for most of the settings if you started the wizard with the relevant Java project or resource selected. + </para> + <table> + <title>Hibernate Console Configuration Parameters</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + <thead> + <row> + <entry align="center"> + <para>Parameter</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + <entry align="center"> + <para>Auto detected value</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Name</para> + </entry> + <entry> + <para>The unique name of the console configuration</para> + </entry> + <entry> + <para>Name of the selected project</para> + </entry> + </row> + <row> + <entry> + <para>Type</para> + </entry> + <entry> + <para> + Choose between "Core", "Annotations" and "JPA". Note that the two latter requires running Eclipse IDE with a JDK 5 runtime, otherwise you will get class loading and/or version errors. + </para> + </entry> + <entry> + <para>No default value</para> + </entry> + </row> + <row> + <entry> + <para>Project</para> + </entry> + <entry> + <para>The name of a Java project whose classpath should be used in the console configuration</para> + </entry> + <entry> + <para>Name of the selected project</para> + </entry> + </row> + <row> + <entry> + <para>Database connection</para> + </entry> + <entry> + <para> + DTP provided connection that you can use instead of what is defined in the <filename>cfg.xml</filename> and JPA <filename>persistence.xml</filename> files. It is possible to use an already configured Hibernate or JPA connection, or specify a new one here. + </para> + </entry> + <entry> + <para>[Hibernate Configured connection]</para> + </entry> + </row> + <row> + <entry> + <para>Property file</para> + </entry> + <entry> + <para>Path to a <filename>hibernate.properties</filename> file</para> + </entry> + <entry> + <para>First <filename>hibernate.properties</filename> file found in the selected project</para> + </entry> + </row> + <row> + <entry> + <para>Configuration file</para> + </entry> + <entry> + <para>Path to a <filename>hibernate.cfg.xml</filename> file</para> + </entry> + <entry> + <para>First <filename>hibernate.cfg.xml</filename> file found in the selected project</para> + </entry> + </row> + <row> + <entry> + <para>Persistence unit</para> + </entry> + <entry> + <para>Name of the persistence unit to use</para> + </entry> + <entry> + <para> + No default value (let Hibernate Entity Manager find the persistence unit or it can be defined manually using the <guibutton>Browse</guibutton> button) + </para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <note> + <title>Tip:</title> + <para> + The two latter settings are usually not required if you specify a project that has a <filename> /hibernate.cfg.xml </filename> or <filename>/META-INF/persistence.xml</filename> file in its classpath.</para> + </note> + <itemizedlist> + <listitem> + <para> + The <guilabel>Options</guilabel> tab the optional settings</para> + </listitem> + </itemizedlist> + <figure> + <title>Options Tab of the Console Configuration Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_2_a.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The next table describes the Hibernate Console Configuration options available on the <guilabel>Options</guilabel> tab.</para> + <table> + <title>Hibernate Console Configuration Options</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + <thead> + <row> + <entry align="center"> + <para>Parameter</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + <entry align="center"> + <para>Auto detected value</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Database dialect</para> + </entry> + <entry> + <para>Define a database dialect. It is possible either to enter your own value or choose from list. </para> + </entry> + <entry> + <para>No default value</para> + </entry> + </row> + <row> + <entry> + <para>Naming strategy</para> + </entry> + <entry> + <para>Fully qualified class name of a custom <code>NamingStrategy</code>. Only required if you use a special naming strategy.</para> + </entry> + <entry> + <para>No default value</para> + </entry> + </row> + <row> + <entry> + <para>Entity resolver</para> + </entry> + <entry> + <para>Fully qualified class name of a custom <code>EntityResolver</code>. Only required if you have special XML entity includes in your mapping files.</para> + </entry> + <entry> + <para>No default value</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <itemizedlist> + <listitem> + <para><guilabel>Classpath</guilabel> for classpath</para> + </listitem> + </itemizedlist> + <figure> + <title>Specifying Classpath in Hibernate Console Configuration</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" fileref="images/plugins/plugins_3.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_3.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para>The following table specifies the parameters of the <guilabel>Classpath</guilabel> tab of the wizard.</para> + <table> + <title>Hibernate Console Configuration Classpath</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + <colspec colnum="3" colwidth="1*"/> + <thead> + <row> + <entry align="center"> + <para>Parameter</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + <entry align="center"> + <para>Auto detected value</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Classpath</para> + </entry> + <entry> + <para> + The classpath for loading POJO and JDBC drivers; only needed if the default classpath of the Project does not contain the required classes. Do not add Hibernate core libraries or dependencies, they are already included. If you get ClassNotFound errors then check this list for possible missing or redundant directories or JAR files. + </para> + </entry> + <entry> + <para>Empty</para> + </entry> + </row> + <row> + <entry> + <para>Include default classpath from project</para> + </entry> + <entry> + <para>When enabled the project classpath will be appended to the classpath specified above</para> + </entry> + <entry> + <para>Enabled</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <itemizedlist> + <listitem> + <para> + <guilabel>Mappings</guilabel> for additional mappings</para> + </listitem> + </itemizedlist> + <figure> + <title>Specifying additional Mappings in Hibernate Console Configuration</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" fileref="images/plugins/plugins_4.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_4.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para>Parameters of the <guilabel>Mappings</guilabel> tab of the <property>Hibernate Console Configuration wizard</property> are explained below:</para> + <table> + <title>Hibernate Console Configuration Mappings</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + <colspec colnum="3" colwidth="1*"/> + <thead> + <row> + <entry align="center"> + <para>Parameter</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + <entry align="center"> + <para>Auto detected value</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Mapping files </para> + </entry> + <entry> + <para> + List of additional mapping files that should be loaded. Note: A <filename>hibernate.cfg.xml</filename> or <filename>persistence.xml</filename> can also contain mappings. Thus if these are duplications here, you will get "Duplicate mapping" errors when using the console configuration. + </para> + </entry> + <entry> + <para>empty</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <itemizedlist> + <listitem> + <para>and the last tab <guilabel>Common</guilabel> + </para> + </listitem> + </itemizedlist> + <figure> + <title>Common Tab of the Console Configuration Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_4_a.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The <guilabel>Common</guilabel> tab allows you to define the general aspects of the launch configuration including storage location, console encoding and some others.</para> + <para> + Clicking the <guibutton>Finish</guibutton> button creates the configuration and shows it in the <property>Hibernate Configurations view</property>. + </para> + <figure> + <title>Console Overview</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" fileref="images/plugins/plugins_5.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_5.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="modif_console_conf"> + <title>Modifying a Hibernate Console Configuration </title> + <para>When you created a Hibernate Console Configuration you can modify it in two ways: </para> + <itemizedlist> + <listitem> + <para> + Right-click on the configuration in the <guilabel>Hibernate Configurations View</guilabel> and select <guimenuitem>Edit Configuration</guimenuitem>, or just double-click on the <guilabel>Console Configuration</guilabel> item. + </para> + <figure> + <title>Opening Edit Configuration Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_4_c.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + You will then see the <guilabel>Edit Configuration Wizard</guilabel>, which is similar to <guilabel>Create Console Configuration</guilabel>, described in <xref linkend="creat_console_conf"/>. + </para> + </listitem> + <listitem> + <para>Use the <guilabel>Properties</guilabel> view to modify the Console Configuration properties.</para> + <figure> + <title>Properties View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_4_b.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + The following table describes the available settings in the <guilabel>Properties</guilabel> view. Most properties can be changed by left clicking on them, but some can not. + <table> + <title>Properties</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + <colspec colnum="3" align="left" colwidth="1*"/> + <thead> + <row> + <entry align="center"> + <para>Property</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + <entry align="center"> + <para>Is Changeable</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Additional mapping files </para> + </entry> + <entry> + <para>Count of additional mapping files that should be loaded. </para> + </entry> + <entry> + <para>False</para> + </entry> + </row> + <row> + <entry> + <para>Configuration file</para> + </entry> + <entry> + <para>Path to a <filename>hibernate.cfg.xml</filename> file</para> + </entry> + <entry> + <para>False</para> + </entry> + </row> + <row> + <entry> + <para>Connection</para> + </entry> + <entry> + <para> + DTP provided connection that you can use instead of what is in the <filename>cfg.xml</filename> and JPA <filename>persistence.xml</filename> files. It is possible to use either an already configured Hibernate or JPA connection, or specify a new one here. + </para> + </entry> + <entry> + <para>True</para> + </entry> + </row> + <row> + <entry> + <para>Name</para> + </entry> + <entry> + <para>The unique name of the console configuration</para> + </entry> + <entry> + <para>True</para> + </entry> + </row> + <row> + <entry> + <para>Project</para> + </entry> + <entry> + <para>The name of a Java project which classpath should be used in the console configuration</para> + </entry> + <entry> + <para>True</para> + </entry> + </row> + <row> + <entry> + <para>Properties file</para> + </entry> + <entry> + <para>Path to a <filename>hibernate.properties</filename> file</para> + </entry> + <entry> + <para>False</para> + </entry> + </row> + <row> + <entry> + <para>Type</para> + </entry> + <entry> + <para> + Choose between "CORE", "ANNOTATIONS" and "JPA" according to the method of relational mapping you want to + use. Note, the two latter requires running Eclipse IDE with a JDK 5 runtime, otherwise you will get class loading and/or version errors. + </para> + </entry> + <entry> + <para>True</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </para> + </listitem> + </itemizedlist> + </section> + <section id="closing_conf_config"> + <title>Closing Hibernate Console Configuration</title> + <para> + To close <guilabel>Hibernate Console Configuration</guilabel> you need to right-click your configuration and choose the <guimenuitem>Close Configuration</guimenuitem> option. + </para> + <figure> + <title>Close Hibernate Console Configuration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_4_d.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + When closing the configuration the connection with database will be closed, JAR libs will be unlock (for Windows) and other resources will set as free. + </para> + </section> + </section> + <section id="refeng_codegen" role="updated"> + <title>Reverse Engineering and Code Generation</title> + <para> + Hibernate provides "click-and-generate" reverse engineering and code generation facilities. This allows you to generate a range of artifacts based on database or an existing Hibernate configuration, be that mapping files or annotated classes. Some of these are POJO Java source files, Hibernate <filename>.hbm.xml</filename> files, <filename>hibernate.cfg.xml</filename> generation and schema documentation. + </para> + <para> + To start working with this process, start the <guilabel>Hibernate Code Generation</guilabel> tool which is available from the toolbar via the <property>Hibernate</property> icon or via the <menuchoice><guimenuitem>Run</guimenuitem><guimenuitem>Hibernate Code Generation</guimenuitem></menuchoice> menu item. + </para> + <section id="code_gen"> + <title>Code Generation Launcher</title> + <para> + When you click on the <guimenuitem>Open Hibernate Code Generation Dialog...</guimenuitem> option the standard Eclipse launcher dialog will appear. In this dialog you can create, edit and delete named Hibernate code generation "launchers". + </para> + <figure id="hib_code_gen"> + <title>Getting Hibernate Code Generation Launcher</title> + <mediaobject> + <imageobject role="fo"> + <imagedata fileref="images/plugins/plugins_6.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_6.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para/> + <figure> + <title>Hibernate Code Generation Launcher</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_7.png" format="PNG" /> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_7.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + The first time you create a code generation launcher you should give it a meaningful name, otherwise the default prefix <guilabel>New_Generation</guilabel> will be used. + </para> + <note> + <title>Tip:</title> + <para> + The "At least one exporter option must be selected" warning indicates that for this launcher to work you need to select an exporter on the <guilabel>Exporter</guilabel> tab. When an exporter has been selected the warning will disappear. + </para> + </note> + <para> + The dialog also has the standard <guilabel>Refresh</guilabel> and <guilabel>Common</guilabel> tabs that can be used to configure which directories should be automatically refreshed and various general settings for launchers, such as saving them in a project for sharing the launcher within a team. + </para> + <para>On the <guilabel>Main</guilabel> tab you see the following fields:</para> + <table> + <title>Code generation "Main" tab fields</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + <colspec colnum="3" colwidth="0.5*"/> + <thead> + <row> + <entry align="center"> + <para>Field</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Console Configuration</para> + </entry> + <entry> + <para>The name of the console configuration that should be used when generating code</para> + </entry> + </row> + <row> + <entry> + <para>Output directory</para> + </entry> + <entry> + <para> + The default location where all output will be written to. It's possible to enter absolute directory path, for example - <filename>d:/temp</filename>. Be aware that existing files will be overwritten, so be sure to specify the correct directory. + </para> + </entry> + </row> + <row> + <entry> + <para>Reverse engineer from JDBC Connection</para> + </entry> + <entry> + <para> + If enabled, the tools will reverse engineer the database defined in the connection information in the selected Hibernate Console Configuration, and generate code based on the database schema. If not enabled, the code generation will be based on the existing mappings specified in the Hibernate Console configuration. + </para> + </entry> + </row> + <row> + <entry> + <para>Package</para> + </entry> + <entry> + <para>The package name here is used as the default package name for any entities found when reverse engineering</para> + </entry> + </row> + <row> + <entry> + <para>reveng.xml</para> + </entry> + <entry> + <para> + Path to a <filename>reveng.xml</filename> file. A <filename>reveng.xml</filename> file allows you to control certain aspects of the reverse engineering process such as how JDBC types are mapped to Hibernate types, and which tables are included and excluded from the process (which is especially important). Clicking the <guibutton>Setup</guibutton> button allows you to select an existing <filename>reveng.xml</filename> file, or create a new one. See more details about the <filename>reveng.xml</filename> file in <xref linkend="reverseengineering"/>. + </para> + </entry> + </row> + <row> + <entry> + <para>reveng. strategy</para> + </entry> + <entry> + <para> + If the <filename>reveng.xml</filename> file does not provide enough customization you can provide your own implementation of a <code>ReverseEngineeringStrategy</code>. The class needs to be in the classpath of the Console Configuration, otherwise you will get class not found exceptions. See <xref linkend="custom-reveng-strategy"/> for details and an example of a custom strategy. + </para> + </entry> + </row> + <row> + <entry> + <para>Generate basic typed composite ids</para> + </entry> + <entry> + <para> + When a table that has a multi-column primary key a <code><composite-id></code> mapping will always be created. If this option is enabled and there are matching foreign-keys, each key column is still considered a 'basic' scalar (string, long, etc.) instead of a reference to an entity. If you disable this option a <code><key-many-to-one></code> instead. Note: a <code><many-to-one></code> property is still created, but is simply marked as non-updatable and non-insertable. + </para> + </entry> + </row> + <row> + <entry> + <para>Detect optimistic lock columns</para> + </entry> + <entry> + <para> + Automatically detect optimistic lock columns. Controllable via reveng. strategy; the current default is to use columns named VERSION or TIMESTAMP. + </para> + </entry> + </row> + <row> + <entry> + <para>Detect many-to-many tables</para> + </entry> + <entry> + <para>Automatically detect many-to-many tables. Controllable via reveng. strategy.</para> + </entry> + </row> + <row> + <entry> + <para>Detect one-to-one associations</para> + </entry> + <entry> + <para> + Reverse engineering detects one-to-one associations via primary key and both the <filename>hbm.xml</filename> file and annotation generation generates the proper code for it. + </para> + <para> + The detection is enabled by default (except for Seam 1.2 and Seam 2.0) reverse engineering. For Hibernate Tools generation there is a checkbox to disable this feature if it is not required. + </para> + </entry> + </row> + <row> + <entry> + <para>Use custom templates</para> + </entry> + <entry> + <para> + If enabled, the Template directory will be searched first when looking up the templates, allowing you to redefine how the individual templates process the hibernate mapping model. + </para> + </entry> + </row> + <row> + <entry> + <para>Template directory</para> + </entry> + <entry> + <para>A path to a directory with custom templates</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </section> + <section id="exportes"> + <title>Exporters</title> + <para> + The <guilabel>Exporters</guilabel> tab is used to specify the type of code that should be generated. Each selection represents an Exporter that is responsible for generating the code, hence the name. + </para> + <figure> + <title>Selecting Exporters</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_8.png" format="PNG" /> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_8.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + The following table provides a short description of the various exporters. Remember you can add and remove any Exporters depending on your needs. + </para> + <table> + <title>Code generation "Exporter" tab fields</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + <thead> + <row> + <entry align="center"> + <para>Field</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Domain code</para> + </entry> + <entry> + <para>Generates POJO's for all the persistent classes and components found in the given Hibernate configuration.</para> + </entry> + </row> + <row> + <entry> + <para>DAO code</para> + </entry> + <entry> + <para>Generates a set of DAO's for each entity found.</para> + </entry> + </row> + <row> + <entry> + <para>Hibernate XML Mappings</para> + </entry> + <entry> + <para>Generate mapping (<filename>hbm.xml</filename>) files for each entity.</para> + </entry> + </row> + <row> + <entry> + <para>Hibernate XML Configuration</para> + </entry> + <entry> + <para> + Generate a <filename>hibernate.cfg.xml</filename> file. Used to keep the <filename>hibernate.cfg.xml</filename> file updated with any newly discovered mapping files. + </para> + </entry> + </row> + <row> + <entry> + <para>Schema Documentation (.html)</para> + </entry> + <entry> + <para>Generates a set of HTML pages that documents the database schema and some of the mappings.</para> + </entry> + </row> + <row> + <entry> + <para>Generic Exporter (hbmtemplate)</para> + </entry> + <entry> + <para>Fully customizable exporter that can be used to perform custom generation.</para> + </entry> + </row> + <row> + <entry> + <para>Schema Export (.ddl)</para> + </entry> + <entry> + <para>Generates the appropriate SQL DDL and allows you to store the result in a file or export it directly to the database.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <para> + Each Exporter listens to certain properties which can be setup in the <guilabel>Properties</guilabel> section where you can add and remove predefined or customer properties for each of the exporters. The following table lists the time of writing predefined properties: + </para> + <para> + <table> + <title>Exporter Properties</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" colwidth="3*"/> + <thead> + <row> + <entry align="center"> + <para>Name</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>jdk5</para> + </entry> + <entry> + <para>Generate Java 5 syntax</para> + </entry> + </row> + <row> + <entry> + <para>ejb3</para> + </entry> + <entry> + <para>Generate EJB 3 annotations</para> + </entry> + </row> + <row> + <entry> + <para>for_each</para> + </entry> + <entry> + <para> + Specifies for which type of model elements the exporter should create a file and run through the templates. Possible values are: entity, component, configuration + </para> + </entry> + </row> + <row> + <entry> + <para>template_path</para> + </entry> + <entry> + <para>Custom template directory for this specific exporter. You can use Eclipse variables.</para> + </entry> + </row> + <row> + <entry> + <para>template_name</para> + </entry> + <entry> + <para>Name for template relative to the template path</para> + </entry> + </row> + <row> + <entry> + <para>outputdir</para> + </entry> + <entry> + <para>Custom output directory for this specific exporter. You can use Eclipse variables.</para> + </entry> + </row> + <row> + <entry> + <para>file_pattern</para> + </entry> + <entry> + <para> + Pattern to use for the generated files, relatively for the output dir. Example: <filename>{package-name}/{class-name}.java</filename>. + </para> + </entry> + </row> + <row> + <entry> + <para>dot.executable</para> + </entry> + <entry> + <para>Executable to run GraphViz (only relevant, but optional for Schema documentation)</para> + </entry> + </row> + <row> + <entry> + <para>drop</para> + </entry> + <entry> + <para>Output will contain drop statements for the tables, indices and constraints</para> + </entry> + </row> + <row> + <entry> + <para>delimiter</para> + </entry> + <entry> + <para>If specified the statements will be dumped to this file</para> + </entry> + </row> + <row> + <entry> + <para>create</para> + </entry> + <entry> + <para>Output will contain create statements for the tables, indices and constraints</para> + </entry> + </row> + <row> + <entry> + <para>scriptToConsole</para> + </entry> + <entry> + <para>The script will be output to Console</para> + </entry> + </row> + <row> + <entry> + <para>exportToDatabase</para> + </entry> + <entry> + <para>Executes the generated statements against the database</para> + </entry> + </row> + <row> + <entry> + <para>outputFileName</para> + </entry> + <entry> + <para>If specified the statements will be dumped to this file</para> + </entry> + </row> + <row> + <entry> + <para>haltOnError</para> + </entry> + <entry> + <para>Halts the build process if an error occurs</para> + </entry> + </row> + <row> + <entry> + <para>format</para> + </entry> + <entry> + <para>Applies basic formatting to the statements</para> + </entry> + </row> + <row> + <entry> + <para>schemaUpdate</para> + </entry> + <entry> + <para>Updates a schema</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </para> + <para> + To add a property to the chosen Exporter click the <guibutton>Add</guibutton> button in the <guilabel>Properties</guilabel> section. In the resulting dialog you should select the property from the proposed list and the value for it. + </para> + <figure> + <title>Adding the Property for Schema Export (.ddl)</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_8a.png"/> + </imageobject> + </mediaobject> + </figure> + <note> + <title>Tip:</title> + <para>If the property is a directory, it is possible to browse directories in the <guilabel>Value</guilabel> field.</para> + </note> + <figure> + <title>Specifying the Property Value</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_8b.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + <section id="map_config_editor"> + <title>Hibernate Mapping and Configuration File Editor</title> + <para> + The <property>Hibernate Mapping File editor</property> provides XML editing functionality for the <filename>hbm.xml</filename> and <filename>cfg.xml</filename> files. The editor is based on the Eclipse WTP tools and extends its functionality to provide Hibernate specific code completion. + </para> + <figure> + <title>XML Editing Functionality</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_9.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_9.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <section> + <title>Java property/class completion</title> + <para> + Package, class, and field completion is enabled for relevant XML attributes. The auto-completion tool detects its context and limits the completion for a tag (such as <code><property></code>) and only shows the properties and fields available in the enclosing <code><class></code>, <code><subclass></code> etc. It is also possible to navigate from the <filename>hbm.xml</filename> files to the relevant classes and fields in your Java code. + </para> + <figure> + <title>Navigation Functionality</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" fileref="images/plugins/plugins_10.png" format="PNG" scale="80"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_10.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + This is done via the standard hyperlink navigation functionality in Eclipse. By default this is done by pressing <keycap>F3</keycap> while the cursor is on a class or field, or by pressing <keycap>Ctrl</keycap> and the mouse button. + </para> + <para>For Java completion and navigation to work the file needs to reside inside an Eclipse Java project, otherwise the feature is not available.</para> + <note> + <title>Note:</title> + <para>Java completion does not require a Hibernate console configuration to be used.</para> + </note> + </section> + <section> + <title>Table/Column completion</title> + <para>Table and column completion is also available for all table and column attributes. </para> + <figure> + <title>Table and Column Completion</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_11.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_11.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <important> + <title>Important:</title> + <para> + Table and Column completion requires a properly configured Hibernate console configuration, and this configuration should be the default for the project where the <filename>hbm.xml</filename> resides. + </para> + </important> + <para> + You can check which console configuration is selected in the Properties of a project under the <guilabel>Hibernate Settings</guilabel> page. When a proper configuration is selected it will be used to fetch the table and column names in the background. + </para> + <note> + <title>Note:</title> + <para> + Currently it is not recommended to use this feature on large databases since it does not fetch the information iteratively. This will be improved in future versions. + </para> + </note> + </section> + <section> + <title>Configuration property completion</title> + <para> + Code completion for the value of <code><property> name</code> attributes are available when editing the <filename>cfg.xml</filename> file. + </para> + <figure> + <title>Property Completion</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_12.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_12.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + </section> + </section> + <section id="map_config_struct_editor"> + <title>Structured Hibernate Mapping and Configuration File Editor</title> + <para> + The structured editor represents a file in a tree form. It also provides a way to modify the structure of the file and its elements with the help of tables provided on the right-hand area. + </para> + <para> + To open any mapping file in the editor, select <menuchoice><guimenuitem>Open With</guimenuitem><guimenuitem>Hibernate 3.0 XML Editor</guimenuitem></menuchoice> from the context menu of the file. The editor is shown in the following image: + </para> + <figure> + <title>Structured hbm.xml Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_12_a.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + For the configuration file you should select <menuchoice><guimenuitem>Open With</guimenuitem><guimenuitem>Hibernate Configuration 3.0 XML Editor</guimenuitem></menuchoice>. + </para> + <figure> + <title>Structured cfg.xml Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_12_b.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="properties_editor"> + <title>JBoss Tools Properties Editor</title> + <para> + The editor is designed to edit <filename>.properties</filename> files. It contains two tabs: the <guilabel>Properties</guilabel> (UI) tab and the <guilabel>Source</guilabel> tab for manual editing. + </para> + <para> + For <filename>hibernate.properties</filename> files the <guilabel>JBoss Tools Properties Editor</guilabel> provides content assist for both Hibernate properties and values. You can make use of the content assist while editing the file in the <guilabel>Source</guilabel> view and in the <guilabel>Properties</guilabel> view of the editor. + </para> + <para>To add the property in the <guilabel>Properties</guilabel> view, click the <guibutton>Add</guibutton> button.</para> + <figure> + <title>Adding the Property</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/add_property1.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + In the <guilabel>Name</guilabel> field press <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> to invoke the content assist. It will suggest <code>'hibernate.'</code> which is the prefix for all hibernate properties. After selecting <code>'hibernate.'</code> and invoking the content assist again, other prefixes and properties are displayed as the proposals, with a description for each one. + </para> + <figure> + <title>Content Assist for Properties Names</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/add_property2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>When invoking the content assist in the <guilabel>Value</guilabel> field, it also provides a list of proposals.</para> + <figure> + <title>Content Assist for Properties Values</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/add_property3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>In the <guilabel>Source</guilabel> view of the editor, content assist can also be invoked both for properties names and values:</para> + <figure> + <title>Content Assist in the Source view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/add_property4.png"/> + </imageobject> + </mediaobject> + </figure> + <figure> + <title>Content Assist in the Source view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/add_property5.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="rev_xml_editor"> + <title>Reveng.xml Editor</title> + <para> + A <filename>reveng.xml </filename> file is used to customize and control how reverse engineering is performed by the tools. The plugins provide an editor to assist in editing this file. + </para> + <para> + The editor is intended to allow easy definition of type mappings, table include and excludes, and specific override settings for columns, e.g. define an explicit name for a column when the default naming rules are not applicable. + </para> + <note> + <title>Note:</title> + <para> + Not all the features of the <filename>.reveng.xml</filename> file are exposed or fully implemented in the editor, but the main functionality is there. To understand the full flexibility of the <filename>reveng.xml</filename> file, please see <xref linkend="hibernaterevengxmlfile"/> + </para> + </note> + <para> + The editor is activated as soon as a <filename>.reveng.xml </filename> file is opened. To create an initial <filename>reveng.xml </filename> file the <guilabel>Reverse Engineering File Wizard</guilabel> can be started by pressing <keycombo><keycap>Ctrl</keycap><keycap>N</keycap></keycombo> and then selecting <menuchoice><guimenuitem>Hibernate</guimenuitem><guimenuitem>Hibernate Reverse Engineering File (reveng.xml)</guimenuitem></menuchoice>. + </para> + <figure> + <title>ChooseReverse Engineering File Wizard </title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_22.png" format="PNG" /> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_22.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + Or you can get it via the <guilabel>Code Generation Launcher</guilabel> by checking the appropriate section in the <guilabel>Main</guilabel> tab of the <guilabel>Getting Hibernate Code Generation Wizard</guilabel> (see <xref linkend="hib_code_gen"/>). + </para> + <para> + The following screenshot shows the <guilabel>Overview</guilabel> page where the appropriate console configuration is selected (it is auto-detected if Hibernate 3 support is enabled for the project). + </para> + <figure> + <title>Overview Page</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_13.png" format="PNG" /> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_13.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + The <guilabel>Table Filter</guilabel> page allows you to specify which tables to include and exclude. Clicking the <guibutton>Refresh</guibutton> button shows the tables from the database that have not yet been excluded. + </para> + <figure> + <title>Table Filters Page</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_14.png" format="PNG" /> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_14.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + The <guilabel>Type Mappings</guilabel> page is used to specify type mappings from JBDC types to any Hibernate type (including user types) if the default rules are not applicable. To see the database tables press the <guibutton>Refresh</guibutton> button underneath. For more information on type mappings please see the <xref linkend="type_map"/> section. + </para> + <figure> + <title>Type Mappings Page</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_15.png" format="PNG" /> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_15.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + The <guilabel>Table and Columns</guilabel> page allows you to explicitly set which details (e.g. which hibernatetype and propertyname) should be used in the reverse engineered model. For more details on how to configure the tables while reverse engineering read <xref linkend="tab_and_col"/>. + </para> + <figure> + <title>Table and Columns Page</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_16.png" format="PNG" /> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_16.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section id="hib_console"> + <title>Hibernate Console Perspective</title> + <para> + The <guilabel>Hibernate Console Perspective</guilabel> combines a set of views which allow you to see the structure of your mapped entities and classes, edit HQL queries, execute the queries, and view the results. To use this perspective you need to create a <guilabel>Hibernate Console Configuration</guilabel> (see <xref linkend="console_conf"/> for more information). + </para> + <section> + <title>Viewing the entity structure</title> + <para> + To view your new configuration and entity or class structure, switch to the <guilabel>Hibernate Configurations View</guilabel>. Expanding the tree allows you to browse the class or entity structure, as well as view the relationships. + </para> + <figure> + <title>Hibernate Console Perspective</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_17.png"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_17.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + The <guilabel>Console Configuration</guilabel> does not dynamically adjust to changes performed in mappings and Java code. To reload the configuration select the configuration and click the <guibutton>Reload</guibutton> button in the view toolbar or in the context menu. + </para> + <para> + It is possible to open source and mapping files for objects showed in the <guilabel>Hibernate Configurations View</guilabel>. Just bring up the context menu for an object and select <guimenuitem>Open Source File</guimenuitem> to see the appropriate Java class or <guimenuitem>Open Mapping File</guimenuitem> to open a <filename>.hbm.xml</filename> file. + </para> + <figure> + <title>Opening Source for Objects</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_17_a.png"/> + </imageobject> + </mediaobject> + </figure> + <section id="map_diagram"> + <title>Mapping Diagram</title> + <para> + In order to visualize how entities are related, as well as view their structures, a <guilabel>Mapping Diagram</guilabel> is provided. It is available by right clicking on the entity you want view a mapping diagram for and then selecting <guilabel>Mapping Diagram</guilabel>. + </para> + <figure> + <title>Mapping Diagram</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_18.png"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_18.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + To make <guilabel>Mapping Diagram</guilabel> usage easier you can use the <guilabel>Rules</guilabel>, <guilabel>Grid</guilabel>, <guilabel>Snap to Geometry</guilabel> checkboxes in the <guimenu>View</guimenu> menu. + </para> + <figure> + <title>View menu</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/map_diagram1.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + If you select the <guilabel>Rulers</guilabel> checkbox, the view print page scale will be added to the page. The numbers on the scale displays its size in inches. If you click on the scale a <guilabel>Ruler Guide</guilabel> will appear on the diagram. You can connect any diagram item to it. To connect the items you should move their tops to the Ruler Guide. And while moving the ruler guide, the items will be moved together with it as a whole. + </para> + <figure> + <title>Moving the Ruler guide</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/map_diagram2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>If you select the <guilabel>Grid</guilabel> checkbox, a grid will appear on the diagram.</para> + <figure> + <title>Grid on Mapping diagram</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/map_diagram3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The <guilabel>Snap to Geometry</guilabel> checkbox allows you to align the diagram items with the grid.</para> + <para> + For better navigating through the diagram use the <guilabel>Outline view</guilabel>, which is available in the structural and graphical modes. + </para> + <figure> + <title>Navigating in the Structural Mode</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_18_a.png"/> + </imageobject> + </mediaobject> + </figure> + <para>To switch between the view modes, use the buttons in the top-right corner of the <guilabel>Outline view</guilabel>.</para> + <figure> + <title>Navigating in the Graphical Mode</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_18_b.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The options in the context menu of the mapping diagram are listed in the next table.</para> + <table> + <title>Context Menu Options of the Mapping Diagram</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" align="left" colwidth="1*"/> + <colspec colnum="3" align="left" colwidth="3*"/> + <thead> + <row> + <entry align="center"> + <para>Icon</para> + </entry> + <entry align="center"> + <para>Command</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/toggleConnections.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Show|Hide connections</para> + </entry> + <entry>Allows you to select what types of connections should be shown on the diagram: <itemizedlist> <listitem> <para>Property Mappings</para> - </listitem> - <listitem> - <para>Class Mappings</para> - </listitem> - <listitem> - <para>Associations</para> - </listitem> - <listitem> - <para>Foreign key constraints</para> - </listitem> - </itemizedlist></entry> - </row> - <row> - <entry> - <para/> - </entry> - <entry> - <para>Select All</para> - </entry> - <entry> - <para>Makes all the diagram elements selected</para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/autoLayout.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Auto layout</para> - </entry> - <entry> - <para>Used to dispose all the items of the diagram in a standard manner</para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/exportAsImage.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Export as Image</para> - </entry> - <entry> - <para>Allows to export a diagram as <emphasis><property>.png - </property>,</emphasis> - <emphasis> - <property>.jpeg</property> - </emphasis> or <emphasis> - <property>.bmp </property> - </emphasis></para> - </entry> - </row> - </tbody> - </tgroup> - </table> - <para>When you open the context menu while clicking an item on the diagram, it quite differs - from the one described before.</para> - <figure> - <title>Context Menu in Mapping Item</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_18_g.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The next table describes all the extra options in the menu of mapping items:</para> - <table> - <title>Extra Options in the Context Menu of Mapping Item</title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" align="left" colwidth="1*"/> - <colspec colnum="3" align="left" colwidth="3*"/> - <thead> - <row> - <entry align="center"> - <para>Icon</para> - </entry> - <entry align="center"> - <para>Command</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/openSourceFile_but.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Open Source File</para> - </entry> - <entry> - <para>Makes it possible to open a source file for a chosen object/element. The - selected element will be highlighted in the open file.</para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/openMappingFile_but.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Open Mapping File</para> - </entry> - <entry> - <para>Makes it possible to open a mapping file for a chosen object/element. The - selected element will be highlighted in the open file.</para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/visibleState.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Show|Hide shape(s)</para> - </entry> - <entry> - <para>Used to hide/show an item on the mapping diagram</para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/expandState.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Expand|Collapse shape(s)</para> - </entry> - <entry> - <para>Used for expanding/collapsing fields of the item</para> - </entry> - </row> - </tbody> - </tgroup> - </table> - <note> - <title>Tip:</title> - <para>All the described types of the context menu are also available in the <property - >Outline</property> view.</para> - </note> - <para>The below table lists the actions that could be performed using the keyboard keys (or - keys combinations).</para> - <table> - <title>Hibernate Mapping Diagram Shortcut Keys</title> - <tgroup cols="2"> - <colspec colnum="1" align="left" colwidth="3*"/> - <colspec colnum="2" align="left" colwidth="1*"/> - <thead> - <row> - <entry align="center"> - <para>Command</para> - </entry> - <entry align="center"> - <para>Binding</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para>Scroll the diagram content</para> - </entry> - <entry> - <para>Ctrl + Shift + arrows</para> - </entry> - </row> - <row> - <entry> - <para>Collapse/Expand selected item(s)</para> - </entry> - <entry> - <para> Enter </para> - </entry> - </row> - <row> - <entry> - <para>Show/Hide selected item(s)</para> - </entry> - <entry> - <para> + </para> - </entry> - </row> - <row> - <entry> - <para>Sort items in alphabetical order or return the initial state</para> - </entry> - <entry> - <para>Space</para> - </entry> - </row> - <row> - <entry> - <para>Navigate between the items</para> - </entry> - <entry> - <para>Arrows</para> - </entry> - </row> - </tbody> - </tgroup> - </table> - <para>It's possible to save the diagram in the eclipse workspace. Click the usual - <emphasis> - <property>File > Save As</property> - </emphasis> option, the wizard will ask you to set the location within you project where - to save the file and give the name for the diagram. The item's names concatenated - with the ampersand symbols are set as the default name for a diagram. The file is saved - with the <literal>.hibernate</literal> extension.</para> - <figure> - <title>The Diagram saved in the Workspace</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/saveDiagram.png"/> - </imageobject> - </mediaobject> - </figure> - <note> - <title>Note:</title> - <para>If you restart the Eclipse with the mapping diagram opened, the mapping diagram will - be restored with the message like on the figure below. To view the diagram content, you - should perform the refreshing.</para> - </note> - <figure> - <title>The Diagram after Restarting the Eclipse</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/diagram1.png"/> - </imageobject> - </mediaobject> - </figure> - <figure> - <title>The Diagram after Refreshing</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/diagram2.png"/> - </imageobject> - </mediaobject> - </figure> - <para>There are some useful commands in the toolbar.</para> - <figure> - <title>The Diagram View Toolbar</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/diagramToolbar.png"/> - </imageobject> - </mediaobject> - </figure> - <para>They are described in the table below.</para> - <table> - <title>Command in Diagram View Toolbar </title> - <tgroup cols="3"> - <colspec colnum="1" align="left" colwidth="1*"/> - <colspec colnum="2" align="left" colwidth="1*"/> - <colspec colnum="3" align="left" colwidth="3*"/> - <thead> - <row> - <entry align="center"> - <para>Icon</para> - </entry> - <entry align="center"> - <para>Command</para> - </entry> - <entry align="center"> - <para>Description</para> - </entry> - </row> - </thead> - <tbody> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/toolbarRefresh.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Refresh Visual Mapping</para> - </entry> - <entry> - <para>It update <property>Mapping Diagram</property> if <property>Console - Configuration</property> was changed. </para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/toolbarZoom.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Zoom Box</para> - </entry> - <entry> - <para>Used to define scale of the diagram. Also it's used for <property>Mapping - Diagram</property> printing. If you want to put the whole <property - >diagram</property> to one print page, you need select <property - >Page</property> option in the <property>Zoom Box</property>.</para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/toolbarAutolayout.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Auto layout</para> - </entry> - <entry> - <para>Used to arrange all diagram items in a standard manner.</para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/toolbarShowHideConnections.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Show|Hide connections</para> - </entry> - <entry> - <para>Used to show or hide connection on the diagram. Moreover you can choose what - type of connections must be present on the diagram (<property>Property - Mappings</property>, <property>Class Mappings</property>, <property - >Associations</property> or <property>Foreign key constraints</property>) - .</para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/toolbarExpandCollapse.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para>Expand|Collapse</para> - </entry> - <entry> - <para>Used for expanding/collapsing fields of the item.</para> - </entry> - </row> - <row> - <entry> - <para> - <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/toolbarShowHideShapes.png"/> - </imageobject> - </inlinemediaobject> - </para> - </entry> - <entry> - <para> Show|Hide shape(s)</para> - </entry> - <entry> - <para>Used to hide/show an item on the mapping diagram.</para> - </entry> - </row> - </tbody> - </tgroup> - </table> - </section> - </section> - <section> - <title>Prototyping Queries</title> - <para>Queries can be prototyped by entering them into the <property>HQL</property> or - <property>Criteria Editor</property>. To execute a query you should click the green run - button in the editor toolbar or press <emphasis> - <property>Ctrl+Enter</property> - </emphasis>.</para> - <section id="hql_and_criteria_editors"> - <title>HQL Editor and Hibernate Criteria Editor</title> - <para>To open the query editors right-click your project <property>Console - Configuration</property> and select <property>HQL Editor</property> (or <property - >Hibernate Criteria Editor</property>).</para> - <figure> - <title>Opening HQL Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/prototypingQueries.png"/> - </imageobject> - </mediaobject> - </figure> - <note> - <title>Tip:</title> - <para>If the context menu items are disabled then you need at first to create a <property - >Session Factory</property>. That is done by simply expanding the <property>Session - Factory</property> node.</para> - </note> - <para>When open the editors they should automatically detect the chosen Console - Configuration.</para> - <para>To get a prefill query for any entity (or any entity child node) listed in the - <emphasis> - <property>Session Factory</property> - </emphasis> you should double-click it. This will open the <property>HQL Editor</property> - with the associated query.</para> - <para>Choosing <emphasis> - <property>HQL Editor</property> - </emphasis> in the context menu for any entity (or any entity child node) will also open - the HQL editor with the associated query. If you choose <emphasis> - <property>Hibernate Criteria Editor</property> - </emphasis> in the context menu, it will open <property>Hibernate Criteria - Editor</property> with the associated criteria.</para> - <figure> - <title>Generating Simple Queries</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_19.png" - format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_19.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>It's also possible to copy a portion of code from <emphasis> - <property>.java</property> - </emphasis> file into the <property>HQL</property> or <property>Criteria - editor</property>. To do this make use of the Quick Fix option (<emphasis> - <property>Ctrl + 1</property>)</emphasis>.</para> - <figure> - <title>Quick Fix Option Demonstration</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_19_b.png"/> - </imageobject> - </mediaobject> - </figure> - <para>You can also update the original java code according to changes in the HQL or Criteria - editor. For that you should save your HQL/Criteria query and submit the replacing in - appeared confirmation dialog.</para> - <figure> - <title>Updating Java Code</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_19_c.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Also you can pin <property>HQL editor</property> and <property>Criteria - editor</property> for one tab in <property>Hibernate Query Result</property> view. For - that you need click on <property>Stick result to one tab</property> - button(<inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/sticky_but.png"/> - </imageobject> - </inlinemediaobject> ). In the issue query executions results will be shown in one tab (no - more will be opened). </para> - <para> Moreover you are able to rename tab in <property>Hibernate Query Result</property>. - Click the tab, and type a new name in <property>Property View->Tab name field</property>. </para> - <figure> - <title>Tab Renaming</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/plugins_19_d.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - <section> - <title>Error Handling</title> - <para>Errors during creation of the <property>Session Factory</property> or running the - queries (e.g. if your configuration or query is incorrect) will be shown in a message - dialog or inclined in the view that detected the error, you may get more information about - the error in the <property>Error Log View</property> on the right pane.</para> - <para>Results of a query will be shown in the <property>Hibernate Query Result - View</property> and details of possible errors (syntax errors, database errors, etc.) - can be seen in the <property>Error Log View</property>.</para> - <note> - <title>Note:</title> - <para>HQL queries are executed by default using <literal>list()</literal> thus without any - limit of the size of the output the query could return a large result set. You might run - out of memory. To avoid this you can put a value in the Max results field to reduce the - number of elements returned.</para> - </note> - </section> - <section> - <title>Dynamic Query Translator</title> - <para>If the <property>Hibernate Dynamic Query Translator View</property> is visible while - writing in the <property>HQL Editor</property> it will show the generated SQL for a HQL - query.</para> - <figure> - <title>Hibernate Dynamic Query Translator View</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_20.png" - format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_20.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>The translation is done each time you stop typing into the editor, if there are errors - in the HQL the parse exception will be shown embedded in the view.</para> - </section> - </section> - <section> - <title>Properties View</title> - <para>As you can see on the figure,when clicking on class/entity <property>Properties - view</property> shows the number of query results as well as the time of executing.</para> - <figure> - <title>Properties View</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_21_a.png" - format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_21_a.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>It also displays the structure of any persistent object selected in the <property - >Hibernate Query Results View</property>. Editing is not yet supported.</para> - <figure> - <title>Properties View for Selected Object</title> - <mediaobject> - <imageobject role="fo"> - <imagedata align="center" scale="80" fileref="images/plugins/plugins_21_b.png" - format="PNG"/> - </imageobject> - <imageobject role="html"> - <imagedata align="center" fileref="images/plugins/plugins_21_b.png" format="PNG"/> - </imageobject> - </mediaobject> - </figure> - <para>You can also use <property>Properties view</property> when clicking on the configuration - itself in Hibernate Configuration View( <xref linkend="modif_console_conf"/>). </para> - </section> - </section> - <section id="jpa_annotations"> - <title>Hibernate:add JPA annotations refactoring </title> - <para>Using this wizard you can add the next Hibernate annotations to the class: <emphasis> - <property>@Column</property> - </emphasis>,<emphasis> - <property>@Entity</property> - </emphasis>,<emphasis> - <property>@ManyToOne</property> - </emphasis>,<emphasis> - <property>@OneToMany</property> - </emphasis>,<emphasis> - <property>@OneToOne</property> - </emphasis>,<emphasis> - <property>@ManyToMany</property> - </emphasis>,<emphasis> - <property>@MappedSuperclass</property> - </emphasis>,<emphasis> - <property>@Id</property> - </emphasis>,<emphasis> - <property>@GeneratedValue</property> - </emphasis> ,<emphasis> - <property>@Version </property> - </emphasis> + </listitem> + <listitem> + <para>Class Mappings</para> + </listitem> + <listitem> + <para>Associations</para> + </listitem> + <listitem> + <para>Foreign key constraints</para> + </listitem> + </itemizedlist> + </entry> + </row> + <row> + <entry> + <para/> + </entry> + <entry> + <para>Select All</para> + </entry> + <entry> + <para>Selects all the diagram elements</para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/autoLayout.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Auto layout</para> + </entry> + <entry> + <para>Used to dispose all the items in the diagram in a standard manner</para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/exportAsImage.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Export as Image</para> + </entry> + <entry> + <para> + Allows the diagram to be exported as a <filename>PNG</filename>,<filename>JPEG</filename> or <filename>BMP</filename> file + </para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <para>When you open the context menu for an item in the diagram, it differs quite significantly from the one described before.</para> + <figure> + <title>Context Menu in Mapping Item</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_18_g.png"/> + </imageobject> + </mediaobject> + </figure> + <para>The next table describes the additional options found in the mapping items context menu:</para> + <table> + <title>Extra Options in the Context Menu of Mapping Item</title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" align="left" colwidth="1*"/> + <colspec colnum="3" align="left" colwidth="3*"/> + <thead> + <row> + <entry align="center"> + <para>Icon</para> + </entry> + <entry align="center"> + <para>Command</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/openSourceFile_but.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Open Source File</para> + </entry> + <entry> + <para> + Opens the source file for a chosen object or element. The selected element will be highlighted in the open file. + </para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/openMappingFile_but.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Open Mapping File</para> + </entry> + <entry> + <para> + Opens a mapping file for a chosen object or element. The selected element will be highlighted in the open file. + </para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/visibleState.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Show|Hide shape(s)</para> + </entry> + <entry> + <para>Used to hide or show an item on the mapping diagram</para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/expandState.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Expand|Collapse shape(s)</para> + </entry> + <entry> + <para>Used to expand and collapse fields displayed by the item</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <note> + <title>Tip:</title> + <para>All these context menu options are also available in the <guilabel>Outline</guilabel> view.</para> + </note> + <para>The following table lists the available keyboard shortcuts.</para> + <table> + <title>Hibernate Mapping Diagram Shortcut Keys</title> + <tgroup cols="2"> + <colspec colnum="1" align="left" colwidth="3*"/> + <colspec colnum="2" align="left" colwidth="1*"/> + <thead> + <row> + <entry align="center"> + <para>Command</para> + </entry> + <entry align="center"> + <para>Binding</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para>Scroll the diagram content</para> + </entry> + <entry> + <para> + <keycombo> + <keycap>Ctrl</keycap> + <keycap>Shift</keycap> + <keycap>arrows</keycap> + </keycombo> + </para> + </entry> + </row> + <row> + <entry> + <para>Collapse or Expand selected item(s)</para> + </entry> + <entry> + <para> + <keycap>Enter</keycap> + </para> + </entry> + </row> + <row> + <entry> + <para>Show or Hide selected item(s)</para> + </entry> + <entry> + <para> + <keycap>+</keycap> + </para> + </entry> + </row> + <row> + <entry> + <para>Sort items in alphabetical order or return to the initial state</para> + </entry> + <entry> + <para> + <keycap>Space</keycap> + </para> + </entry> + </row> + <row> + <entry> + <para>Navigate between the items</para> + </entry> + <entry> + <para> + <keycap>Arrows</keycap> + </para> + </entry> + </row> + </tbody> + </tgroup> + </table> + <para> + It is possible to save the diagram in the Eclipse workspace. Select <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>Save As</guimenuitem></menuchoice>, and the wizard will ask you to specify the location within you project where you wish to save the file, and provide the name for the diagram. The default name is the item's names concatenated with the ampersand symbols. The file is saved with the <filename>.hibernate</filename> extension. + </para> + <figure> + <title>The Diagram saved in the Workspace</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/saveDiagram.png"/> + </imageobject> + </mediaobject> + </figure> + <note> + <title>Note:</title> + <para> + If you restart Eclipse with the mapping diagram opened, the mapping diagram will be restored with the message like on the figure below. To view the diagram content, you should refresh the view. + </para> + </note> + <figure> + <title>The Diagram after Restarting the Eclipse</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/diagram1.png"/> + </imageobject> + </mediaobject> + </figure> + <figure> + <title>The Diagram after Refreshing</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/diagram2.png"/> + </imageobject> + </mediaobject> + </figure> + <para>There are some useful commands in the toolbar.</para> + <figure> + <title>The Diagram View Toolbar</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/diagramToolbar.png"/> + </imageobject> + </mediaobject> + </figure> + <para>They are described in the table below.</para> + <table> + <title>Command in Diagram View Toolbar </title> + <tgroup cols="3"> + <colspec colnum="1" align="left" colwidth="1*"/> + <colspec colnum="2" align="left" colwidth="1*"/> + <colspec colnum="3" align="left" colwidth="3*"/> + <thead> + <row> + <entry align="center"> + <para>Icon</para> + </entry> + <entry align="center"> + <para>Command</para> + </entry> + <entry align="center"> + <para>Description</para> + </entry> + </row> + </thead> + <tbody> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/toolbarRefresh.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Refresh Visual Mapping</para> + </entry> + <entry> + <para>It will update the <guilabel>Mapping Diagram</guilabel> the if <guilabel>Console Configuration</guilabel> was changed. </para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/toolbarZoom.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Zoom Box</para> + </entry> + <entry> + <para> + Used to define scale of the diagram. It is also used for printing <guilabel>Mapping Diagrams</guilabel>. If you want to print the whole <guilabel>diagram</guilabel> to one page, you need select the <guilabel>Page</guilabel> option in the <guilabel>Zoom Box</guilabel> drop down list. + </para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/toolbarAutolayout.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Auto layout</para> + </entry> + <entry> + <para>Used to arrange all diagram items in a standard manner.</para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/toolbarShowHideConnections.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Show|Hide connections</para> + </entry> + <entry> + <para> + Used to show or hide a connection on the diagram. You can also choose what type of connections must be present on the diagram (<guilabel>Property Mappings</guilabel>, <guilabel>Class Mappings</guilabel>, <guilabel>Associations</guilabel> or <guilabel>Foreign key constraints</guilabel>). + </para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/toolbarExpandCollapse.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para>Expand|Collapse</para> + </entry> + <entry> + <para>Used for expanding or collapsing fields of the item.</para> + </entry> + </row> + <row> + <entry> + <para> + <inlinemediaobject> + <imageobject> + <imagedata fileref="images/plugins/toolbarShowHideShapes.png"/> + </imageobject> + </inlinemediaobject> + </para> + </entry> + <entry> + <para> Show|Hide shape(s)</para> + </entry> + <entry> + <para>Used to hide or show an item on the mapping diagram.</para> + </entry> + </row> + </tbody> + </tgroup> + </table> + </section> + </section> + <section> + <title>Prototyping Queries</title> + <para> + Queries can be prototyped by entering them into the <guilabel>HQL</guilabel> or <guilabel>Criteria Editor</guilabel>. To execute a query click the green run button in the editor toolbar, or press <keycombo><keycap>Ctrl</keycap><keycap>Enter</keycap></keycombo>. + </para> + <section id="hql_and_criteria_editors"> + <title>HQL Editor and Hibernate Criteria Editor</title> + <para> + To open the query editors right-click your projects <guilabel>Console Configuration</guilabel> and select <guimenuitem>HQL Editor</guimenuitem> (or <guimenuitem>Hibernate Criteria Editor</guimenuitem>). + </para> + <figure> + <title>Opening HQL Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/prototypingQueries.png"/> + </imageobject> + </mediaobject> + </figure> + <note> + <title>Tip:</title> + <para> + If the context menu items are disabled then you need at first to create a <guilabel>Session Factory</guilabel>. That is done by expanding the <guilabel>Session Factory</guilabel> node. + </para> + </note> + <para>When they are opened, the editors they should automatically detect the chosen <guilabel>Console Configuration</guilabel>.</para> + <para> + To generate a predefined query for any entity (or any entity child node) listed in the <guilabel>Session Factory</guilabel> you should double-click it. This will open the <guilabel>HQL Editor</guilabel> with the associated query. + </para> + <para> + Choosing <guimenuitem>HQL Editor</guimenuitem> in the context menu for any entity (or any entity child node) will also open the HQL Editor with the associated query. If you select <guimenuitem>Hibernate Criteria Editor</guimenuitem> in the context menu, it will open <guilabel>Hibernate Criteria Editor</guilabel> with the associated criteria. + </para> + <figure> + <title>Generating Simple Queries</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_19.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_19.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + It is also possible to copy a portion of code from a <filename>.java</filename> file into the <guilabel>HQL</guilabel> or <guilabel>Criteria editor</guilabel>. To do this make use of the Quick Fix option (<keycombo><keycap>Ctrl</keycap><keycap>1</keycap></keycombo>). + </para> + <figure> + <title>Quick Fix Option Demonstration</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_19_b.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + You can also update the original Java code with changes made in the HQL or Criteria editor. For that you should save your HQL/Criteria query and submit the replacement code when prompted by the confirmation dialog. + </para> + <figure> + <title>Updating Java Code</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_19_c.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + In addition, you can pin the <guilabel>HQL editor</guilabel> and <guilabel>Criteria editor</guilabel> as a tab in the <guilabel>Hibernate Query Result</guilabel> view. For that you need click on the <guibutton>Stick result to one tab</guibutton> button (<inlinemediaobject><imageobject><imagedata fileref="images/plugins/sticky_but.png"/></imageobject></inlinemediaobject>). In this state query executions results will be shown in one tab (no more will be opened). + </para> + <para> + You are able to rename the <guilabel>Hibernate Query Result</guilabel> tab. Click the tab, and type a new name in the <menuchoice><guimenuitem>Property View</guimenuitem><guimenuitem>Tab name</guimenuitem></menuchoice> field. + </para> + <figure> + <title>Tab Renaming</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/plugins_19_d.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + <section> + <title>Error Handling</title> + <para> + Errors raised during the creation of the <guilabel>Session Factory</guilabel>, or when executing the queries (e.g. if your configuration or query is incorrect), will be shown in a message dialog or inclined in the view that detected the error. You may get more information about the error in the <guilabel>Error Log</guilabel> view on the right pane. + </para> + <para> + Results of a query will be shown in the <guilabel>Hibernate Query Result</guilabel> view and details of possible errors (syntax errors, database errors, etc.) can be seen in the <guilabel>Error Log</guilabel> view. + </para> + <note> + <title>Note:</title> + <para> + HQL queries are executed by default using the <code>list()</code> function, and without any row limit could return a large result set. You may run out of memory. To avoid this you can enter a value in the <guilabel>Max</guilabel> results field to reduce the number of elements that are returned. + </para> + </note> + </section> + <section> + <title>Dynamic Query Translator</title> + <para> + If the <guilabel>Hibernate Dynamic Query Translator</guilabel> view is visible, it will show the generated SQL for a HQL query while you write in the <guilabel>HQL Editor</guilabel> . + </para> + <figure> + <title>Hibernate Dynamic Query Translator View</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_20.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_20.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + The translation is performed each time you stop typing in the editor. If there are errors in the HQL code the parse exception will be shown embedded in the view. + </para> + </section> + </section> + <section> + <title>Properties View</title> + <para> + As you can see in the figure below, when clicking on class or entity the <guilabel>Properties</guilabel> view shows the number of query results as well as the execution time. + </para> + <figure> + <title>Properties View</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_21_a.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_21_a.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + It also displays the structure of any persistent object selected in the <guilabel>Hibernate Query Results View</guilabel>. Editing is not yet supported. + </para> + <figure> + <title>Properties View for Selected Object</title> + <mediaobject> + <imageobject role="fo"> + <imagedata align="center" scale="80" fileref="images/plugins/plugins_21_b.png" format="PNG"/> + </imageobject> + <imageobject role="html"> + <imagedata align="center" fileref="images/plugins/plugins_21_b.png" format="PNG"/> + </imageobject> + </mediaobject> + </figure> + <para> + You can also use <guilabel>Properties</guilabel> view when clicking on the configuration itself in <guilabel>Hibernate Configuration</guilabel> view (see <xref linkend="modif_console_conf"/>). + </para> + </section> + </section> + <section id="jpa_annotations"> + <title>Hibernate:add JPA annotations refactoring </title> + <para>Using this wizard you can add the following Hibernate annotations to a class: <code>@Column</code>, <code>@Entity</code>, <code>@ManyToOne</code>, <code>@OneToMany</code>, <code>@OneToOne</code>, <code>@ManyToMany</code>, <code>@MappedSuperclass</code>, <code>@Id</code>, <code>@GeneratedValue</code>, <code>@Version </code> + </para> + <itemizedlist> + <listitem> + <para><code>@Column</code> is added to all String properties.</para> + </listitem> + <listitem> + <para> + <code>@Entity</code> is always declared before any class where it has not yet been defined.</para> + </listitem> + <listitem> + <para> + <code>@ManyToOne</code>, <code>@OneToMany</code>, <code>@OneToOne</code>, <code>@ManyToMany</code> - these annotations are declared according to the classes hierarchy. + </para> + </listitem> + <listitem> + <para> + <code>@MappedSuperclass</code> is added to abstract superclasses.</para> + </listitem> + <listitem> + <para> + <code>@Id</code>, <code>@GeneratedValue</code> are only added automatically to the properties under the name "Id", where they have not yet been defined. + </para> + </listitem> + <listitem> + <para> + <code>@Version</code> is declared in case you select optimistic locking (see <xref linkend="optim_lock"/>).</para> + </listitem> + </itemizedlist> + <note> + <title>Note:</title> + <para> + This section doesn't cover the definitions of the <property>Hibernate annotations</property>. For more information read the <ulink url="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html/">Hibernate Annotations Documentation</ulink>. + </para> + </note> + <para> + To open this wizard you should right click the class you want to add the annotations to and select <menuchoice><guimenuitem>Source</guimenuitem><guimenuitem>Generate Hibernate/JPA annotations</guimenuitem></menuchoice> from the context menu. You will see the <guilabel>Hibernate: add JPA annotations</guilabel> dialog. + </para> + <figure> + <title>Starting Hibernate:add JPA annotations dialog</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/annotations1.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + The top section of this dialog lists all the classes that will be passed through refactoring. Next to the class you have selected, this list also displays its superclasses and the classes that the objects present in the current class as properties. If you want to add new classes or packages to the list, you should click the <guibutton>Back</guibutton> button. This will display the <guilabel>Add classes and packages</guilabel> page. + </para> + <figure> + <title>Add classes and packages page </title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/annotations1_a.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + Here you can add additional classes or entire packages, and you can limit the dependencies depth by selecting the <guilabel>depth control</guilabel> option (you can find more information on this option in <xref linkend="depth_control"/>). When you are finished click the <guibutton>Next</guibutton> button and you will be returned to <guilabel>The following classes will be changed</guilabel> page.</para> + <para> + By default the tags are added to the fields of selected classes. You can change this option to <guilabel>Getters</guilabel> in the <guilabel>Preferred location of Annotations</guilabel> drop down list, which results in the annotations being added to the getter methods. If you choose <guilabel>Auto select from class preference</guilabel> then the annotations are added according to the position of the majority of the existing annotations. + </para> + <para> + If it is necessary to map your <code>String</code> properties to the columns that length differ from the default value (255), change the <guilabel>Default string length</guilabel> field and the <code>@Column(length = your length)</code> annotation will be created for every <code>String</code> property. + </para> + <para id="optim_lock"> + You can add optimistic locking capabilities to an entity bean by selecting the <guilabel>Enable optimistic locking</guilabel> checkbox. This operation will add the version property to all the selected classes. The property will be also annotated with <code>@Version</code>, and a getter and setter will be created. If the property is already exists, it won't be created, but the getters and setters will be generated. If there is already <code>@MappedSuperclass</code> annotation with <code>@Version</code> in the base class of the current class, <code>@Version</code> is not inserted into the current class. </para> - <itemizedlist> - <listitem> - <para><emphasis> - <property>@Column</property> - </emphasis> is added to all String properties.</para> - </listitem> - <listitem> - <para><emphasis> - <property>@Entity</property> - </emphasis> is always declared before any class where it doesn't present.</para> - </listitem> - <listitem> - <para><emphasis> - <property>@ManyToOne</property> - </emphasis>,<emphasis> - <property>@OneToMany</property> - </emphasis>,<emphasis> - <property>@OneToOne</property> - </emphasis>,<emphasis> - <property>@ManyToMany</property> - </emphasis> - this annotations are declared according to the classes hierarchy.</para> - </listitem> - <listitem> - <para><emphasis> - <property>@MappedSuperclass</property> - </emphasis> is added to abstract superclasses.</para> - </listitem> - <listitem> - <para><emphasis> - <property>@Id</property> - </emphasis>,<emphasis> - <property>@GeneratedValue</property> - </emphasis> are added automatically only to the properties under the name "Id",where they - don't present.</para> - </listitem> - <listitem> - <para><emphasis> - <property>@Version</property> - </emphasis> is declared in case you select <xref linkend="optim_lock"/>.</para> - </listitem> - </itemizedlist> - <note> - <title>Note:</title> - <para>This section doesn't cover the meaning of the <property>Hibernate annotations</property> - , for more information read <ulink - url="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html/">Hibernate - Annotations Documentation</ulink> .</para> - </note> - <para>To open this wizard you should right click the class you want to enrich with annotations - <emphasis> - <property>>Source>Generate Hibernate/JPA annotations</property> - </emphasis>. You will see the Hibernate:add JPA annotations dialog. </para> - <figure> - <title>Starting Hibernate:add JPA annotations dialog</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/annotations1.png"/> - </imageobject> - </mediaobject> - </figure> - <para> In the top of it you can see the list of all classes that will be passed through - refactoring. Besides the class you have selected in this list you can also find its - superclasses and the classes that objects present in the current class as properties. If you - want to add new classes or package to the list of classes, you should click the <property - >Back</property> button. In result you will see <property>Add classes and - packages</property> page.</para> - <figure> - <title>Add classes and packages page </title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/annotations1_a.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Here you can add one more classes or whole package, moreover you can limit dependencies - depth by selecting <property>depth control</property> option (more about this option you will - find in <xref linkend="depth_control"/>). When finished - just press the <property>Next</property> button and you will be returned to <property>The - following classes will be changed</property> page and will be able to continue work with - it.</para> - <para>By default the tags are added to the fields of selected classes. But you can change this - option to <emphasis> - <property>Getters</property> - </emphasis>in <emphasis> - <property> Preferred location of Annotations</property> - </emphasis> dropdownlist and then all the annotations will be added to the getter methods. If - you choose <emphasis> - <property>Auto select from class preference</property> - </emphasis> then the annotations are added according to the majority of the already existed - ones positions. </para> - <para> If it's nessecary to map your String properties to the columns that length differ from - the default value(255) ,change <emphasis> - <property>Default string length field</property> - </emphasis> and <code>@Column(length = your length)</code> will be created before every String - property. </para> - <para id="optim_lock">You can add optimistic locking capability to an entity bean by selecting - <emphasis> - <property>Enable optimistic locking</property> - </emphasis> checkbox. This operation will add version property to all the selected classes. - The property will be also annotated with @Version ,getter and setter will be created. If the - property is already exists,it won't be created ,but the getters,setters will be generated. If - there is already @MappedSuperclass with version in the base class of the current class - - <emphasis> - <property>"version"</property> - </emphasis> is not inserted into the current class. </para> - <para>After defining all necessary settings in the current step press <emphasis> - <property>Next</property> - </emphasis> and follow the next wizard steps. </para> - <figure> - <title>Hibernate:add JPA annotations view</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/annotations2.png"/> - </imageobject> - </mediaobject> - </figure> - <para>The view represents two windows: one with the source code and and the second with - refactored one. With the help of <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/butt1.png"/> - </imageobject> - </inlinemediaobject> ,<inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/butt2.png"/> - </imageobject> - </inlinemediaobject> ,<inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/butt3.png"/> - </imageobject> - </inlinemediaobject> ,<inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/butt4.png"/> - </imageobject> - </inlinemediaobject> buttons you can quickly navigate between the differences in the code. If - you don't agree with some changes you can't undo them but you can remove the class from the - list of classes that need refactoring. </para> - <figure> - <title>List of classes that need refactoring</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/annotations3.png"/> - </imageobject> - </mediaobject> - </figure> - <para>To apply the changes click <emphasis> - <property>Finish</property> - </emphasis>.</para> - </section> - <section id="debug_log"> - <title>Enable debug logging in the plugins</title> - <para>It is possible to configure the eclipse plugin to route all logging made by the plugins - and hibernate code it self to the <property>Error Log View</property> in Eclipse.</para> - <para><property>Error Log View</property> is very useful tool to solve any problem which appears - in Hibernate Tools Plugins. You can use if there are troubles with setting up <property - >Hibernate Console Configuration</property>.</para> - <para>This is done by editing the <emphasis> - <property>hibernate-log4j.properties</property> - </emphasis> in <emphasis> - <property>org.hibernate.eclipse/ directory/jar</property> - </emphasis>. This file includes a default configuration that only logs WARN and above to a set - of custom appenders (PluginFileAppender and PluginLogAppender). You can change these settings - to be as verbose or silent as you please - see <ulink url="http://www.hibernate.org/5.html" - >Hibernate Documentation</ulink> for interesting categories and Log4j documentation.</para> - <section> - <title>Relevant Resources Links</title> - <para>Find more on how to configure logging via a log4j property file in <ulink - url="http://supportweb.cs.bham.ac.uk/docs/tutorials/docsystem/build/tutorials/..." - >Log4j documentation</ulink>.</para> - </section> - </section> - <section id="dali_integration"> - <title>Hibernate support for Dali plugins in Eclipse WTP</title> - <para>Starting from 3.0.0 Alpha1 version of <property>JBoss Tools</property> Hibernate plugins - support Eclipse Dali integration what now makes it possible to use a Hibernate as a complete - JPA development platform.</para> - <section id="jpa_project_with_hibernate"> - <title>Creating JPA project with Hibernate support</title> - <para>When starting a new JPA project from <emphasis> - <property>New > Other > JPA > JPA Project</property> - </emphasis> (or simply <emphasis> - <property>New > JPA Project</property> - </emphasis> in <property>JPA Perspective</property>), the first wizard page looks as - follows.</para> - <figure> - <title>Starting JPA Project</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration1.png"/> - </imageobject> - </mediaobject> - </figure> - <para>It's possible here to select a target runtime and change the project configuration, - or you can leave everything as it is.</para> - <para>On the JPA Facet page you should choose Hibernate as a target platform. Also select the - proper database connection, if it is defined, or add a new one by clicking the <emphasis> - <property>Add connection</property> - </emphasis> link.</para> - <para>Hitting <emphasis> - <property>Finish</property> - </emphasis> will generate the project.</para> - <figure> - <title>Targeting at Hibernate Platform</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration2.png"/> - </imageobject> - </mediaobject> - </figure> - <note> - <title>Note:</title> - <para>Please note, if you choose Hibernate as a platform while creating a JPA/Dali project, - a Hibernate Console Configuration for the project is created automatically when the wizard - finishes its work. It allows a full usage of <property>Hibernate Tools</property> features - without additional setup.</para> - </note> - </section> - <section id="generate_ddl_entities_with_hibernate"> - <title>Generating DDL and Entities</title> - <para>By enabling Hibernate platform specific features you can now generate DDL and Entities. - For that find <emphasis> - <property>JPA Tools > Generate Tables from Entities/Generate Entities from - Tables</property> - </emphasis> options in the context menu of your JPA project.</para> - <figure> - <title>Generate DDL/Entities</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration3.png"/> - </imageobject> - </mediaobject> - </figure> - <note> - <title>Note:</title> - <para>Please, remember to put the proper database driver to the classpath of your - project.</para> - </note> - <para>The <property>Generate Entities wizard</property> first will ask you to choose the - directory where all output will be written.</para> - <figure> - <title>Generate Entities Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration4.png"/> - </imageobject> - </mediaobject> - </figure> - <para>To generate entities you can use:</para> - <itemizedlist> - <listitem> - <para>a Hibernate Console Configuration (proposed by default)</para> - <para>Just make sure that the <emphasis> - <property>Use Console Configuration</property> - </emphasis> checkbox is selected and choose a needed configuration from the <emphasis> - <property>Console configurations</property> - </emphasis> list box.</para> - <figure> - <title>Generate Entities Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration5.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - <itemizedlist> - <listitem> - <para>or a DTP connection directly</para> - <para>Just uncheck <emphasis> - <property>Use Console Configuration</property> - </emphasis> and adjust database settings.</para> - </listitem> - </itemizedlist> - <para>All the same you do with Generate Entities Wizard you can do with Generate DDL wizard. - Special feature for Generate DDL wizard is possible automatic execution of Generation DDL in - the database. </para> - <figure> - <title>Generate DDL Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration6.png"/> - </imageobject> - </mediaobject> - </figure> - <para>Thus, you can now have the Hibernate runtime support in Eclipse JPA projects.</para> - </section> - <section id="hibernate_annotations_support"> - <title>Hibernate Annotations Support</title> - <para>Also Hibernate Annotations are supported in <property>Dali Java Persistence - Tools</property>. The next annotations are integrated with <property>JPA - Details</property> view:</para> - <itemizedlist> - <listitem> - <para>Id Generator annotations - <property>@GenericGenerator</property> and <property - >@GeneratedValue</property></para> - <figure> - <title>@GenericGenerator support in Dali</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration7.png"/> - </imageobject> - </mediaobject> - </figure> - <figure> - <title>@GeneratedValue support in Dali</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration8.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Property annotations- <property>@DiscriminatorFormula</property>, <property - >@Generated Annotation</property>, <property>@Index annotation</property></para> - <figure> - <title>@Index support in Dali</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration9.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Mapping Queries annotations - <property>@NamedQuery</property> and <property - >@NamedNativeQuery</property></para> - <figure> - <title>Add New Named Query Dialog with Hibernate Support</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration10.png"/> - </imageobject> - </mediaobject> - </figure> - <figure> - <title>@NamedQuery support in Dali</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration11.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - <listitem> - <para>Association annotations in an <property>embeddable</property> object (<property - >@OneToOne</property>, <property>@ManyToOne</property>, <property - >@OneToMany</property> or <property>@ManyToMany</property>)</para> - <figure> - <title>Hibernate Support for Embeddable Object</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/plugins/dali_integration12.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - </itemizedlist> - <para>More information about Hibernate Annotation you can find in <ulink - url="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html/">Hibernate - Annotations Reference Guide</ulink>. </para> - </section> - <section> - <title>Relevant Resources Links</title> - <para>There is full information about native Dali plugin features on <ulink - url="http://help.eclipse.org/galileo/index.jsp?nav=/8">Eclipse Documentation - page</ulink>.</para> - </section> - </section> + <para>After defining all the required settings click the <guibutton>Next</guibutton> button.</para> + <figure> + <title>Hibernate:add JPA annotations view</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/annotations2.png"/> + </imageobject> + </mediaobject> + </figure> + <para> + The view represents two windows: one with the source code and and the second with refactored one. With the help of the <inlinemediaobject><imageobject><imagedata fileref="images/plugins/butt1.png"/></imageobject></inlinemediaobject>, <inlinemediaobject><imageobject><imagedata fileref="images/plugins/butt2.png"/></imageobject></inlinemediaobject>, <inlinemediaobject><imageobject><imagedata fileref="images/plugins/butt3.png"/></imageobject></inlinemediaobject>, <inlinemediaobject><imageobject><imagedata fileref="images/plugins/butt4.png"/></imageobject></inlinemediaobject> buttons you can quickly navigate between the differences in the code. If you don't agree with some changes you can't undo them but you can remove the class from the list of classes that need refactoring. + </para> + <figure> + <title>List of classes that need refactoring</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/annotations3.png"/> + </imageobject> + </mediaobject> + </figure> + <para>To apply the changes click the <guibutton>Finish</guibutton> button.</para> + </section> + <section id="debug_log"> + <title>Enable debug logging in the plugins</title> + <para> + It is possible to configure the Eclipse plugin to route all logging performed by the plugins and Hibernate code it self to the <guilabel>Error Log</guilabel> view in Eclipse. + </para> + <para> + The <guilabel>Error Log</guilabel> view is very useful tool to use when solving any problems which appear in the Hibernate Tools plugins. You can use it if there are troubles setting up a <guilabel>Hibernate Console Configuration</guilabel>. + </para> + <para> + This is done by editing the <filename>hibernate-log4j.properties</filename> file in the <filename>org.hibernate.eclipse/</filename> directory or JAR. This file includes a default configuration that only logs WARN and above to a set of custom appenders (PluginFileAppender and PluginLogAppender). You can change these settings to be as verbose or silent as you please. See the <ulink url="http://www.hibernate.org/5.html">Hibernate Documentation</ulink> for more information on logging categories and Log4j documentation. + </para> + <section> + <title>Relevant Resources Links</title> + <para> + More information on how to to configure logging via a Log4j property file can be found in the <ulink url="http://supportweb.cs.bham.ac.uk/docs/tutorials/docsystem/build/tutorials/...">Log4j documentation</ulink>. + </para> + </section> + </section> + <section id="dali_integration"> + <title>Hibernate support for Dali plugins in Eclipse WTP</title> + <para> + Starting from version 3.0.0 Alpha1, <productname>JBoss Tools</productname> Hibernate plugins support Eclipse Dali integration, which makes it possible to use a Hibernate as a complete JPA development platform. + </para> + <section id="jpa_project_with_hibernate"> + <title>Creating JPA project with Hibernate support</title> + <para> + When starting a new JPA project by selecting <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>JPA</guimenuitem><guimenuitem>JPA Project</guimenuitem></menuchoice> (or simply <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>JPA Project</guimenuitem></menuchoice> in the <guilabel>JPA Perspective</guilabel>), the first wizard page is shown in the image below. + </para> + <figure> + <title>Starting JPA Project</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration1.png"/> + </imageobject> + </mediaobject> + </figure> + <para>You can select a target runtime and change the project configuration, or you can leave everything as it is.</para> + <para> + On the JPA Facet page you should choose <guilabel>Hibernate</guilabel> as a target platform. Also select the proper database connection, if it is defined, or add a new one by clicking the <guilabel>Add connection</guilabel> link. + </para> + <para>Clicking the <guibutton>Finish</guibutton> button will generate the project.</para> + <figure> + <title>Targeting at Hibernate Platform</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration2.png"/> + </imageobject> + </mediaobject> + </figure> + <note> + <title>Note:</title> + <para> + If you choose Hibernate as a platform while creating a JPA/Dali project, a Hibernate Console Configuration for the project is created automatically when the wizard is finished. It allows all the <guilabel>Hibernate Tools</guilabel> features to be used without any additional setup. + </para> + </note> + </section> + <section id="generate_ddl_entities_with_hibernate"> + <title>Generating DDL and Entities</title> + <para> + By enabling Hibernate platform specific features you can now generate DDL and Entities. To do that select the <menuchoice><guimenuitem>JPA Tools</guimenuitem><guimenuitem>Generate Tables from Entities/Generate Entities from Tables</guimenuitem></menuchoice> options in the context menu of your JPA project. + </para> + <figure> + <title>Generate DDL/Entities</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration3.png"/> + </imageobject> + </mediaobject> + </figure> + <note> + <title>Note:</title> + <para>Remember to put the appropriate database driver to the classpath of your project.</para> + </note> + <para>The <guilabel>Generate Entities wizard</guilabel> will first ask you to choose the directory where all output will be written.</para> + <figure> + <title>Generate Entities Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration4.png"/> + </imageobject> + </mediaobject> + </figure> + <para>To generate entities you can use:</para> + <itemizedlist> + <listitem> + <para>A Hibernate Console Configuration (proposed by default)</para> + <para> + To select this option make sure that the <guilabel>Use Console Configuration</guilabel> checkbox is selected and select a configuration from the <guilabel>Console configurations</guilabel> list box. + </para> + <figure> + <title>Generate Entities Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration5.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <itemizedlist> + <listitem> + <para>Or a DTP connection directly</para> + <para>To select this option uncheck the <guilabel>Use Console Configuration</guilabel> option and adjust the database settings.</para> + </listitem> + </itemizedlist> + <para> + The options you define in the <guilabel>Generate Entities Wizard</guilabel> can also be set with the <guilabel>Generate DDL wizard</guilabel>. The <guilabel>Generate DDL</guilabel> wizard also allows you automatically generate DDL for the database. + </para> + <figure> + <title>Generate DDL Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration6.png"/> + </imageobject> + </mediaobject> + </figure> + <para>In this way you can enable Hibernate runtime support in Eclipse JPA projects.</para> + </section> + <section id="hibernate_annotations_support"> + <title>Hibernate Annotations Support</title> + <para> + Hibernate Annotations are also supported in <guilabel>Dali Java Persistence Tools</guilabel>. The following annotations are integrated with the <guilabel>JPA Details</guilabel> view: + </para> + <itemizedlist> + <listitem> + <para>Id Generator annotations - <code>@GenericGenerator</code> and <code>@GeneratedValue</code> + </para> + <figure> + <title>@GenericGenerator support in Dali</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration7.png"/> + </imageobject> + </mediaobject> + </figure> + <figure> + <title>@GeneratedValue support in Dali</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration8.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Property annotations - <code>@DiscriminatorFormula</code>, <code>@Generated</code>, <code>@Index</code> + </para> + <figure> + <title>@Index support in Dali</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration9.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para>Mapping Queries annotations - <code>@NamedQuery</code> and <code>@NamedNativeQuery</code> + </para> + <figure> + <title>Add New Named Query Dialog with Hibernate Support</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration10.png"/> + </imageobject> + </mediaobject> + </figure> + <figure> + <title>@NamedQuery support in Dali</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration11.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + <listitem> + <para> + Association annotations in an <property>embeddable</property> object (<code>@OneToOne</code>, <code>@ManyToOne</code>, <code>@OneToMany</code> or <code>@ManyToMany</code>) + </para> + <figure> + <title>Hibernate Support for Embeddable Object</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/plugins/dali_integration12.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + </itemizedlist> + <para> + More information about Hibernate Annotations can be found in the <ulink url="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html/">Hibernate Annotations Reference Guide</ulink>. + </para> + </section> + <section> + <title>Relevant Resources Links</title> + <para> + Find more information about native Dali plugin features on the <ulink url="http://help.eclipse.org/galileo/index.jsp?nav=/8">Eclipse Documentation page</ulink>. + </para> + </section> + </section> </chapter> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/reverseengineering.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/reverseengineering.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/reverseengineering.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -2,54 +2,44 @@ <chapter id="reverseengineering"> <title>Controlling reverse engineering</title> - <para>When using the <code><jdbcconfiguration></code>, the ant task will read the - database metadata and thus will perform a reverse engineering of the database schema into a - normal Hibernate Configuration. It is from this object e.g. <code><hbm2java></code>can generate other artifacts such as <emphasis> - <property>.java</property> - </emphasis>, <emphasis> - <property>.hbm.xml</property> - </emphasis> etc.</para> + <para> + When using the <code><jdbcconfiguration></code> tag, the Ant task will read the database metadata and then reverse engineer the database schema into a normal Hibernate Configuration. It is from this object (e.g. <code><hbm2java></code>) that other artifacts, such as <filename>.java</filename> and <filename>.hbm.xml</filename>, can be generated. + </para> - <para>To govern this process <property>Hibernate</property> uses a reverse engineering strategy. A - reverse engineering strategy is mainly called to provide more java like names for tables, column - and foreignkeys into classes, properties and associations. It also used to provide mappings from - SQL types to <property>Hibernate</property> types. The strategy can be customized by a user. The - user can even provide its own custom reverse engineering strategy if the provided strategy is - not enough, or simply just provide a small part of the strategy and delegate the rest to the - default strategy.</para> + <para> + To govern this process <productname>Hibernate</productname> uses a reverse engineering strategy. A reverse engineering strategy is mainly called to provide more Java like names for tables, column and foreign keys into classes, properties and associations. It is also used to provide mappings from SQL types to <productname>Hibernate</productname> types. + </para> + <para> + The strategy can be customized by the user. This can be done by providing a custom reverse engineering strategy should the default strategy does not include the required functionality, or simply define a small component of the strategy and delegate the rest to the default strategy. + </para> - <para>Thus, further in this chapter we will discuss how you can configure the process of a reverse - engineering, what default reverse engineering strategy includes as well as some custom concepts.</para> + <para> + Further in this chapter we will discuss how you can configure the process of reverse engineering, what the default reverse engineering strategy includes, as well as some custom concepts. + </para> <section> <title>Default reverse engineering strategy</title> - <para>The default strategy uses some rules for mapping JDBC artifact names to java artifact - names. It also provide basic typemappings from JDBC types to <property>Hibernate</property> - types. It is the default strategy that uses the packagename attribute to convert a table name - to a fully qualified classname.</para> + <para> + The default strategy uses a collection of rules for mapping JDBC artifact names to Java artifact names. It also provide basic type mappings from JDBC types to <productname>Hibernate</productname> types. It is the default strategy that uses the <code>packagename</code> attribute to convert a table name into a fully qualified class name. + </para> </section> <section id="hibernaterevengxmlfile"> <title>hibernate.reveng.xml file</title> - <para>To have fine control over the process a <emphasis> - <property>hibernate.reveng.xml</property> - </emphasis> file can be provided. In this file you can specify type mappings and table - filtering. This file can be created by hand (it's just basic XML) or you can use the - <ulink url="http://www.hibernate.org/30.html">Hibernate plugins</ulink> which have a - specialized editor.</para> + <para> + A <filename>hibernate.reveng.xml</filename> file can provide a finer degree of control of the reverse engineering process. In this file you can specify type mappings and table filtering. This file can be created by hand (it's just basic XML) or you can use the <ulink url="http://www.hibernate.org/30.html">Hibernate plugins</ulink>, which provides a specialized editor. + </para> <note> <title>Note:</title> - <para>Many databases are case-sensitive with their names and thus if you cannot make some - table match and you are sure it is not excluded by a <code><table-filter></code> then check - if the case matches; most databases stores table names in uppercase.</para> + <para> + Many databases have case-sensitive names, so if a table does not match, and you are sure it is not excluded by a <code><table-filter></code>, check that the case matches. Most databases stores table names in upper case. + </para> </note> - <para>Below you can see an example of a <emphasis> - <property>reveng.xml</property>. </emphasis> Following the example gives you more details - about the format.</para> + <para>Below you can see an example of a <filename>reveng.xml</filename> file.</para> <programlisting role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-reverse-engineering @@ -106,44 +96,33 @@ <section> <title>Schema Selection (<schema-selection>)</title> - <para><code><schema-selection></code> is used to drive which schemas the reverse engineering will try and - process.</para> + <para>The <code><schema-selection></code> tag is used to determine which schemas the reverse engineering will try and process.</para> - <para>By default the reverse engineering will read all schemas and then use <code><table-filter></code> - to decide which tables get reverse engineered and which do not; this makes it - easy to get started but can be inefficient on databases with many schemas.</para> + <para> + By default the reverse engineering will read all schemas and then use the <code><table-filter></code> tag to decide which tables are reverse engineered and which are not. This makes it easy to get started but can be inefficient on databases with many schemas. + </para> - <para>With <code><schema-selection></code> it is thus possible to limit the actual processed schemas and thus significantly - speed-up the reverse engineering. <code><table-filter></code> is still used to then decide which tables will be included/excluded.</para> + <para> + With the <code><schema-selection></code> tag it is thus possible to limit which schemas are processed, which in turn can significantly speed-up the reverse engineering. The <code><table-filter></code> tag is still used to then decide which tables will be included and excluded. + </para> <note> <title>Note:</title> - <para>If no <code><schema-selection></code> is specified, the reverse - engineering works as if all schemas should be processed. This is equal to: - <![CDATA[<schema-selection/>]]>. Which in turn is equal to: - <![CDATA[<schema-selection match-catalog=".*" match-schema=".*" match-table=".*"/>]]></para> + <para> + If no <code><schema-selection></code> tag is specified, the reverse engineering works as if all schemas should be processed. This is equal to: <![CDATA[<schema-selection/>]]>, which in turn is equal to: <![CDATA[<schema-selection match-catalog=".*" match-schema=".*" match-table=".*"/>]]> + </para> </note> <section> <title>Examples</title> - <para>The following will process all tables from <emphasis> - <property>"MY_SCHEMA"</property>. - </emphasis></para> + <para>The following will process all tables from <code>"MY_SCHEMA"</code>.</para> <programlisting role="XML"><![CDATA[<schema-selection match-schema="MY_SCHEMA"/>]]></programlisting> - <para>It is possible to have multiple <literal>schema-selection</literal>'s to support - multi-schema reading or simply to limit the processing to very specific tables. The - following example processes all tables in <emphasis> - <property>"MY_SCHEMA"</property>, - </emphasis> a specific <emphasis> - <property>"CITY"</property> - </emphasis> table plus all tables that starts with <emphasis> - <property>"CODES_"</property> - </emphasis> in <emphasis> - <property>"COMMON_SCHEMA"</property>. - </emphasis></para> + <para> + It is possible to have multiple <code>schema-selection</code>'s to support multi-schema reading, or to limit the processing to very specific tables. The following example processes all tables in <code>"MY_SCHEMA"</code>, a specific <code>"CITY"</code> table plus all tables that start with <code>"CODES_"</code> in <code>"COMMON_SCHEMA"</code>. + </para> <programlisting role="XML"><![CDATA[<schema-selection match-schema="MY_SCHEMA"/> <schema-selection match-schema="COMMON_SCHEMA" match-table="CITY"/> @@ -154,13 +133,9 @@ <section id="type_map"> <title>Type mappings (<type-mapping>)</title> - <para>The <code><type-mapping></code> section specifies how the JDBC types found in the database should be mapped to - Hibernate types. e.g. <emphasis> - <property>java.sql.Types.VARCHAR</property></emphasis> with a length of 1 should be mapped to the - Hibernate type <emphasis> - <property>yes_no</property></emphasis> or <emphasis> - <property>java.sql.Types.NUMERIC</property></emphasis> should generally just be - converted to the Hibernate type <literal>long</literal>.</para> + <para> + The <code><type-mapping></code> section specifies how the JDBC types found in the database should be mapped to Hibernate types. e.g. <code>java.sql.Types.VARCHAR</code> with a length of 1 should be mapped to the Hibernate type <code>yes_no</code>, or <code>java.sql.Types.NUMERIC</code> should generally just be converted to the Hibernate type <code>long</code>. + </para> <programlisting role="XML"><![CDATA[<type-mapping> <sql-type @@ -173,16 +148,14 @@ /> </type-mapping>]]></programlisting> - <para>The number of attributes specified and the sequence of the <literal>sql-type</literal>'s - is important. Meaning that <property>Hibernate</property> will search for the most specific - first, and if no specific match is found it will seek from top to bottom when trying to - resolve a type mapping.</para> + <para> + The number of attributes specified and the sequence of the <code>sql-type</code> tags are important. This is because <productname>Hibernate</productname> will search for the most specific first, and if no specific match is found it will seek from top to bottom when trying to resolve a type mapping. + </para> <section> <title>Example</title> - <para>The following is an example of a type-mapping which shows the flexibility and the - importance of ordering of the type mappings.</para> + <para>The following is an example of a type-mapping which shows the flexibility and importance of the ordering of the type mappings.</para> <programlisting role="XML"><![CDATA[<type-mapping> <sql-type jdbc-type="NUMERIC" precision="15" hibernate-type="big_decimal"/> @@ -195,8 +168,7 @@ <sql-type jdbc-type="VARCHAR" hibernate-type="string"/> </type-mapping>]]></programlisting> - <para>The following table shows how this affects an example table named <emphasis> - <property>CUSTOMER</property>:</emphasis></para> + <para>The following table shows how this affects an example table named <code>CUSTOMER</code>:</para> <table frame="topbot"> <title>sql-type examples</title> @@ -264,9 +236,9 @@ <entry>your.package.TrimStringUserType</entry> - <entry>No type-mapping matches length=30 and not-null=false, but type-mapping - matches the 2 mappings which only specifies VARCHAR. The type-mapping that comes - first is chosen.</entry> + <entry> + No type-mapping matches <code>length=30</code> and <code>not-null=false</code>, but type-mapping matches the 2 mappings which only specifies <code>VARCHAR</code>. The type-mapping that comes first is chosen. + </entry> </row> <row> @@ -282,10 +254,8 @@ <entry>char</entry> - <entry>Even though there is a generic match for VARCHAR, the more specific - type-mapping for VARCHAR with not-null="false" is chosen. The first VARCHAR - sql-type matches in length but has no value for not-null and thus is not - considered.</entry> + <entry> + Even though there is a generic match for <code>VARCHAR</code>, the more specific type-mapping for <code>VARCHAR</code> with <code>not-null="false"</code> is chosen. The first <code>VARCHAR</code> sql-type matches in length but has no value for not-null and thus is not considered.</entry> </row> <row> @@ -301,7 +271,7 @@ <entry>java.lang.Character</entry> - <entry>The most specific VARCHAR with not-null="true" is selected</entry> + <entry>The most specific <code>VARCHAR</code> with <code>not-null="true"</code> is selected</entry> </row> <row> @@ -317,7 +287,7 @@ <entry>big_decimal</entry> - <entry>There is a precise match for NUMERIC with precision 15</entry> + <entry>There is a precise match for <code>NUMERIC</code> with precision 15</entry> </row> <row> @@ -333,7 +303,7 @@ <entry>java.lang.Long</entry> - <entry>type-mapping for NUMERIC with not-null="false"</entry> + <entry>type-mapping for <code>NUMERIC</code> with <code>not-null="false"</code></entry> </row> </tbody> </tgroup> @@ -346,10 +316,9 @@ <section> <title>Table filters (<table-filter>)</title> - <para>The <code><table-filter></code> - let you specify matching rules for performing general filtering/setup for - tables, e.g. let you include or exclude specific tables based on the schema or even a - specific prefix.</para> + <para> + The <code><table-filter></code> tag lets you specify matching rules for performing general filtering and setup of tables, e.g. let you include or exclude specific tables based on the schema or even a specific prefix. + </para> <programlisting role="XML"><![CDATA[<table-filter match-catalog="catalog_matching_rule" @@ -433,10 +402,9 @@ <section id="tab_and_col"> <title>Specific table configuration (<table>)</title> - <para><code><table></code> - allows you to provide explicit configuration on how a table should be reverse - engineered. Amongst other things it allows controlling over the naming of a class for the - table, specifying which identifier generator should be used for the primary key etc.</para> + <para> + The <code><table></code> tag allows you to explicitly define how a table should be reverse engineered. It allows control over the naming of a class for the table, provides a way to specify which identifier generator should be used for the primary key and more. + </para> <programlisting role="XML"><![CDATA[<table catalog="catalog_name" @@ -475,9 +443,10 @@ <row> <entry><para>catalog</para></entry> - <entry><para>Catalog name for a table. It has to be specified if you are - reverse engineering multiple catalogs or if it is not equal to - hiberante.default_catalog.</para></entry> + <entry> + <para>Catalog name for a table. It has to be specified if you are reverse engineering multiple catalogs or if it is not equal to hiberante.default_catalog. + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -485,9 +454,11 @@ <row> <entry><para>schema</para></entry> - <entry><para>Schema name for a table. It has to be specified if you are - reverse engineering multiple schemas or if it is not equal to - hiberante.default_schema.</para></entry> + <entry> + <para> + Schema name for a table. It has to be specified if you are reverse engineering multiple schemas or if it is not equal to hiberante.default_schema. + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -503,8 +474,7 @@ <row> <entry><para>class</para></entry> - <entry><para>The class name for a table. Default name is a camelcase version - of the table name.</para></entry> + <entry><para>The class name for a table. Default name is a CamelCase version of the table name.</para></entry> <entry><para>Optional</para></entry> </row> @@ -517,9 +487,9 @@ <section> <title><primary-key></title> - <para>A <code><primary-key></code> allows you to define a primary-key for tables that don't have it - defined in the database, and probably more importantly it allows you to define which - identifier strategy should be used (even for already existing primary-key's).</para> + <para> + A <code><primary-key></code> tag allows you to define a primary-key for tables that do not have one defined in the database, and more importantly it allows you to define which identifier strategy should be used (even for preexisting primary-key's). + </para> <programlisting role="XML"><![CDATA[<primary-key <generator class="generatorname"> @@ -554,9 +524,11 @@ <row> <entry><para>generator/class</para></entry> - <entry><para>Defines which identifier generator should be used. - The class name is any hibernate short hand name or fully qualified class name for an - identifier strategy.</para></entry> + <entry> + <para> + Defines which identifier generator should be used. The class name is any hibernate short hand name or fully qualified class name for an identifier strategy. + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -564,8 +536,7 @@ <row> <entry><para>generator/param</para></entry> - <entry><para>Allows to specify which parameter with a name and - value should be passed to the identifier generator.</para></entry> + <entry><para>Allows to specify which parameter with a name and value should be passed to the identifier generator.</para></entry> <entry><para>Optional</para></entry> </row> @@ -573,8 +544,11 @@ <row> <entry><para>key-column</para></entry> - <entry><para>Specifies which column(s ) the primary-key consists of. A - key-column is same as column, but does not have the exclude property.</para></entry> + <entry> + <para> + Specifies which column(s ) the primary-key consists of. A key-column is same as column, but does not have the exclude property. + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -589,11 +563,11 @@ <section> <title><column></title> - <para>With a <code><column></code> it is possible to explicitly name the resulting property for a column. It is - also possible to redefine what jdbc and/or Hibernate type a column should be processed as - and finally it is possible to completely exclude a column from processing.</para> + <para> + With a <code><column></code> tag it is possible to explicitly name the resulting property for a column, to redefine what JDBC and/or Hibernate type a column should be processed as, and to completely exclude a column from processing. + </para> - <programlisting role="XML"><![CDATA[<column + <programlisting role="XML"><![CDATA[<column name="column_name" jdbc-type="java.sql.Types type" type="hibernate_type" @@ -635,9 +609,11 @@ <row> <entry><para>jdbc-type</para></entry> - <entry><para>Which jdbc-type this column should be processed as. A - value from java.sql.Types, either numerical (93) or the constant name - (TIMESTAMP).</para></entry> + <entry> + <para> + Which jdbc-type this column should be processed as. A value from <code>java.sql.Types</code>, either numerical (e.g. 93) or the constant name (e.g. <code>TIMESTAMP</code>). + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -654,8 +630,7 @@ <row> <entry><para>property</para></entry> - <entry><para>What property name will be generated for this - column</para></entry> + <entry><para>What property name will be generated for this column</para></entry> <entry><para>Optional</para></entry> </row> @@ -678,12 +653,11 @@ <section> <title><foreign-key></title> - <para>The <code><foreign-key></code> - has two purposes. One for allowing to define foreign-keys in databases that - does not support them or does not have them defined in their schema. Secondly, to allow - defining the name of the resulting properties (many-to-one, one-to-one and one-to-many's).</para> + <para> + The <code><foreign-key></code> tag has two purposes. The first is to define foreign-keys in databases that does not support them or do not have them defined in their schema. The second is to define the name of the resulting properties (many-to-one, one-to-one and one-to-many's). + </para> - <programlisting role="XML"><![CDATA[<foreign-key + <programlisting role="XML"><![CDATA[<foreign-key constraint-name="foreignKeyName" foreign-catalog="catalogName" foreign-schema="schemaName" @@ -730,9 +704,11 @@ <row> <entry><para>constraint-name</para></entry> - <entry><para>Name of the foreign key constraint. Important when - naming many-to-one, one-to-one and set. It is the constraint-name that is used to link the - processed foreign-keys with the resulting property names.</para></entry> + <entry> + <para> + Name of the foreign key constraint. Important when naming many-to-one, one-to-one and set. It is the constraint-name that is used to link the processed foreign-keys with the resulting property names. + </para> + </entry> <entry><para>Required</para></entry> </row> @@ -740,8 +716,7 @@ <row> <entry><para>foreign-catalog</para></entry> - <entry><para>Name of the foreign table's catalog. (Only - relevant if you want to explicitly define a foreign key).</para></entry> + <entry><para>Name of the foreign table's catalog. (Only relevant if you want to explicitly define a foreign key).</para></entry> <entry><para>Optional</para></entry> </row> @@ -749,8 +724,7 @@ <row> <entry><para>foreign-schema</para></entry> - <entry><para>Name of the foreign table's schema. (Only relevant - if you want to explicitly define a foreign key).</para></entry> + <entry><para>Name of the foreign table's schema. (Only relevant if you want to explicitly define a foreign key).</para></entry> <entry><para>Optional</para></entry> </row> @@ -759,8 +733,7 @@ <row> <entry><para>foreign-table</para></entry> - <entry><para>Name of the foreign table. (Only relevant if you - want to explicitly define a foreign key).</para></entry> + <entry><para>Name of the foreign table. (Only relevant if you want to explicitly define a foreign key).</para></entry> <entry><para>Optional</para></entry> </row> @@ -768,9 +741,11 @@ <row> <entry><para>column-ref </para></entry> - <entry><para>Defines that the foreign-key constraint between a - local-column and foreign-column name. (Only relevant if you want to explicitly - define a foreign key).</para></entry> + <entry> + <para> + Defines the foreign-key constraint between a local-column and foreign-column name. (Only relevant if you want to explicitly define a foreign key). + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -778,9 +753,11 @@ <row> <entry><para>many-to-one</para></entry> - <entry><para>Defines that a many-to-one should be created and the - property attribute specifies the name of the resulting property. Exclude can be - used to explicitly define that it should be created or not.</para></entry> + <entry> + <para> + Defines that a many-to-one should be created and the property attribute specifies the name of the resulting property. Exclude can be used to explicitly define that it should be created or not. + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -788,9 +765,11 @@ <row> <entry><para>set</para></entry> - <entry><para>Defines that a set should be created based on this foreign-key - and the property attribute specifies the name of the resulting (set) property. - Exclude can be used to explicitly define that it should be created or not.</para></entry> + <entry> + <para> + Defines that a set should be created based on this foreign-key and the property attribute specifies the name of the resulting (set) property. Exclude can be used to explicitly define that it should be created or not. + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -798,9 +777,11 @@ <row> <entry><para>one-to-one</para></entry> - <entry><para>Defines that a one-to-one should be created and the - property attribute specifies the name of the resulting property. Exclude can be - used to explicitly define that it should be created or not.</para></entry> + <entry> + <para> + Defines that a one-to-one should be created and the property attribute specifies the name of the resulting property. Exclude can be used to explicitly define that it should be created or not. + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -808,9 +789,11 @@ <row> <entry><para>inverse-one-to-one</para></entry> - <entry><para>Defines that an inverse one-to-one should be created based on this foreign-key - and the property attribute specifies the name of the resulting property. - Exclude can be used to explicitly define that it should be created or not.</para></entry> + <entry> + <para> + Defines that an inverse one-to-one should be created based on this foreign-key and the property attribute specifies the name of the resulting property. Exclude can be used to explicitly define that it should be created or not. + </para> + </entry> <entry><para>Optional</para></entry> </row> @@ -826,17 +809,9 @@ <section id="custom-reveng-strategy"> <title>Custom strategy</title> - <para>It is possible to implement a user strategy. Such strategy must implement <emphasis> - <property>org.hibernate.cfg.reveng.ReverseEngineeringStrategy</property>. - </emphasis> It is recommended that one uses the - <property>DelegatingReverseEngineeringStrategy</property> and provide a public constructor - which takes another <property>ReverseEngineeringStrategy </property> as an argument. This will - allow you to only implement the relevant methods and provide a fallback strategy. Example of - custom delegating strategy which converts all column names that ends with <emphasis> - <property>"PK"</property> - </emphasis> into a property named <emphasis> - <property>"id"</property>. - </emphasis></para> + <para> + It is possible to implement a user strategy. Such a strategy must implement <code>org.hibernate.cfg.reveng.ReverseEngineeringStrategy</code>. It is recommended that you use the <code>DelegatingReverseEngineeringStrategy</code> and provide a public constructor which takes another <code>ReverseEngineeringStrategy</code> as an argument. This will allow you to only implement the relevant methods and provide a fall back strategy. An example is shown below of a custom delegating strategy that converts all column names ending with <code>"PK"</code> into a property named <code>"id"</code>. + </para> <programlisting role="JAVA"><![CDATA[public class ExampleStrategy extends DelegatingReverseEngineeringStrategy { @@ -857,21 +832,16 @@ <section> <title>Custom Database Metadata</title> - <para>By default the reverse engineering is performed by reading using the JDBC database - metadata API. This is done via the class <emphasis> - <property>org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect</property> - </emphasis> which is an implementation of <emphasis> - <property>org.hibernate.cfg.reveng.dialect.MetaDataDialect</property>. - </emphasis></para> + <para> + By default the reverse engineering is performed using the JDBC database metadata API. This is done via the class <code>org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect</code>, which is an implementation of <code>org.hibernate.cfg.reveng.dialect.MetaDataDialect</code>. + </para> - <para>The default implementation can be replaced with an alternative implementation by setting - the property <emphasis> - <property>hibernatetool.metadatadialect</property> - </emphasis> to a fully qualified classname for a class that implements - <property>JDBCMetaDataDialect</property>.</para> + <para> + The default implementation can be replaced with an alternative implementation by setting the <code>hibernatetool.metadatadialect</code> property to a fully qualified class name for a class that implements <code>JDBCMetaDataDialect</code>. + </para> - <para>This can be used to provide database specific optimized metadata reading. If you create an - optimized/better metadata reading for your database it will be a very welcome - contribution.</para> + <para> + This can be used to provide database specific optimized metadata reading. If you create an optimized metadata reader for your database it will be a very welcome contribution. + </para> </section> </chapter> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/setup.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/setup.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/en-US/setup.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -1,115 +1,43 @@ <?xml version="1.0" encoding="ISO-8859-1"?> <chapter id="setup"> - <title>Download and install Hibernate Tools</title> - <para><property>Hibernate Tools</property> can be used "standalone" via Ant 1.6.x or - fully integrated into an Eclipse + WTP based IDE, such as <property>JBDS/JBoss Tools</property>, - or a default Eclipse + WTP installation. The following sections describe the install steps in - these environments.</para> - <note> - <title>Note:</title> - <para>The <property>Hibernate Tools 3.3.0</property> (the current release version) requires - Eclipse Galileo 3.5.</para> - </note> - <section> - <title>JBoss Tools</title> - <para><property>JBoss Tools 3.1.0</property> (the latest release) includes <property>Hibernate - Tools 3.3.0</property> and thus nothing is required besides <property>downloading</property> - and <property>installing JBoss Tools</property>. If you need to update to a newer version of - the <property>Hibernate Tools</property> just follow the instructions in the Eclipse IDE - section.</para> - </section> - <section> - <title>Eclipse IDE</title> - <para>To install the <property>Hibernate Tools</property> into any <property>Eclipse - 3.5</property> based IDE you can either use <ulink - url="http://download.jboss.org/jbosstools/updates/stable/">JBoss Tools Update Site</ulink> - or install it manually.</para> - <para>If you want to install the <property>Hibernate Tools</property> distribution manually you - need to:</para> - <itemizedlist> - <listitem> - <para>Download from www.eclipse.org:</para> - <itemizedlist> - <listitem> - <para>birt-report-framework-2_5_0.zip</para> - </listitem> - <listitem> - <para>birt-wtp-integration-sdk-2_3_2.zip</para> - </listitem> - <listitem> - <para>dtp-sdk_1.7.0.zip</para> - </listitem> - <listitem> - <para>eclipse-SDK-3.5-win32.zip</para> - </listitem> - <listitem> - <para>emf-runtime-2.5.0.zip</para> - </listitem> - <listitem> - <para>GEF-SDK-3.5.0.zip</para> - </listitem> - <listitem> - <para>org.eclipse.swtbot.eclipse.test-2.0.0.371-dev-e35.zip</para> - </listitem> - <listitem> - <para>org.eclipse.swtbot.eclipse-2.0.0.340-dev.zip</para> - </listitem> - <listitem> - <para>site-1.6.2.zip</para> - </listitem> - <listitem> - <para>tptp.sdk-TPTP-4.6.0.zip</para> - </listitem> - <listitem> - <para>wtp-sdk-R-3.1-20090616035105.zip</para> - </listitem> - <listitem> - <para>xsd-runtime-2.5.0.zip</para> - </listitem> - </itemizedlist> - </listitem> - <listitem> - <para>Then you should unpack these files into Eclipse install folder.</para> - </listitem> - <listitem> - <para>From <ulink url="https://www.hibernate.org/6.html">hibernate.org-Download Overview</ulink> download <ulink url="http://downloads.sourceforge.net/project/jboss/JBossTools/JBossTools3.1.0...">Hibernate Tools</ulink> - .</para> - - </listitem> - <listitem> - <para>Unpack <property>Hibernate Tools</property> in eclipse/dropins folder</para> - </listitem> - </itemizedlist> - <note> - <title>Note:</title> - <para>If you need more detailed instructions on plugins installation and general usage of eclipse - then check out <ulink url="https://eclipse-tutorial.dev.java.net/" - >https://eclipse-tutorial.dev.java.net/</ulink> and especially <ulink - url="https://eclipse-tutorial.dev.java.net/visual-tutorials/updatemanager.html" - >https://eclipse-tutorial.dev.java.net/visual-tutorials/updatemanager.html</ulink> which - covers using the update manager.</para> - </note> - <section> - <title>Usage of Eclipse WTP</title> - <para>The <property>Hibernate Tools</property> plugins currently use <property>WTP - 3.x</property> which at this time is the latest stable release from the Eclipse Webtools - project.</para> - <para>Because the WTP project not always have had proper versioning of their plugins there - might exist WTP plugins in your existing eclipse directory from other Eclipse based projects - that are from an earlier WTP release but has either the same version number or higher. It is - thus recommended that if you have issues with WTP provided features to try and install the - plugins on a clean install of eclipse to ensure there are no version collisions.</para> - </section> - </section> - <section> - <title>Ant</title> - <para>To use the tools via Ant you need the <emphasis> - <property>hibernate-tools.jar</property> - </emphasis> and associated libraries. The libraries are included in the distribution from the - Hibernate website and the Eclipse updatesite. The libraries are located in the eclipse plugins - directory at <emphasis> - <property>/plugins/org.hibernate.eclipse.x.x.x/lib/tools/</property> - </emphasis>. These libraries are 100% independent from the eclipse platform. How to use these - via ant tasks are described in the <xref linkend="ant"/> chapter.</para> - </section> + <title>Download and install Hibernate Tools</title> + <para> + <productname>Hibernate Tools</productname> can be used "standalone" via Ant 1.6.x or fully integrated into an Eclipse + WTP based IDE, such as the case with <productname>JBDS/JBoss Tools</productname>, or a default Eclipse + WTP installation. The following sections describe the install steps in these environments. + </para> + <note> + <title>Note:</title> + <para>The <productname>Hibernate Tools 3.4.0</productname> (the current release version) requires Eclipse Helios (3.6).</para> + </note> + <section> + <title>JBoss Tools</title> + <para> + <productname>JBoss Tools 3.4.0</productname> (the latest release) includes <productname>Hibernate Tools 3.3.0</productname> and thus no additional steps are required beyond downloading and installing <productname>JBoss Tools</productname>. If you need to update to a newer version of the <productname>Hibernate Tools</productname> just follow the instructions in <xref linkend="eclipse_ide"/>. + </para> + </section> + <section id="eclipse_ide"> + <title>Eclipse IDE</title> + <para> + To install the <productname>Hibernate Tools</productname> into any <productname>Eclipse 3.6</productname> based IDE you can either use the <ulink url="http://download.jboss.org/jbosstools/updates/stable/">JBoss Tools Update Site</ulink>. + </para> + <note> + <title>Note:</title> + <para> + If you need more detailed instructions on plugin installation and general usage of <productname>Eclipse</productname> then check out <ulink url="https://eclipse-tutorial.dev.java.net/">https://eclipse-tutorial.dev.java.net/</ulink> and especially <ulink url="https://eclipse-tutorial.dev.java.net/visual-tutorials/updatemanager.html">https://eclipse-tutorial.dev.java.net/visual-tutorials/updatemanager.html</ulink> which covers the use of the update manager. + </para> + </note> + <section> + <title>Using Eclipse WTP</title> + <para> + The <productname>Hibernate Tools</productname> plugins currently use <property>WTP 3.x</property>, which at this time is the latest stable release from the <productname>Eclipse Webtools</productname> project. + </para> + <para> + Because the <productname>WTP</productname> project has not always used proper versioning with their plugins, <productname>WTP</productname> plugins may be present in your existing <productname>Eclipse</productname> directory from other <productname>Eclipse</productname> based projects that are from an earlier <productname>WTP</productname> release but has either the same version number or higher. It is thus recommended that if you have issues with features provided by <productname>WTP</productname> to install the plugins on a clean install of <productname>Eclipse</productname> to ensure there are no version collisions. + </para> + </section> + </section> + <section> + <title>Ant</title> + <para>To use the tools via <productname>Ant</productname> you need the <filename>hibernate-tools.jar</filename> file and associated libraries. The libraries are included in the distribution from the <productname>Hibernate</productname> website and the <productname>Eclipse</productname> update site. The libraries are located in the <productname>Eclipse</productname> plugins directory at <filename>/plugins/org.hibernate.eclipse.x.x.x/lib/tools/</filename>. These libraries are 100% independent from the <productname>Eclipse</productname> platform. How to use the <productname>Hibernate Tools</productname> via <productname>Ant</productname> tasks is described in <xref linkend="ant"/>. + </para> + </section> </chapter> Modified: branches/jbosstools-3.2.x/hibernatetools/docs/reference/pom.xml =================================================================== --- branches/jbosstools-3.2.x/hibernatetools/docs/reference/pom.xml 2011-07-18 01:51:18 UTC (rev 32974) +++ branches/jbosstools-3.2.x/hibernatetools/docs/reference/pom.xml 2011-07-18 01:59:12 UTC (rev 32975) @@ -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>Hibernatetools_Reference_Guide</docname> - <bookname>Hibernatetools Reference Guide</bookname> - </properties> - - <profiles> + <properties> + <translation>en-US</translation> + <docname>Hibernatetools_Reference_Guide</docname> + <bookname>Hibernatetools Reference Guide</bookname> + </properties> + <profiles> +  - <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>  - <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>  - <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>  - <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>  - <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>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>

14 years, 9 months

1
0
0 / 0

JBoss Tools SVN: r32974 - branches/jbosstools-3.2.x/hibernatetools/docs.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2011-07-17 21:51:18 -0400 (Sun, 17 Jul 2011) New Revision: 32974 Removed: branches/jbosstools-3.2.x/hibernatetools/docs/task-reference/ Log: removed

14 years, 9 months

1
0
0 / 0

JBoss Tools SVN: r32973 - in branches/jbosstools-3.2.x/documentation/guides/Update_Guide: en-US and 1 other directories.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2011-07-17 21:50:34 -0400 (Sun, 17 Jul 2011) New Revision: 32973 Added: branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/images/icon.svg Modified: branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Author_Group.xml branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Book_Info.xml branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Feedback.xml branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Preface.xml branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Update_Guide.ent branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Update_Guide.xml branches/jbosstools-3.2.x/documentation/guides/Update_Guide/pom.xml Log: updated for GA Modified: branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Author_Group.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Author_Group.xml 2011-07-18 01:48:50 UTC (rev 32972) +++ branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Author_Group.xml 2011-07-18 01:50:34 UTC (rev 32973) @@ -3,8 +3,11 @@ ]> <authorgroup> <author> - <firstname>Matthew</firstname> - <surname>Casperson</surname> - <email>mcaspers(a)redhat.com</email> + <firstname>Ben</firstname> + <surname>Clare</surname> </author> + <author> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + </author> </authorgroup> Modified: branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Book_Info.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Book_Info.xml 2011-07-18 01:48:50 UTC (rev 32972) +++ branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Book_Info.xml 2011-07-18 01:50:34 UTC (rev 32973) @@ -3,14 +3,14 @@ ]> <bookinfo> <title>Update Guide</title> - <subtitle>Updating from 3.0 to 3.0.x</subtitle> + <subtitle>Updating from 4.0 to 4.1.x</subtitle> <productname>JBoss Developer Studio</productname> - <productnumber>4.0</productnumber> - <edition>4.0.0</edition> + <productnumber>4.1</productnumber> + <edition>4.1.0</edition> <pubsnumber>5</pubsnumber> <abstract> <para> - The Update Guide explains how to upgrade from JBoss Developer Studio 3.0 to JBoss Developer Studio 3.0.x + The Update Guide explains how to upgrade from JBoss Developer Studio 4.0 to JBoss Developer Studio 4.1.x </para> </abstract> <corpauthor> Modified: branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Feedback.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Feedback.xml 2011-07-18 01:48:50 UTC (rev 32972) +++ branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Feedback.xml 2011-07-18 01:50:34 UTC (rev 32973) @@ -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=12310500&issu...">https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...</ulink> - </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> +  <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/documentation/guides/Update_Guide/en-US/Preface.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Preface.xml 2011-07-18 01:48:50 UTC (rev 32972) +++ branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Preface.xml 2011-07-18 01:50:34 UTC (rev 32973) @@ -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.html">Red Hat Documentation</ulink> website under the <guilabel>JBoss Developer Studio</guilabel> section. </para> -  </preface> Modified: branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Update_Guide.ent =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Update_Guide.ent 2011-07-18 01:48:50 UTC (rev 32972) +++ branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Update_Guide.ent 2011-07-18 01:50:34 UTC (rev 32973) @@ -2,3 +2,6 @@ <!ENTITY BOOKID "Update_Guide"> <!ENTITY YEAR "2011"> <!ENTITY HOLDER "Red Hat"> +<!ENTITY BZPRODUCT "JBoss Developer Studio"> +<!ENTITY BZCOMPONENT "Beginners Guide"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Develope...'>http://bugzilla.redhat.com/</ulink>"> Modified: branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Update_Guide.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Update_Guide.xml 2011-07-18 01:48:50 UTC (rev 32972) +++ branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/Update_Guide.xml 2011-07-18 01:50:34 UTC (rev 32973) @@ -5,5 +5,6 @@ <xi:include href="Book_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="Preface.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="Update.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> Added: branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/images/icon.svg =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/images/icon.svg (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/Update_Guide/en-US/images/icon.svg 2011-07-18 01:50:34 UTC (rev 32973) @@ -0,0 +1,3936 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> + +<svg + xmlns:ns="http://ns.adobe.com/AdobeSVGViewerExtensions/3/" + xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/" + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + version="1.0" + width="32" + height="32" + id="svg3017" + sodipodi:version="0.32" + inkscape:version="0.44+devel" + sodipodi:docname="book.svg" + sodipodi:docbase="/home/andy/Desktop"> + <metadata + id="metadata489"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + </cc:Work> + </rdf:RDF> + </metadata> + <sodipodi:namedview + inkscape:window-height="480" + inkscape:window-width="858" + inkscape:pageshadow="0" + inkscape:pageopacity="0.0" + guidetolerance="10.0" + gridtolerance="10.0" + objecttolerance="10.0" + borderopacity="1.0" + bordercolor="#666666" + pagecolor="#ffffff" + id="base" + inkscape:zoom="1" + inkscape:cx="16" + inkscape:cy="15.944056" + inkscape:window-x="0" + inkscape:window-y="33" + inkscape:current-layer="svg3017" /> + <defs + id="defs3019"> + <linearGradient + id="linearGradient2381"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop2383" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="stop2385" /> + </linearGradient> + <linearGradient + x1="415.73831" + y1="11.854" + x2="418.13361" + y2="18.8104" + id="XMLID_1758_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)"> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="0" + id="stop3903" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop3905" /> + <a:midPointStop + style="stop-color:#CCCCCC" + offset="0" /> + <a:midPointStop + style="stop-color:#CCCCCC" + offset="0.5" /> + <a:midPointStop + style="stop-color:#F2F2F2" + offset="1" /> + </linearGradient> + <linearGradient + x1="500.70749" + y1="-13.2441" + x2="513.46442" + y2="-2.1547" + id="XMLID_1757_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop3890" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop3892" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <clipPath + id="XMLID_1755_"> + <use + id="use3874" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_343_" /> + </clipPath> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop3877" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop3879" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop3881" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop3883" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="471.0806" + y1="201.07761" + x2="481.91711" + y2="210.4977" + id="XMLID_1754_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#6498c1;stop-opacity:1" + offset="0.005618" + id="stop3863" /> + <stop + style="stop-color:#79a9cc;stop-opacity:1" + offset="0.2332" + id="stop3865" /> + <stop + style="stop-color:#a4cde2;stop-opacity:1" + offset="0.74049997" + id="stop3867" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="1" + id="stop3869" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="5.618000e-003" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="0.4438" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="1" /> + </linearGradient> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="XMLID_1753_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop3851" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop3853" /> + <a:midPointStop + style="stop-color:#B2B2B2" + offset="0" /> + <a:midPointStop + style="stop-color:#B2B2B2" + offset="0.5" /> + <a:midPointStop + style="stop-color:#F2F2F2" + offset="1" /> + </linearGradient> + <clipPath + id="XMLID_1751_"> + <use + id="use3837" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_338_" /> + </clipPath> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop3840" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop3842" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop3844" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop3846" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="468.2915" + y1="204.7612" + x2="479.39871" + y2="214.4166" + id="XMLID_1750_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop3830" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop3832" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop3818" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop3820" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <linearGradient + x1="501.0903" + y1="-19.2544" + x2="531.85413" + y2="0.72390002" + id="XMLID_1748_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop3803" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop3805" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop3807" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop3809" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="XMLID_2275_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop9947" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop9949" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop9951" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop9953" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <clipPath + id="XMLID_2273_"> + <use + id="use9933" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_960_" /> + </clipPath> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="XMLID_2274_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop9936" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop9938" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop9940" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop9942" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <linearGradient + x1="478.21341" + y1="-131.9297" + x2="469.85818" + y2="-140.28481" + id="XMLID_2272_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop9917" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop9919" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop9921" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop9923" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <marker + refX="0" + refY="0" + orient="auto" + style="overflow:visible" + id="TriangleInM"> + <path + d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z " + transform="scale(-0.4,-0.4)" + style="fill:#5c5c4f" + id="path3197" /> + </marker> + <linearGradient + x1="200.7363" + y1="100.4028" + x2="211.99519" + y2="89.143997" + id="XMLID_3298_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#bfbfbf;stop-opacity:1" + offset="0" + id="stop20103" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop20105" /> + <a:midPointStop + offset="0" + style="stop-color:#BFBFBF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#BFBFBF" /> + <a:midPointStop + offset="1" + style="stop-color:#F2F2F2" /> + </linearGradient> + <linearGradient + x1="200.7363" + y1="100.4028" + x2="211.99519" + y2="89.143997" + id="linearGradient36592" + xlink:href="#XMLID_3298_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="181.2925" + y1="110.8481" + x2="192.6369" + y2="99.5037" + id="XMLID_3297_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="stop20096" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop20098" /> + <a:midPointStop + offset="0" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="181.2925" + y1="110.8481" + x2="192.6369" + y2="99.5037" + id="linearGradient36595" + xlink:href="#XMLID_3297_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="211.77589" + y1="105.7749" + x2="212.6619" + y2="108.2092" + id="XMLID_3296_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#0f6124;stop-opacity:1" + offset="0" + id="stop20087" /> + <stop + style="stop-color:#219630;stop-opacity:1" + offset="1" + id="stop20089" /> + <a:midPointStop + offset="0" + style="stop-color:#0F6124" /> + <a:midPointStop + offset="0.5" + style="stop-color:#0F6124" /> + <a:midPointStop + offset="1" + style="stop-color:#219630" /> + </linearGradient> + <linearGradient + x1="211.77589" + y1="105.7749" + x2="212.6619" + y2="108.2092" + id="linearGradient36677" + xlink:href="#XMLID_3296_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="208.9834" + y1="116.8296" + x2="200.0811" + y2="96.834602" + id="XMLID_3295_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop20076" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.5" + id="stop20078" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop20080" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="208.9834" + y1="116.8296" + x2="200.0811" + y2="96.834602" + id="linearGradient36604" + xlink:href="#XMLID_3295_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="195.5264" + y1="97.911102" + x2="213.5213" + y2="115.9061" + id="XMLID_3294_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="0" + id="stop20069" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop20071" /> + <a:midPointStop + offset="0" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="0.5" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="195.5264" + y1="97.911102" + x2="213.5213" + y2="115.9061" + id="linearGradient36607" + xlink:href="#XMLID_3294_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="186.1938" + y1="109.1343" + x2="206.6881" + y2="88.639999" + id="XMLID_3293_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop20056" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.16850001" + id="stop20058" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.23029999" + id="stop20060" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.2809" + id="stop20062" /> + <stop + style="stop-color:#c2c2c2;stop-opacity:1" + offset="0.5" + id="stop20064" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.1685" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.2303" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.2809" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#C2C2C2" /> + </linearGradient> + <linearGradient + x1="186.1938" + y1="109.1343" + x2="206.6881" + y2="88.639999" + id="linearGradient36610" + xlink:href="#XMLID_3293_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="184.8569" + y1="112.2676" + x2="211.94099" + y2="89.541397" + id="XMLID_3292_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop20043" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.16850001" + id="stop20045" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.23029999" + id="stop20047" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.2809" + id="stop20049" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop20051" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.1685" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.2303" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.2809" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="184.8569" + y1="112.2676" + x2="211.94099" + y2="89.541397" + id="linearGradient36613" + xlink:href="#XMLID_3292_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <marker + refX="0" + refY="0" + orient="auto" + style="overflow:visible" + id="TriangleOutM"> + <path + d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z " + transform="scale(0.4,0.4)" + style="fill:#5c5c4f;fill-rule:evenodd;stroke-width:1pt;marker-start:none" + id="path3238" /> + </marker> + <linearGradient + x1="165.3" + y1="99.5" + x2="165.3" + y2="115.9" + id="XMLID_3457_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#999;stop-opacity:1" + offset="0" + id="stop8309" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0.30000001" + id="stop8311" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="1" + id="stop8313" /> + <a:midPointstop + offset="0" + style="stop-color:#999999" /> + <a:midPointstop + offset="0.5" + style="stop-color:#999999" /> + <a:midPointstop + offset="0.3" + style="stop-color:#B2B2B2" /> + <a:midPointstop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointstop + offset="1" + style="stop-color:#B2B2B2" /> + </linearGradient> + <linearGradient + x1="165.3" + y1="99.5" + x2="165.3" + y2="115.9" + id="lg1997" + xlink:href="#XMLID_3457_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="175" + y1="99.800003" + x2="175" + y2="112.5" + id="XMLID_3456_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="0" + id="stop8300" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="0.60000002" + id="stop8302" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="1" + id="stop8304" /> + <a:midPointstop + offset="0" + style="stop-color:#737373" /> + <a:midPointstop + offset="0.5" + style="stop-color:#737373" /> + <a:midPointstop + offset="0.6" + style="stop-color:#191919" /> + <a:midPointstop + offset="0.5" + style="stop-color:#191919" /> + <a:midPointstop + offset="1" + style="stop-color:#191919" /> + </linearGradient> + <linearGradient + x1="175" + y1="99.800003" + x2="175" + y2="112.5" + id="lg2000" + xlink:href="#XMLID_3456_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="168.8" + y1="107.1" + x2="164.5" + y2="110" + id="XMLID_3455_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#666;stop-opacity:1" + offset="0" + id="stop8291" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="0.69999999" + id="stop8293" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="1" + id="stop8295" /> + <a:midPointstop + offset="0" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.5" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.7" + style="stop-color:#191919" /> + <a:midPointstop + offset="0.5" + style="stop-color:#191919" /> + <a:midPointstop + offset="1" + style="stop-color:#191919" /> + </linearGradient> + <linearGradient + x1="168.8" + y1="107.1" + x2="164.5" + y2="110" + id="lg2003" + xlink:href="#XMLID_3455_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + id="lg63694"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop63696" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="stop63698" /> + </linearGradient> + <linearGradient + x1="458" + y1="483" + x2="465.20001" + y2="271.39999" + id="lg2006" + xlink:href="#lg63694" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(6.3e-2,0,0,6.3e-2,-1.3,-9.8)" /> + <linearGradient + x1="176.3" + y1="110.1" + x2="158.7" + y2="105" + id="XMLID_3453_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#666;stop-opacity:1" + offset="0" + id="stop8271" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="0.2" + id="stop8273" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop8275" /> + <a:midPointstop + offset="0" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.5" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.2" + style="stop-color:#737373" /> + <a:midPointstop + offset="0.5" + style="stop-color:#737373" /> + <a:midPointstop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="176.3" + y1="110.1" + x2="158.7" + y2="105" + id="lg2009" + xlink:href="#XMLID_3453_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="173.60001" + y1="118.9" + x2="172.8" + y2="128.2" + id="XMLID_3449_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8232" /> + <stop + style="stop-color:#fff95e;stop-opacity:1" + offset="0.60000002" + id="stop8234" /> + <stop + style="stop-color:#ecd600;stop-opacity:1" + offset="1" + id="stop8236" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.6" + style="stop-color:#FFF95E" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFF95E" /> + <a:midPointstop + offset="1" + style="stop-color:#ECD600" /> + </linearGradient> + <linearGradient + x1="173.60001" + y1="118.9" + x2="172.8" + y2="128.2" + id="lg2016" + xlink:href="#XMLID_3449_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <radialGradient + cx="284.60001" + cy="172.60001" + r="6.5" + fx="284.60001" + fy="172.60001" + id="XMLID_3448_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8219" /> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0.30000001" + id="stop8221" /> + <stop + style="stop-color:#c96b00;stop-opacity:1" + offset="0.89999998" + id="stop8223" /> + <stop + style="stop-color:#9a5500;stop-opacity:1" + offset="1" + id="stop8225" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.3" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.9" + style="stop-color:#C96B00" /> + <a:midPointstop + offset="0.5" + style="stop-color:#C96B00" /> + <a:midPointstop + offset="1" + style="stop-color:#9A5500" /> + </radialGradient> + <radialGradient + cx="284.60001" + cy="172.60001" + r="6.5" + fx="284.60001" + fy="172.60001" + id="rg2020" + xlink:href="#XMLID_3448_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.513992,0,0,2.347576,-689.1621,-378.5717)" /> + <linearGradient + x1="158.10001" + y1="123" + x2="164.2" + y2="126.6" + id="XMLID_3447_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecd600;stop-opacity:1" + offset="0" + id="stop8204" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.30000001" + id="stop8206" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop8208" /> + <a:midPointstop + offset="0" + style="stop-color:#ECD600" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECD600" /> + <a:midPointstop + offset="0.3" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="158.10001" + y1="123" + x2="164.2" + y2="126.6" + id="lg2026" + xlink:href="#XMLID_3447_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <radialGradient + cx="280.89999" + cy="163.7" + r="10.1" + fx="280.89999" + fy="163.7" + id="XMLID_3446_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop8197" /> + <stop + style="stop-color:#fff95e;stop-opacity:1" + offset="1" + id="stop8199" /> + <a:midPointstop + offset="0" + style="stop-color:#FFFFFF" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointstop + offset="1" + style="stop-color:#FFF95E" /> + </radialGradient> + <radialGradient + cx="280.89999" + cy="163.7" + r="10.1" + fx="280.89999" + fy="163.7" + id="rg2029" + xlink:href="#XMLID_3446_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.7,0,0,1.7,-457.5,-266.8)" /> + <linearGradient + x1="156.5" + y1="122.7" + x2="180.10001" + y2="122.7" + id="XMLID_3445_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8184" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.2" + id="stop8186" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.30000001" + id="stop8188" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.40000001" + id="stop8190" /> + <stop + style="stop-color:#d68100;stop-opacity:1" + offset="1" + id="stop8192" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.2" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.3" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.4" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="1" + style="stop-color:#D68100" /> + </linearGradient> + <linearGradient + x1="156.5" + y1="122.7" + x2="180.10001" + y2="122.7" + id="lg2032" + xlink:href="#XMLID_3445_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="156.39999" + y1="115.4" + x2="180.10001" + y2="115.4" + id="XMLID_3444_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8171" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.2" + id="stop8173" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.30000001" + id="stop8175" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.40000001" + id="stop8177" /> + <stop + style="stop-color:#d68100;stop-opacity:1" + offset="1" + id="stop8179" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.2" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.3" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.4" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="1" + style="stop-color:#D68100" /> + </linearGradient> + <linearGradient + x1="156.39999" + y1="115.4" + x2="180.10001" + y2="115.4" + id="lg2035" + xlink:href="#XMLID_3444_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="379.70001" + y1="167.89999" + x2="383.89999" + y2="172.89999" + id="lg4286_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s16159" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.1" + id="s16161" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="1" + id="s16163" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.1" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#737373" + offset="1" /> + </linearGradient> + <linearGradient + x1="379.60001" + y1="167.8" + x2="383.79999" + y2="172" + id="lg6416" + xlink:href="#lg4286_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.622156,0.623859,-0.623859,2.62182,-882.9706,-673.7921)" /> + <linearGradient + x1="384.20001" + y1="169.8" + x2="384.79999" + y2="170.39999" + id="lg4285_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="0" + id="s16152" /> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="1" + id="s16154" /> + <ns:midPointStop + style="stop-color:#737373" + offset="0" /> + <ns:midPointStop + style="stop-color:#737373" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#D9D9D9" + offset="1" /> + </linearGradient> + <linearGradient + x1="384.20001" + y1="169.8" + x2="384.79999" + y2="170.39999" + id="lg6453" + xlink:href="#lg4285_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" /> + <linearGradient + x1="380.5" + y1="172.60001" + x2="382.79999" + y2="173.7" + id="lg4284_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> + <stop + style="stop-color:gray;stop-opacity:1" + offset="0" + id="s16145" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="1" + id="s16147" /> + <ns:midPointStop + style="stop-color:#808080" + offset="0" /> + <ns:midPointStop + style="stop-color:#808080" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#E5E5E5" + offset="1" /> + </linearGradient> + <linearGradient + x1="380.5" + y1="172.60001" + x2="382.79999" + y2="173.7" + id="lg6456" + xlink:href="#lg4284_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" /> + <radialGradient + cx="347.29999" + cy="244.5" + r="5.1999998" + fx="347.29999" + fy="244.5" + id="lg4282_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> + <stop + style="stop-color:#333;stop-opacity:1" + offset="0" + id="s16135" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="s16137" /> + <ns:midPointStop + style="stop-color:#333333" + offset="0" /> + <ns:midPointStop + style="stop-color:#333333" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#999999" + offset="1" /> + </radialGradient> + <linearGradient + x1="310.39999" + y1="397.70001" + x2="310.89999" + y2="399.5" + id="lg4280_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="0" + id="s16111" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.60000002" + id="s16113" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="1" + id="s16115" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.6" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="1" /> + </linearGradient> + <linearGradient + x1="310.39999" + y1="397.70001" + x2="310.89999" + y2="399.5" + id="lg6467" + xlink:href="#lg4280_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> + <linearGradient + x1="310.89999" + y1="395.79999" + x2="313.29999" + y2="403.10001" + id="lg4279_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0" + id="s16100" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.40000001" + id="s16102" /> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="0.89999998" + id="s16104" /> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="1" + id="s16106" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.4" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0.9" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="310.89999" + y1="395.79999" + x2="313.29999" + y2="403.10001" + id="lg6465" + xlink:href="#lg4279_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> + <linearGradient + x1="307.79999" + y1="395.20001" + x2="313.79999" + y2="413.60001" + id="lg4278_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0" + id="s16091" /> + <stop + style="stop-color:#fcd72f;stop-opacity:1" + offset="0.40000001" + id="s16093" /> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="1" + id="s16095" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FCD72F" + offset="0.4" /> + <ns:midPointStop + style="stop-color:#FCD72F" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="306.5" + y1="393" + x2="309" + y2="404" + id="lg6400" + xlink:href="#lg4278_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> + <linearGradient + x1="352.10001" + y1="253.60001" + x2="348.5" + y2="237.8" + id="lg4276_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> + <stop + style="stop-color:#ffff87;stop-opacity:1" + offset="0" + id="s16077" /> + <stop + style="stop-color:#ffad00;stop-opacity:1" + offset="1" + id="s16079" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFAD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="335.60001" + y1="354.79999" + x2="337.89999" + y2="354.79999" + id="lg4275_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="s16057" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.80000001" + id="s16059" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="s16061" /> + <ns:midPointStop + style="stop-color:#D9D9D9" + offset="0" /> + <ns:midPointStop + style="stop-color:#D9D9D9" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.8" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="1" /> + </linearGradient> + <linearGradient + x1="335.60001" + y1="354.79999" + x2="337.89999" + y2="354.79999" + id="lg6463" + xlink:href="#lg4275_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> + <linearGradient + x1="337.39999" + y1="353.10001" + x2="339.39999" + y2="357.10001" + id="lg4274_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s16048" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.1" + id="s16050" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s16052" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.1" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="337.39999" + y1="353.10001" + x2="339.39999" + y2="357.10001" + id="lg6461" + xlink:href="#lg4274_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> + <linearGradient + x1="334.39999" + y1="355.5" + x2="335.5" + y2="356.79999" + id="lg4273_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s16041" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s16043" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="5.6e-003" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="334.39999" + y1="355.5" + x2="335.5" + y2="356.79999" + id="lg6381" + xlink:href="#lg4273_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> + <linearGradient + x1="348.39999" + y1="247.39999" + x2="354.10001" + y2="242" + id="lg4271_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0" + id="s16025" /> + <stop + style="stop-color:#9e9e9e;stop-opacity:1" + offset="0.40000001" + id="s16027" /> + <stop + style="stop-color:black;stop-opacity:1" + offset="1" + id="s16029" /> + <ns:midPointStop + style="stop-color:#F2F2F2" + offset="0" /> + <ns:midPointStop + style="stop-color:#F2F2F2" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#000000" + offset="1" /> + </linearGradient> + <linearGradient + x1="351.29999" + y1="257.29999" + x2="346.29999" + y2="235.5" + id="lg4270_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ffff87;stop-opacity:1" + offset="0" + id="s16007" /> + <stop + style="stop-color:#ffad00;stop-opacity:1" + offset="1" + id="s16009" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFAD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="351.29999" + y1="257.29999" + x2="346.29999" + y2="235.5" + id="lg6459" + xlink:href="#lg4270_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)" /> + <linearGradient + x1="43.799999" + y1="32.5" + x2="63.299999" + y2="66.400002" + id="XMLID_2708_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop75318" /> + <stop + style="stop-color:#fffcea;stop-opacity:1" + offset="1" + id="stop75320" /> + <a:midPointStop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointStop + style="stop-color:#FFFCEA" + offset="1" /> + </linearGradient> + <linearGradient + x1="43.799999" + y1="32.5" + x2="63.299999" + y2="66.400002" + id="lg1907" + xlink:href="#XMLID_2708_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)" /> + <linearGradient + x1="52.5" + y1="40.400002" + x2="58.200001" + y2="64" + id="XMLID_2707_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ffdea0;stop-opacity:1" + offset="0" + id="stop75305" /> + <stop + style="stop-color:#ffd89e;stop-opacity:1" + offset="0.30000001" + id="stop75307" /> + <stop + style="stop-color:#ffd79e;stop-opacity:1" + offset="0.30000001" + id="stop75309" /> + <stop + style="stop-color:#dbaf6d;stop-opacity:1" + offset="0.69999999" + id="stop75311" /> + <stop + style="stop-color:#6f4c24;stop-opacity:1" + offset="1" + id="stop75313" /> + <a:midPointStop + style="stop-color:#FFDEA0" + offset="0" /> + <a:midPointStop + style="stop-color:#FFDEA0" + offset="0.6" /> + <a:midPointStop + style="stop-color:#FFD79E" + offset="0.3" /> + <a:midPointStop + style="stop-color:#FFD79E" + offset="0.5" /> + <a:midPointStop + style="stop-color:#DBAF6D" + offset="0.7" /> + <a:midPointStop + style="stop-color:#DBAF6D" + offset="0.5" /> + <a:midPointStop + style="stop-color:#6F4C24" + offset="1" /> + </linearGradient> + <linearGradient + x1="52.5" + y1="40.400002" + x2="58.200001" + y2="64" + id="lg1910" + xlink:href="#XMLID_2707_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)" /> + <linearGradient + x1="58" + y1="73.199997" + x2="44.5" + y2="19" + id="XMLID_2704_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)"> + <stop + style="stop-color:#d4a96c;stop-opacity:1" + offset="0.5" + id="stop75284" /> + <stop + style="stop-color:#dcb273;stop-opacity:1" + offset="0.60000002" + id="stop75286" /> + <stop + style="stop-color:#f0ca87;stop-opacity:1" + offset="0.80000001" + id="stop75288" /> + <stop + style="stop-color:#ffdc96;stop-opacity:1" + offset="0.69999999" + id="stop75290" /> + <stop + style="stop-color:#c18a42;stop-opacity:1" + offset="1" + id="stop75292" /> + <a:midPointStop + style="stop-color:#D4A96C" + offset="0.5" /> + <a:midPointStop + style="stop-color:#D4A96C" + offset="0.6" /> + <a:midPointStop + style="stop-color:#FFDC96" + offset="0.7" /> + <a:midPointStop + style="stop-color:#FFDC96" + offset="0.5" /> + <a:midPointStop + style="stop-color:#C18A42" + offset="1" /> + </linearGradient> + <linearGradient + x1="53.700001" + y1="32" + x2="53.700001" + y2="64.599998" + id="XMLID_2703_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e5c9b0;stop-opacity:1" + offset="0" + id="stop75268" /> + <stop + style="stop-color:#e5c9b0;stop-opacity:1" + offset="0.40000001" + id="stop75270" /> + <stop + style="stop-color:#c0aa94;stop-opacity:1" + offset="1" + id="stop75272" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0.5" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0.4" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0.5" /> + <a:midPointStop + style="stop-color:#C0AA94" + offset="1" /> + </linearGradient> + <linearGradient + x1="53.700001" + y1="32" + x2="53.700001" + y2="64.599998" + id="lg1916" + xlink:href="#XMLID_2703_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)" /> + <linearGradient + x1="224.31" + y1="19.450001" + x2="214.33" + y2="11.46" + id="XMLID_419_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#404040;stop-opacity:1" + offset="0" + id="s1903" /> + <stop + style="stop-color:#6d6d6d;stop-opacity:1" + offset="0.33000001" + id="s1905" /> + <stop + style="stop-color:#e9e9e9;stop-opacity:1" + offset="1" + id="s1907" /> + <a:midPointStop + offset="0" + style="stop-color:#404040" /> + <a:midPointStop + offset="0.5" + style="stop-color:#404040" /> + <a:midPointStop + offset="0.33" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="0.5" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="1" + style="stop-color:#E9E9E9" /> + </linearGradient> + <linearGradient + x1="221.84" + y1="32.779999" + x2="212.2" + y2="20.27" + id="lg1988" + xlink:href="#XMLID_419_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> + <linearGradient + x1="228.35001" + y1="33.279999" + x2="215.42999" + y2="33.279999" + id="lg1900" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s1902" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="s1906" /> + <a:midPointStop + style="stop-color:#575757" + offset="0" /> + <a:midPointStop + style="stop-color:#575757" + offset="0.5" /> + <a:midPointStop + style="stop-color:#6D6D6D" + offset="0.33" /> + <a:midPointStop + style="stop-color:#6D6D6D" + offset="0.5" /> + <a:midPointStop + style="stop-color:#D3D3D3" + offset="1" /> + </linearGradient> + <linearGradient + x1="234.81" + y1="33.279999" + x2="228.27" + y2="33.279999" + id="lg1908" + xlink:href="#lg1900" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> + <linearGradient + x1="228.35001" + y1="33.279999" + x2="215.42999" + y2="33.279999" + id="XMLID_416_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#575757;stop-opacity:1" + offset="0" + id="s1874" /> + <stop + style="stop-color:#6d6d6d;stop-opacity:1" + offset="0.33000001" + id="s1876" /> + <stop + style="stop-color:#d3d3d3;stop-opacity:1" + offset="1" + id="s1878" /> + <a:midPointStop + offset="0" + style="stop-color:#575757" /> + <a:midPointStop + offset="0.5" + style="stop-color:#575757" /> + <a:midPointStop + offset="0.33" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="0.5" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="1" + style="stop-color:#D3D3D3" /> + </linearGradient> + <linearGradient + x1="228.35001" + y1="33.279999" + x2="215.42999" + y2="33.279999" + id="lg1991" + xlink:href="#XMLID_416_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> + <radialGradient + cx="603.19" + cy="230.77" + r="1.67" + fx="603.19" + fy="230.77" + id="x5010_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.1,0,0,1.1,-54.33,-75.4)"> + <stop + style="stop-color:#c9ffc9;stop-opacity:1" + offset="0" + id="stop29201" /> + <stop + style="stop-color:#23a11f;stop-opacity:1" + offset="1" + id="stop29203" /> + <a:midPointStop + offset="0" + style="stop-color:#C9FFC9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#C9FFC9" /> + <a:midPointStop + offset="1" + style="stop-color:#23A11F" /> + </radialGradient> + <radialGradient + cx="603.19" + cy="230.77" + r="1.67" + fx="603.19" + fy="230.77" + id="radialGradient5711" + xlink:href="#x5010_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.23,0,0,1.23,-709.93,-245.02)" /> + <linearGradient + x1="592.31" + y1="162.60001" + x2="609.32001" + y2="145.59" + id="lg5722" + xlink:href="#x5003_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="601.48999" + y1="170.16" + x2="613.84003" + y2="170.16" + id="x5002_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop29134" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.2" + id="stop29136" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="stop29138" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.20" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="1" + style="stop-color:#999999" /> + </linearGradient> + <linearGradient + x1="601.48999" + y1="170.16" + x2="613.84003" + y2="170.16" + id="lg5725" + xlink:href="#x5002_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.23" + id="x5004_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop29157" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop29159" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.23" + id="lg5728" + xlink:href="#x5004_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="592.31" + y1="162.60001" + x2="609.32001" + y2="145.59" + id="x5003_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0" + id="stop29143" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="1" + id="stop29145" /> + <a:midPointStop + offset="0" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="1" + style="stop-color:#E5E5E5" /> + </linearGradient> + <linearGradient + x1="592.31" + y1="162.60001" + x2="609.32001" + y2="145.59" + id="lg5732" + xlink:href="#x5003_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.24001" + id="x5000_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop29124" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop29126" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.24001" + id="lg5735" + xlink:href="#x5000_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="308.54999" + y1="149.89999" + x2="299.72" + y2="148.83" + id="XMLID_2433_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d6d6d6;stop-opacity:1" + offset="0" + id="71615" /> + <stop + style="stop-color:#a5a5a5;stop-opacity:1" + offset="1" + id="71617" /> + <a:midPointStop + offset="0" + style="stop-color:#D6D6D6" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D6D6D6" /> + <a:midPointStop + offset="1" + style="stop-color:#A5A5A5" /> + </linearGradient> + <linearGradient + x1="308.54999" + y1="149.89999" + x2="299.72" + y2="148.83" + id="lg1952" + xlink:href="#XMLID_2433_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> + <radialGradient + cx="307.39999" + cy="121" + r="23.35" + fx="307.39999" + fy="121" + id="XMLID_2432_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.98,0,0,0.98,2.88,2.75)"> + <stop + style="stop-color:#d2d2d2;stop-opacity:1" + offset="0.19" + id="71592" /> + <stop + style="stop-color:#cfcfcf;stop-opacity:1" + offset="0.44999999" + id="71594" /> + <stop + style="stop-color:#c7c7c7;stop-opacity:1" + offset="0.60000002" + id="71596" /> + <stop + style="stop-color:#b9b9b9;stop-opacity:1" + offset="0.74000001" + id="71598" /> + <stop + style="stop-color:#a4a4a4;stop-opacity:1" + offset="0.86000001" + id="71600" /> + <stop + style="stop-color:#8a8a8a;stop-opacity:1" + offset="0.95999998" + id="71602" /> + <stop + style="stop-color:gray;stop-opacity:1" + offset="1" + id="71604" /> + <a:midPointStop + offset="0.19" + style="stop-color:#D2D2D2" /> + <a:midPointStop + offset="0.8" + style="stop-color:#D2D2D2" /> + <a:midPointStop + offset="1" + style="stop-color:#808080" /> + </radialGradient> + <radialGradient + cx="307.39999" + cy="121" + r="23.35" + fx="307.39999" + fy="121" + id="radialGradient2331" + xlink:href="#XMLID_2432_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-276.62,-121.54)" /> + <linearGradient + x1="294.13" + y1="127.07" + x2="294.13" + y2="142.2" + id="XMLID_2430_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b5d8ff;stop-opacity:1" + offset="0" + id="71582" /> + <stop + style="stop-color:black;stop-opacity:1" + offset="1" + id="71584" /> + <a:midPointStop + offset="0" + style="stop-color:#B5D8FF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B5D8FF" /> + <a:midPointStop + offset="1" + style="stop-color:#000000" /> + </linearGradient> + <linearGradient + x1="294.13" + y1="127.07" + x2="294.13" + y2="142.2" + id="lg2820" + xlink:href="#XMLID_2430_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> + <linearGradient + x1="279.10999" + y1="148.03" + x2="309.16" + y2="148.03" + id="XMLID_2429_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e1e1e1;stop-opacity:1" + offset="0" + id="71564" /> + <stop + style="stop-color:#e1e1e1;stop-opacity:1" + offset="0.25" + id="71566" /> + <stop + style="stop-color:#a5a5a5;stop-opacity:1" + offset="0.44" + id="71568" /> + <stop + style="stop-color:#a5a5a5;stop-opacity:1" + offset="1" + id="71570" /> + <a:midPointStop + offset="0" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.25" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.44" + style="stop-color:#A5A5A5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#A5A5A5" /> + <a:midPointStop + offset="1" + style="stop-color:#A5A5A5" /> + </linearGradient> + <linearGradient + x1="279.10999" + y1="148.03" + x2="309.16" + y2="148.03" + id="lg2818" + xlink:href="#XMLID_2429_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> + <radialGradient + cx="622.34302" + cy="14.449" + r="26.496" + fx="622.34302" + fy="14.449" + id="lg3499_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.851,0,0,0.849,69.297,51.658)"> + <stop + style="stop-color:#23468e;stop-opacity:1" + offset="0" + id="stop10972" /> + <stop + style="stop-color:#012859;stop-opacity:1" + offset="1" + id="stop10974" /> + <a:midPointStop + offset="0" + style="stop-color:#23468E" /> + <a:midPointStop + offset="0.5" + style="stop-color:#23468E" /> + <a:midPointStop + offset="1" + style="stop-color:#012859" /> + </radialGradient> + <radialGradient + cx="622.34302" + cy="14.449" + r="26.496" + fx="622.34302" + fy="14.449" + id="rg5791" + xlink:href="#lg3499_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.858,0,0,0.857,-511.7,9.02)" /> + <linearGradient + x1="616.112" + y1="76.247002" + x2="588.14099" + y2="60.742001" + id="lg3497_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#01326e;stop-opacity:1" + offset="0" + id="stop10962" /> + <stop + style="stop-color:#012859;stop-opacity:1" + offset="1" + id="stop10964" /> + <a:midPointStop + offset="0" + style="stop-color:#01326E" /> + <a:midPointStop + offset="0.5" + style="stop-color:#01326E" /> + <a:midPointStop + offset="1" + style="stop-color:#012859" /> + </linearGradient> + <linearGradient + x1="617.698" + y1="82.445999" + x2="585.95203" + y2="54.848999" + id="lg3496_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="stop10950" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop10952" /> + <a:midPointStop + offset="0" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="617.698" + y1="82.445999" + x2="585.95203" + y2="54.848999" + id="lg5794" + xlink:href="#lg3496_" + gradientUnits="userSpaceOnUse" /> + <linearGradient + x1="601.39001" + y1="55.341" + x2="588.29199" + y2="71.515999" + id="lg3495_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop10941" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.52200001" + id="stop10943" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop10945" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.522" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="601.39001" + y1="55.341" + x2="588.29199" + y2="71.515999" + id="lg5771" + xlink:href="#lg3495_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.009,0,0,1.009,-581.615,-43.098)" /> + <linearGradient + x1="611.34601" + y1="55.279999" + x2="590.39001" + y2="81.157997" + id="lg3494_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop10932" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.52200001" + id="stop10934" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop10936" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.522" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="611.34601" + y1="55.279999" + x2="590.39001" + y2="81.157997" + id="lg5774" + xlink:href="#lg3494_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.009,0,0,1.009,-581.616,-43.098)" /> + <linearGradient + x1="798.72998" + y1="69.839996" + x2="799.04999" + y2="70.709999" + id="g3302_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#005e00;stop-opacity:1" + offset="0" + id="s6504" /> + <stop + style="stop-color:#23a11f;stop-opacity:1" + offset="1" + id="s6506" /> + <a:midPointstop + style="stop-color:#005E00" + offset="0" /> + <a:midPointstop + style="stop-color:#005E00" + offset="0.5" /> + <a:midPointstop + style="stop-color:#23A11F" + offset="1" /> + </linearGradient> + <linearGradient + x1="798.72998" + y1="69.839996" + x2="799.04999" + y2="70.709999" + id="lg5851" + xlink:href="#g3302_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> + <linearGradient + x1="779.19" + y1="122.73" + x2="811.69" + y2="149.74001" + id="g3301_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,129.19)"> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0" + id="s6483" /> + <stop + style="stop-color:#eee;stop-opacity:1" + offset="0.17" + id="s6485" /> + <stop + style="stop-color:#e3e3e3;stop-opacity:1" + offset="0.34" + id="s6487" /> + <stop + style="stop-color:#cfcfcf;stop-opacity:1" + offset="0.50999999" + id="s6489" /> + <stop + style="stop-color:#b4b4b4;stop-opacity:1" + offset="0.67000002" + id="s6491" /> + <stop + style="stop-color:#919191;stop-opacity:1" + offset="0.83999997" + id="s6493" /> + <stop + style="stop-color:#666;stop-opacity:1" + offset="1" + id="s6495" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.71" /> + <a:midPointstop + style="stop-color:#666666" + offset="1" /> + </linearGradient> + <linearGradient + x1="779.19" + y1="122.73" + x2="811.69" + y2="149.74001" + id="lg5855" + xlink:href="#g3301_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,103.123)" /> + <clipPath + id="g3299_"> + <use + id="use6469" + x="0" + y="0" + width="1005.92" + height="376.97" + xlink:href="#g101_" /> + </clipPath> + <radialGradient + cx="1189.9301" + cy="100.05" + r="40.400002" + fx="1189.9301" + fy="100.05" + id="g3300_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.34,-8.46e-2,0,0.34,394.16,137.13)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s6472" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="s6474" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointstop + style="stop-color:#000000" + offset="1" /> + </radialGradient> + <radialGradient + cx="1199.74" + cy="97.150002" + r="40.400002" + fx="1199.74" + fy="97.150002" + id="rg5860" + xlink:href="#g3300_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.409,-0.107,0,0.429,-451.489,113.149)" /> + <linearGradient + x1="796.38" + y1="67.580002" + x2="781.28003" + y2="58.549999" + id="g3298_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#4c8bca;stop-opacity:1" + offset="0" + id="s6462" /> + <stop + style="stop-color:#b7e9ff;stop-opacity:1" + offset="1" + id="s6464" /> + <a:midPointstop + style="stop-color:#4C8BCA" + offset="0" /> + <a:midPointstop + style="stop-color:#4C8BCA" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B7E9FF" + offset="1" /> + </linearGradient> + <linearGradient + x1="800.97998" + y1="140.72" + x2="777.71997" + y2="121.76" + id="g3297_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,129.19)"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="s6448" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s6450" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0.5" /> + <a:midPointstop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="800.97998" + y1="140.72" + x2="777.71997" + y2="121.76" + id="lg5890" + xlink:href="#g3297_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,129.19)" /> + <linearGradient + x1="790.03998" + y1="-16.33" + x2="779.84003" + y2="-3.73" + id="g3296_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(0,70.17)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="s6439" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.51999998" + id="s6441" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s6443" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0.5" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.52" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.5" /> + <a:midPointstop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="790.03998" + y1="-16.33" + x2="779.84003" + y2="-3.73" + id="lg5866" + xlink:href="#g3296_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,28.6)" /> + <linearGradient + x1="785.84003" + y1="72.989998" + x2="785.26001" + y2="76.279999" + id="g3293_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s6412" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="1" + id="s6414" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointstop + style="stop-color:#737373" + offset="1" /> + </linearGradient> + <linearGradient + x1="785.84003" + y1="72.989998" + x2="785.26001" + y2="76.279999" + id="lg5871" + xlink:href="#g3293_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> + <linearGradient + x1="789.37" + y1="69.879997" + x2="791.03998" + y2="77.120003" + id="g3292_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#999;stop-opacity:1" + offset="0" + id="s6403" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.28" + id="s6405" /> + <stop + style="stop-color:#666;stop-opacity:1" + offset="1" + id="s6407" /> + <a:midPointstop + style="stop-color:#999999" + offset="0" /> + <a:midPointstop + style="stop-color:#999999" + offset="0.5" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.28" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.5" /> + <a:midPointstop + style="stop-color:#666666" + offset="1" /> + </linearGradient> + <linearGradient + x1="789.37" + y1="69.879997" + x2="791.03998" + y2="77.120003" + id="lg5874" + xlink:href="#g3292_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> + <linearGradient + x1="786.65997" + y1="136.12" + x2="786.71002" + y2="134.33" + id="g3290_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,137.29)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="s6380" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="1" + id="s6382" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="1" /> + </linearGradient> + <linearGradient + x1="786.65997" + y1="136.12" + x2="786.71002" + y2="134.33" + id="lg5878" + xlink:href="#g3290_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,113.351)" /> + <radialGradient + cx="1458.77" + cy="-5.0999999" + r="35.130001" + fx="1458.77" + fy="-5.0999999" + id="g3289_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s6371" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="s6373" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointstop + style="stop-color:#999999" + offset="1" /> + </radialGradient> + <radialGradient + cx="1458.77" + cy="-5.0999999" + r="35.130001" + fx="1458.77" + fy="-5.0999999" + id="rg5881" + xlink:href="#g3289_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" /> + <radialGradient + cx="1612.98" + cy="-4.4699998" + r="36.580002" + fx="1612.98" + fy="-4.4699998" + id="g3288_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.34,0,0,0.36,238.56,86.87)"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="s6362" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0.63999999" + id="s6364" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="1" + id="s6366" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.64" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.5" /> + <a:midPointstop + style="stop-color:#737373" + offset="1" /> + </radialGradient> + <radialGradient + cx="1612.98" + cy="-4.4699998" + r="36.580002" + fx="1612.98" + fy="-4.4699998" + id="rg5884" + xlink:href="#g3288_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.408,0,0,0.448,-638.943,49.495)" /> + <radialGradient + cx="1470.5" + cy="-10.21" + r="33.290001" + fx="1470.5" + fy="-10.21" + id="g3287_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="s6347" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0.38999999" + id="s6349" /> + <stop + style="stop-color:#b1b1b1;stop-opacity:1" + offset="0.75" + id="s6351" /> + <stop + style="stop-color:#aaa;stop-opacity:1" + offset="0.88" + id="s6353" /> + <stop + style="stop-color:#9e9e9e;stop-opacity:1" + offset="0.97000003" + id="s6355" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="s6357" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.39" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.87" /> + <a:midPointstop + style="stop-color:#999999" + offset="1" /> + </radialGradient> + <radialGradient + cx="1470.5" + cy="-10.21" + r="33.290001" + fx="1470.5" + fy="-10.21" + id="rg5887" + xlink:href="#g3287_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" /> + <pattern + patternTransform="matrix(0.592927,0,0,0.592927,78,462)" + id="cream-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-365.3146,-513.505)" + id="g3047"> + id="path2858" /> + <path + inkscape:label="#path2854" + sodipodi:nodetypes="czzzz" + style="fill:#e3dcc0" + id="path3060" + d="M 390.31462,529.50504 C 390.31462,534.47304 386.28262,538.50504 381.31462,538.50504 C 376.34662,538.50504 372.31462,534.47304 372.31462,529.50504 C 372.31462,524.53704 376.34662,520.50504 381.31462,520.50504 C 386.28262,520.50504 390.31462,524.53704 390.31462,529.50504 z " /> +</g> + </pattern> + <pattern + patternTransform="matrix(0.733751,0,0,0.733751,67,367)" + id="dark-cream-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-408.0946,-513.505)" + id="dark-cream-spot" + inkscape:label="#g3043"> + <path + sodipodi:nodetypes="czzzz" + style="fill:#c8c5ac" + d="M 433.09458,529.50504 C 433.09458,534.47304 429.06258,538.50504 424.09458,538.50504 C 419.12658,538.50504 415.09458,534.47304 415.09458,529.50504 C 415.09458,524.53704 419.12658,520.50504 424.09458,520.50504 C 429.06258,520.50504 433.09458,524.53704 433.09458,529.50504 z " + id="path2953" /> + </g> + </pattern> + <pattern + patternTransform="matrix(0.375,0,0,0.375,379,400)" + id="white-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-484.3997,-513.505)" + id="white-spot" + inkscape:label="#g3035"> + <path + style="opacity:0.25;fill:white" + id="path3033" + d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z " + sodipodi:nodetypes="czzzz" /> + </g> + </pattern> + <pattern + patternTransform="matrix(0.455007,0,0,0.455007,-5e-5,1.9e-5)" + id="black-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-448.3997,-513.505)" + id="black-spot" + inkscape:label="#g3039"> + <path + sodipodi:nodetypes="czzzz" + d="M 473.39967,529.50504 C 473.39967,534.47304 469.36767,538.50504 464.39967,538.50504 C 459.43167,538.50504 455.39967,534.47304 455.39967,529.50504 C 455.39967,524.53704 459.43167,520.50504 464.39967,520.50504 C 469.36767,520.50504 473.39967,524.53704 473.39967,529.50504 z " + id="path2961" + style="opacity:0.25;fill:black" /> + </g> + </pattern> + <linearGradient + x1="501.0903" + y1="-19.2544" + x2="531.85413" + y2="0.72390002" + id="linearGradient17334" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop17336" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop17338" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop17340" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop17342" /> + <a:midPointStop + offset="0" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.5112" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.6461" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="1" + style="stop-color:#16336E" /> + </linearGradient> + <linearGradient + x1="415.73831" + y1="11.854" + x2="418.13361" + y2="18.8104" + id="linearGradient17426" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)"> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="0" + id="stop17428" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop17430" /> + <a:midPointStop + offset="0" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="0.5" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="1" + style="stop-color:#F2F2F2" /> + </linearGradient> + <linearGradient + x1="478.21341" + y1="-131.9297" + x2="469.85818" + y2="-140.28481" + id="linearGradient17434" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop17436" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop17438" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop17440" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop17442" /> + <a:midPointStop + offset="0" + style="stop-color:#F3403F" /> + <a:midPointStop + offset="0.4213" + style="stop-color:#F3403F" /> + <a:midPointStop + offset="1" + style="stop-color:#A6100C" /> + </linearGradient> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17709" + xlink:href="#XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" /> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17711" + xlink:href="#XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="linearGradient17713" + xlink:href="#XMLID_1753_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17715" + xlink:href="#XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="500.70749" + y1="-13.2441" + x2="513.46442" + y2="-2.1547" + id="linearGradient17717" + xlink:href="#XMLID_1757_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="linearGradient17721" + xlink:href="#XMLID_2274_" + gradientUnits="userSpaceOnUse" /> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="linearGradient17723" + xlink:href="#XMLID_2275_" + gradientUnits="userSpaceOnUse" /> + <linearGradient + x1="500.70749" + y1="-13.2441" + x2="513.46442" + y2="-2.1547" + id="linearGradient17416" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop17418" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop17420" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <defs + id="defs9929"> + <path + d="M 489.21,209.35 L 485.35,203.63 C 483.63,204.25 473.47,208.93 471.5,210.18 C 470.57,210.77 470.17,211.16 469.72,212.48 C 470.93,212.31 471.72,212.49 473.42,213.04 C 473.26,214.77 473.24,215.74 473.57,218.2 C 474.01,216.88 474.41,216.49 475.34,215.9 C 477.33,214.65 487.49,209.97 489.21,209.35 z " + id="XMLID_960_" /> + </defs> + <clipPath + id="clipPath17448"> + <use + id="use17450" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_960_" /> + </clipPath> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="linearGradient17452" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop17454" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop17456" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop17458" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop17460" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="linearGradient17463" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop17465" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop17467" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop17469" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop17471" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="linearGradient17807" + xlink:href="#XMLID_2275_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-177.1654,35.43307)" /> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="linearGradient17810" + xlink:href="#XMLID_2274_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-177.1654,35.43307)" /> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17812" + xlink:href="#XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" /> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17814" + xlink:href="#XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="linearGradient17816" + xlink:href="#XMLID_1753_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17818" + xlink:href="#XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17347" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop17349" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop17351" /> + <a:midPointStop + offset="0" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="1" + style="stop-color:#96BAD6" /> + </linearGradient> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="linearGradient17379" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop17381" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop17383" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="1" + style="stop-color:#F2F2F2" /> + </linearGradient> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17862" + xlink:href="#XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,-166.1427,-0.18283)" /> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17864" + xlink:href="#XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <defs + id="defs3859"> + <polygon + points="465.54,213.52 481.94,217.46 482.74,216.71 487.46,198.05 471.08,194.07 470.26,194.83 465.54,213.52 " + id="XMLID_343_" /> + </defs> + <linearGradient + x1="471.0806" + y1="201.07761" + x2="481.91711" + y2="210.4977" + id="linearGradient17389" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#6498c1;stop-opacity:1" + offset="0.005618" + id="stop17391" /> + <stop + style="stop-color:#79a9cc;stop-opacity:1" + offset="0.2332" + id="stop17393" /> + <stop + style="stop-color:#a4cde2;stop-opacity:1" + offset="0.74049997" + id="stop17395" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="1" + id="stop17397" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="5.618000e-003" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="0.4438" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="1" /> + </linearGradient> + <clipPath + id="clipPath17400"> + <use + id="use17402" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_343_" /> + </clipPath> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17404" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop17406" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop17408" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop17410" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop17412" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17882" + xlink:href="#XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <defs + id="defs3826"> + <polygon + points="463.52,216.14 480.56,220.24 481.36,219.5 483.03,202.04 469.05,196.69 468.24,197.45 463.52,216.14 " + id="XMLID_338_" /> + </defs> + <linearGradient + x1="468.2915" + y1="204.7612" + x2="479.39871" + y2="214.4166" + id="linearGradient17357" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop17359" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop17361" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <clipPath + id="clipPath17364"> + <use + id="use17366" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_338_" /> + </clipPath> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17368" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop17370" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop17372" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop17374" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop17376" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" + id="linearGradient2387" + xlink:href="#linearGradient2381" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> + <linearGradient + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" + id="linearGradient5105" + xlink:href="#linearGradient2381" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> + <linearGradient + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" + id="linearGradient5145" + xlink:href="#linearGradient2381" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient2381" + id="linearGradient2371" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" /> + </defs> + <g + transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" + id="g5089"> + <path + d="M 8.4382985,-6.28125 C 7.8309069,-6.28125 4.125,-0.33238729 4.125,1.96875 L 4.125,28.6875 C 4.125,29.533884 4.7068159,29.8125 5.28125,29.8125 L 30.84375,29.8125 C 31.476092,29.8125 31.968751,29.319842 31.96875,28.6875 L 31.96875,23.46875 L 32.25,23.46875 C 32.74684,23.46875 33.156249,23.059339 33.15625,22.5625 L 33.15625,-5.375 C 33.15625,-5.8718398 32.74684,-6.28125 32.25,-6.28125 L 8.4382985,-6.28125 z " + transform="translate(282.8327,227.1903)" + style="fill:#5c5c4f;stroke:black;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none" + id="path5091" /> + <rect + width="27.85074" + height="29.369793" + rx="1.1414107" + ry="1.1414107" + x="286.96509" + y="227.63805" + style="fill:#032c87" + id="rect5093" /> + <path + d="M 288.43262,225.43675 L 313.67442,225.43675 L 313.67442,254.80655 L 287.29827,254.83069 L 288.43262,225.43675 z " + style="fill:white" + id="rect5095" /> + <path + d="M 302.44536,251.73726 C 303.83227,259.59643 301.75225,263.02091 301.75225,263.02091 C 303.99609,261.41329 305.71651,259.54397 306.65747,257.28491 C 307.62455,259.47755 308.49041,261.71357 310.9319,263.27432 C 310.9319,263.27432 309.33686,256.07392 309.22047,251.73726 L 302.44536,251.73726 z " + style="fill:#a70000;fill-opacity:1;stroke-width:2" + id="path5097" /> + <rect + width="25.241802" + height="29.736675" + rx="0.89682275" + ry="0.89682275" + x="290.73544" + y="220.92249" + style="fill:#809cc9" + id="rect5099" /> + <path + d="M 576.47347,725.93939 L 582.84431,726.35441 L 583.25121,755.8725 C 581.35919,754.55465 576.39694,752.1117 574.98889,754.19149 L 574.98889,727.42397 C 574.98889,726.60151 575.65101,725.93939 576.47347,725.93939 z " + transform="matrix(0.499065,-0.866565,0,1,0,0)" + style="fill:#4573b3;fill-opacity:1" + id="rect5101" /> + <path + d="M 293.2599,221.89363 L 313.99908,221.89363 C 314.45009,221.89363 314.81318,222.25673 314.81318,222.70774 C 315.02865,229.0361 295.44494,244.47124 292.44579,240.30491 L 292.44579,222.70774 C 292.44579,222.25673 292.80889,221.89363 293.2599,221.89363 z " + style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1" + id="path5103" /> + </g> +</svg> Modified: branches/jbosstools-3.2.x/documentation/guides/Update_Guide/pom.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/Update_Guide/pom.xml 2011-07-18 01:48:50 UTC (rev 32972) +++ branches/jbosstools-3.2.x/documentation/guides/Update_Guide/pom.xml 2011-07-18 01:50:34 UTC (rev 32973) @@ -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>Update_Guide</docname> - <bookname>Update Guide</bookname> - </properties> - - <profiles> + <properties> + <translation>en-US</translation> + <docname>Update_Guide</docname> + <bookname>Update Guide</bookname> + </properties> + <profiles> +  - <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>  - <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>  - <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>  - <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>  - <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>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>

14 years, 9 months

1
0
0 / 0

JBoss Tools SVN: r32972 - in branches/jbosstools-3.2.x/documentation/guides/MigrationGuide: en-US and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2011-07-17 21:48:50 -0400 (Sun, 17 Jul 2011) New Revision: 32972 Modified: branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Author_Group.xml branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Book_Info.xml branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Feedback.xml branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Migration_Guide.ent branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Migration_Guide.xml branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Preface.xml branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/issues.xml branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/migration.xml branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/pom.xml Log: updated Modified: branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Author_Group.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Author_Group.xml 2011-07-18 01:46:34 UTC (rev 32971) +++ branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Author_Group.xml 2011-07-18 01:48:50 UTC (rev 32972) @@ -3,8 +3,8 @@ ]> <authorgroup> <author> - <firstname>Matthew</firstname> - <surname>Casperson</surname> - <email>mcaspers(a)redhat.com</email> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + <email>irooskov(a)redhat.com</email> </author> </authorgroup> Modified: branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Book_Info.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Book_Info.xml 2011-07-18 01:46:34 UTC (rev 32971) +++ branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Book_Info.xml 2011-07-18 01:48:50 UTC (rev 32972) @@ -5,9 +5,9 @@ <title>Migration Guide</title> <subtitle>JBoss Developer Studio 3.0x to 4.0.</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 JBoss Developer Studio Migration Guide explains how to migrate from the previous version of the JBoss Developer Studio to the latest version.</para> </abstract> Modified: branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Feedback.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Feedback.xml 2011-07-18 01:46:34 UTC (rev 32971) +++ branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Feedback.xml 2011-07-18 01:48:50 UTC (rev 32972) @@ -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=12310500&issu...">https://jira.jboss.org/jira/secure/CreateIssue.jspa?pid=12310500&issu...</ulink> - </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> +  <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/documentation/guides/MigrationGuide/en-US/Migration_Guide.ent =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Migration_Guide.ent 2011-07-18 01:46:34 UTC (rev 32971) +++ branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Migration_Guide.ent 2011-07-18 01:48:50 UTC (rev 32972) @@ -2,3 +2,6 @@ <!ENTITY BOOKID "Migration_Guide"> <!ENTITY YEAR "2011"> <!ENTITY HOLDER "Red Hat"> +<!ENTITY BZPRODUCT "JBoss Developer Studio"> +<!ENTITY BZCOMPONENT "Migration Guide"> +<!ENTITY BZURL "<ulink url='https://bugzilla.redhat.com/enter_bug.cgi?product=JBoss&percnt;20Develope...'>http://bugzilla.redhat.com/</ulink>"> Modified: branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Migration_Guide.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Migration_Guide.xml 2011-07-18 01:46:34 UTC (rev 32971) +++ branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Migration_Guide.xml 2011-07-18 01:48:50 UTC (rev 32972) @@ -7,5 +7,6 @@ <xi:include href="introduction.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> <xi:include href="migration.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> <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> </book> Modified: branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Preface.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Preface.xml 2011-07-18 01:46:34 UTC (rev 32971) +++ branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/Preface.xml 2011-07-18 01:48:50 UTC (rev 32972) @@ -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.html">Red Hat Documentation</ulink> website under the <guilabel>JBoss Developer Studio</guilabel> section. </para> -  </preface> Modified: branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/issues.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/issues.xml 2011-07-18 01:46:34 UTC (rev 32971) +++ branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/issues.xml 2011-07-18 01:48:50 UTC (rev 32972) @@ -40,19 +40,25 @@ <section> <title>Visual Editor doesn't start and "XPCOM error -2147467259" appears</title> - <para>This error shows that you have problems with your buildin XULRunner plugin.To resolve the issue,please: </para> + <para>This error shows that you have problems with your built-in XULRunner plugin. Follow these steps to resolve the issue: </para> <itemizedlist> <listitem><para>Open <property>Help -> About JBoss Developer Studio-> Installation Details... -> Configuration</property></para></listitem> <listitem><para>find org.eclipse.swt.browser.XULRunnerPath and open this path in terminal</para></listitem> <listitem><para>try xulrunner.exe -version or ./xulrunner -version command and you will see what is needed for XULRunner to work</para></listitem> </itemizedlist> + <para> + In JBoss Developer Studio 4.0, XulRunner 1.9.1.2 or above is required for the visual editor to work correctly. If you are running on a system that uses XulRunner 1.8 or earlier, you may see the above issue. + </para> + <para> + XulRunner 1.9.1.2 is supported on Windows 32-bit and 64bit, Linux 32-bit and 64-bit and Max OSZ Cocoa 32-bit. The JBoss Developer Studio distribution for Mac OSX Cocoa 64-bit does not include the Visual Page Editor. + </para> </section> <section> <title>Problems with <emphasis>not "JBDS"</emphasis> plugins</title> - <para>Some additional plugins that are not supplied by JBDS and work on JBDS 2.X may not work on 3.0.0.GA</para> + <para>Some additional plugins that are not supplied by JBoss Developer Studio and work on JBDS 2.X may not work on 3.0.0.GA</para> <itemizedlist> <listitem><para>To solve the problem check whether the plugin is compatible with Eclipse 3.5.</para></listitem> - <listitem><para>But because such pugins are not supported by JBDS, we can not guarantee its proper work.</para></listitem> + <listitem><para>But because such pugins are not supported by JBoss Developer Studio, we can not guarantee its proper work.</para></listitem> </itemizedlist> </section> Modified: branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/migration.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/migration.xml 2011-07-18 01:46:34 UTC (rev 32971) +++ branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/en-US/migration.xml 2011-07-18 01:48:50 UTC (rev 32972) @@ -21,12 +21,12 @@ <para> Workspaces created with JBDS 3.0x can generally be opened in JBDS 4.0, however this is not guaranteed be the case. Always backup your existing workspaces (see <xref linkend="sect-backup-workspace"/> for more information) before attempting to use them with JBDS 4.0. </para> - + <note> <title>Tip</title> <para> - It is possible to run JBDS 3.0x and 4.0 side by side if they have been installed into separate directories. - </para> + The JBDS executable has changed in JBDS 4.0 from <filename>eclipse</filename> to <filename>jbdevstudio</filename>. + </para> </note> </section> Modified: branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/pom.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/pom.xml 2011-07-18 01:46:34 UTC (rev 32971) +++ branches/jbosstools-3.2.x/documentation/guides/MigrationGuide/pom.xml 2011-07-18 01:48:50 UTC (rev 32972) @@ -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>Exadel_2.1_to_3.0_Migration_Guide</docname> - <bookname>Exadel 2.1 to 3.0 Migration Guide</bookname> - </properties> - - <profiles> + <properties> + <translation>en-US</translation> + <docname>Exadel_2.1_to_3.0_Migration_Guide</docname> + <bookname>Exadel 2.1 to 3.0 Migration Guide</bookname> + </properties> + <profiles> +  - <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>  - <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>  - <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>  - <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>  - <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>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>

14 years, 9 months

1
0
0 / 0

JBoss Tools SVN: r32971 - in branches/jbosstools-3.2.x/documentation/guides: JBDS_Release_Notes and 2 other directories.

by jbosstools-commits＠lists.jboss.org

Author: irooskov(a)redhat.com Date: 2011-07-17 21:46:34 -0400 (Sun, 17 Jul 2011) New Revision: 32971 Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.ent branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/New_Features.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/images/ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/images/WTP_Update_Site.png branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/images/icon.svg branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/master.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/pom.xml branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/publican.cfg Log: adding in release notes for GA Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.ent =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.ent (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.ent 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,4 @@ +<!ENTITY PRODUCT "JBoss Developer Studio"> +<!ENTITY BOOKID "4.1.0_Release_Notes"> +<!ENTITY YEAR "2011"> +<!ENTITY HOLDER "Red Hat"> Property changes on: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.ent ___________________________________________________________________ Added: svn:executable + * Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,12 @@ +<?xml version='1.0' encoding='utf-8' ?> + + + +<article> + <xi:include href="Article_Info.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> + <xi:include href="Overview.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> + <xi:include href="Component_Versions.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> + <xi:include href="Fixed_Issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> + <xi:include href="Known_Issues.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> + <xi:include href="Revision_History.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +</article> Property changes on: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/4.1.0_Release_Notes.xml ___________________________________________________________________ Added: svn:executable + * Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Article_Info.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,26 @@ +<?xml version='1.0' encoding='utf-8' ?> + + + +<articleinfo> + <title>4.1.0 Release Notes</title> + <subtitle>Information about the changes made for this release of the JBoss Developer Studio.</subtitle> + <productname>JBoss Developer Studio</productname> + <productnumber>4.1</productnumber> + <edition>0</edition> + <pubsnumber>2</pubsnumber> + <abstract> + <para> + These release notes contain important information related to the JBoss Developer Studio. New features, known issues, resources, and other current issues are addressed here. + </para> + </abstract> + <corpauthor> + <inlinemediaobject> + <imageobject> + <imagedata fileref="Common_Content/images/title_logo.svg" format="SVG" /> + </imageobject> + </inlinemediaobject> + </corpauthor> + <xi:include href="Common_Content/Legal_Notice.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> + <xi:include href="Author_Group.xml" xmlns:xi="http://www.w3.org/2001/XInclude"></xi:include> +</articleinfo> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Author_Group.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,10 @@ +<?xml version='1.0' encoding='utf-8' ?> +<!DOCTYPE Article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ +]> +<authorgroup> + <author> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + <email>irooskov(a)redhat.com</email> + </author> +</authorgroup> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Component_Versions.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,34 @@ +<?xml version='1.0' encoding='utf-8' ?> +<section id="Component_Versions"> + <title>Component Versions</title> + <para> + This section details the versions of the components which create the JBoss Developer Studio that can be found in this release. + </para> + <itemizedlist> + <listitem> + <para> + Eclipse 3.6 + </para> + </listitem> + <listitem> + <para> + JBoss Tools 3.2.1 + </para> + </listitem> + <listitem> + <para> + JBoss Enterprise Application Platform 5.1 + </para> + </listitem> + </itemizedlist> + <note> + <para> + The Enterprise Application Platform Server has been redefined for the enterprise market to a level where direct association to a community release can no longer be drawn. + </para> + </note> + <important> + <para> + The Drools Rule editor has been removed from this release. For further information on why this has occurred, see <ulink url="https://issues.jboss.org/browse/JBIDE-9052">JBIDE-9052</ulink> + </para> + </important> +</section> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Fixed_Issues.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,344 @@ +<?xml version='1.0' encoding='utf-8' ?> +<section id="Issues-fixed-in-this-release"> + <title> + Features added and issues fixed in version 4.1.0 + </title> + + <formalpara> + <title>BPEL</title> + <para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBDS-1610">JBDS-1610</ulink>: BPEL tooling is now supported as an additional tool for JBoss Developer Studio. Many bug fixes and enhancements have been applied to it in order to bring it from a technology preview to a supported component. + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> + <formalpara> + <title>Contexts and Dependency Injection (CDI)</title> + <para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBIDE-3126">JBIDE-3126</ulink>: Validation for the serializablity of injected beans into passive-scoped beans has been added. This ensures that if a bean belongs to <property>@SessionScoped</property>, <property>@ConversationScope</property> or any <property>@NormalScope(passivating=true)</property> and it is not stateful (<property>@Stateful</property>), the bean is checked to see if it implements <classname>java.io.Serializible</classname>. If it does implement the Serializible class, then it is marked as an error. + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> +  +  +  + <formalpara> + <title>ESB</title> + <para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8569">JBIDE-8569</ulink>: Classes within the JBoss ESB Editor and ESB Message Persister are now filtered within the <guilabel>Select class</guilabel> dialog that is invoked through the <guilabel>Browse</guilabel> button. Content assist proposals are also filtered within the text field instead of a drop-down list, providing a significant performance enhancement over previously voiced solutions. + </para> + </listitem> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8567">JBIDE-8567</ulink>: A drop-down list has been added to the JBoss ESB Editor and Route in order to allow selection of a predefined <guilabel>Service Category</guilabel> or <guilabel>Service Name</guilabel>. + </para> + </listitem> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8466">JBIDE-8466</ulink>: The <guilabel>Rule Agent Properties</guilabel> property has been added to the <guilabel>Content Based Router Action</guilabel> section of the JBoss ESB Editor. The following actions are now also supported through drop-down lists: <property>org.jboss.soa.esb.actions.ContentBasedWiretap</property> and <property>org.jboss.soa.esb.actions.MessageFilter</property>. + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> +  +  +  +  +  +  +  +  +  + +  + <formalpara> + <title>RichFaces</title> + <para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8617">JBIDE-8617</ulink>: A new RichFaces 4 palette is available to assist with RichFaces 4 components. This palette is hidden by default. + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> +  +  +  + <formalpara> + <title>Teiid Designer</title> + <para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8399">JBIDE-8399</ulink>: The engine behind the incorporated project examples that are distributed with the tools can now recognize a Teiid instance within a JBoss server. This has allowed for Teiid requirements to be added to Teiid Designer project examples. + </para> + </listitem> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/TEIIDDES-934">TEIIDDES-934</ulink>: An error was apparent in previous releases of Teiid Designer where the number of models added to a VDB could grow so large that data roles became inaccessible from the menu. This was caused because no scrollbar existed for the menu, meaning menu items would persist past the bottom of the screen without any way for the user to see them. This issue has been corrected in this latest release. + </para> + </listitem> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/TEIIDDES-877">TEIIDDES-877</ulink>: When creating a new Teiid project, the Teiid Designer perspective would not be opened by default. In this version, a user is asked if they would like to open the corresponding Teiid Designer perspective when they have created a new Teiid project. + </para> + </listitem> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/TEIIDDES-869">TEIIDDES-869</ulink>: The Web Service model that was generated by the <guilabel>New Model Wizard</guilabel> was incorrect, with errors in the <methodname>invoke</methodname> and <methodname>invokeHTTP</methodname> procedures. These errors meant that the resulting parameters from the methods would be modeled as <property>IN</property>, rather than as a <property>result</property>. It also meant that the <property>contenttype</property> of the <methodname>invokeHttp</methodname> should be an <property>OUT</property> parameter. These errors have been corrected in this release. + </para> + </listitem> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/TEIIDDES-859">TEIIDDES-859</ulink>: In an example project, the ability to preview data would fail due to the preview jobs starting before the auto-build and locking model resources. Scheduling of the preview jobs are now delayed in order to ensure there is enough time for the auto-build to start. + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> +  +  + <formalpara> + <title>Web Tools Platform</title> + <para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBDS-1602">JBDS-1602</ulink>: The Web Service Tester tool included as part of the Web Tools Platform contained an issue that would generate incorrect SOAP code, causing marshaling issues expressed as a <exceptionname>NullPointerException</exceptionname>. Multiple namespaces can now be handled without error and correct SOAP code is generated, removing marshaling issues. + </para> + </listitem> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8770">JBIDE-8770</ulink>: Sample input has been provided for Web Service Definition Language (WSDL) with a Simple Object Access Protocol (SOAP) header definition. This allows users a foundation to create their own WSDL applications that utilize SOAP definitions. + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> +  +  + <formalpara> + <title>General Issues</title> + <para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBDS-1268">JBDS-1268</ulink>: The JBoss Developer Studio can now be installed by passing the installer a settings file named <filename>InstallConfigRecord.xml</filename>. To undertake this, setup an <filename>InstallConfigRecord.xml</filename> and run the following on a command line: <code>java -jar jbdevstudio-4.1.0.GA.jar InstallConfigRecord.xml</code>. This allows for an automated and reproducible installation. For further information consult the <emphasis>Getting Started Guide</emphasis>. + </para> + </listitem> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBIDE-8596">JBIDE-8596</ulink>: The Properties editor for project files has been improved by allowing the <keycap>Enter</keycap> key to be pressed on a cell to begin editing its contents. Likewise, by performing a single mouse click a user can also edit the contents of a cell (previously a user had to double click to edit a cell). + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> +</section> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,50 @@ +<?xml version='1.0' encoding='utf-8' ?> +<section id="Known_Issues_with_this_release"> + <title> + Known Issues in version 4.1.0 + </title> + <para> + Following is a list of known issues at the time of release. + </para> + <formalpara> + <title>General Known Issues</title> + <para> + <itemizedlist> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBDS-1685">JBDS-1685</ulink>: Upon installing Subclipse from the JBoss Developer Studio Extras site and restarting your JBoss Developer Studio installation, an error exists that sets a default SVN property incorrectly. The workaround for this issue is to navigate to <menuchoice> + <guimenuitem>Window</guimenuitem> + <guimenuitem>Preferences</guimenuitem> + <guimenuitem>Team</guimenuitem> + <guimenuitem>SVN</guimenuitem> + </menuchoice>. + </para> + <para> + If you then see an error window, click the <guibutton>OK</guibutton> button. + </para> + <para> + On the SVN Preferences page, in the <guilabel>SVN interface</guilabel> section, change the drop-down list value of <guilabel>Client</guilabel> to <guimenuitem>SVNKit (Pure Java) SVNKit v1.3.5.7406</guimenuitem>. + </para> + <para> + Click the <guibutton>Apply</guibutton> button and then the <guibutton>OK</guibutton> button. + </para> + <para> + Subclipse will now function correctly. + </para> + </listitem> + <listitem> + <para> + <ulink url="http://jira.jboss.com/jira/browse/JBDS-1643">JBDS-1643</ulink> and <ulink url="http://jira.jboss.com/jira/browse/SOA-3051">SOA-3051</ulink>: JBoss Developer Studio 4.1 assumes the use of Drools 5.0 or above for project creation. If using an earlier version of Drools or JBoss Rules, code compatibility must be set to your version of Drools or JBoss Rules in the last page of the project creation wizard. + </para> + <para> + If you need to set code compatibility to an older version of Drools or JBoss Rules, you may notice multiple warnings when creating a project relating to the new Drools 5 API. These warnings will not affect your project and can be turned off by navigating to <menuchoice> + <guimenuitem>Window</guimenuitem> + <guimenuitem>Preferences</guimenuitem> + <guimenuitem>Drools</guimenuitem> + </menuchoice> and setting the <guilabel>Internal Drools classes are</guilabel> drop-down box to <guilabel>Accessible</guilabel>. + </para> + </listitem> + </itemizedlist> + </para> + </formalpara> +</section> Property changes on: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Known_Issues.xml ___________________________________________________________________ Added: svn:executable + * Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/New_Features.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/New_Features.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/New_Features.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,7 @@ +<?xml version='1.0' encoding='utf-8' ?> +<section id="New_Features"> + <title>New Features in JBoss Developer Studio 4.1</title> + <para> + New product information to go here + </para> +</section> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Overview.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,126 @@ +<?xml version='1.0' encoding='utf-8' ?> +<section id="Overview"> + <title>Overview</title> + <para> + JBoss Developer Studio 4.1 is a major release of the Eclipse based IDE developed and supported by Red Hat (the visual tooling components are supported for 3 years, and the runtime platform for 5 years). The IDE, which is available for Windows, Linux and OS X, provides tooling that allows for rapid Web 2.0 application development on the JBoss Enterprise Application Platform. This release also improves support for SOA application development with the JBoss Enterprise SOA Platform. + </para> + <para> + JBoss Developer Studio 4.1 contains many new features, including: + </para> + <itemizedlist> + <listitem> + <para> + Scriptble install of JBoss Developer Studio 4.1. When installing JBoss Developer Studio 4.1, you can now pass the installation a <filename>InstallConfigRecord.xml</filename> file to install with pre-defined settings, ensuring no user interaction is required. For further details see the release note for JBDS-1268 in the new and fixed issues section of this document, or the <emphasis>Getting Started Guide</emphasis> for this release. + </para> + </listitem> + <listitem> + <para> + Full BPEL Editor support through the JBoss Developer Studio Extras site. The BPEL Editor is now fully supported as an add-on to your basic install of JBoss Developer Studio 4.1. To access this plug-in, add the JBoss Developer Studio Extras site  to your installation; see the BPEL User Guide for further information. + </para> + </listitem> + </itemizedlist> + <important> + <para> + If you are installing on a Linux distribution you must set the following limits in <filename>/etc/security/limits.conf</filename> upon installation completion and before running JBoss Developer Studio: + </para> +<programlisting> +* soft nofile 9216 +* hard nofile 9216 +</programlisting> + <para> + These settings will ensure you do not encounter an error reguarding maximum open files when starting JBoss Developer Studio. + </para> + <para> + For further installation instructions see the Getting Started Guide for this release, available at: <ulink url="http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/index.html">http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/index.html</ulink> + </para> + </important> +  +  + </section> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/Revision_History.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,23 @@ +<?xml version='1.0' encoding='utf-8' ?> + +<appendix> + <title>Revision History</title> + <simpara> + <revhistory> + <revision> + <revnumber>0-0</revnumber> + <date>Fri May 27 2011</date> + <author> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + <email>irooskov(a)redhat.com</email> + </author> + <revdescription> + <simplelist> + <member>Initial creation of release notes document</member> + </simplelist> + </revdescription> + </revision> + </revhistory> + </simpara> +</appendix> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/images/WTP_Update_Site.png =================================================================== (Binary files differ) Property changes on: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/images/WTP_Update_Site.png ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/images/icon.svg =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/images/icon.svg (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/images/icon.svg 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,3936 @@ +<?xml version="1.0" encoding="UTF-8" standalone="no"?> + +<svg + xmlns:ns="http://ns.adobe.com/AdobeSVGViewerExtensions/3/" + xmlns:a="http://ns.adobe.com/AdobeSVGViewerExtensions/3.0/" + xmlns:dc="http://purl.org/dc/elements/1.1/" + xmlns:cc="http://web.resource.org/cc/" + xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" + xmlns:svg="http://www.w3.org/2000/svg" + xmlns="http://www.w3.org/2000/svg" + xmlns:xlink="http://www.w3.org/1999/xlink" + xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd" + xmlns:inkscape="http://www.inkscape.org/namespaces/inkscape" + version="1.0" + width="32" + height="32" + id="svg3017" + sodipodi:version="0.32" + inkscape:version="0.44+devel" + sodipodi:docname="book.svg" + sodipodi:docbase="/home/andy/Desktop"> + <metadata + id="metadata489"> + <rdf:RDF> + <cc:Work + rdf:about=""> + <dc:format>image/svg+xml</dc:format> + <dc:type + rdf:resource="http://purl.org/dc/dcmitype/StillImage" /> + </cc:Work> + </rdf:RDF> + </metadata> + <sodipodi:namedview + inkscape:window-height="480" + inkscape:window-width="858" + inkscape:pageshadow="0" + inkscape:pageopacity="0.0" + guidetolerance="10.0" + gridtolerance="10.0" + objecttolerance="10.0" + borderopacity="1.0" + bordercolor="#666666" + pagecolor="#ffffff" + id="base" + inkscape:zoom="1" + inkscape:cx="16" + inkscape:cy="15.944056" + inkscape:window-x="0" + inkscape:window-y="33" + inkscape:current-layer="svg3017" /> + <defs + id="defs3019"> + <linearGradient + id="linearGradient2381"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop2383" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="stop2385" /> + </linearGradient> + <linearGradient + x1="415.73831" + y1="11.854" + x2="418.13361" + y2="18.8104" + id="XMLID_1758_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)"> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="0" + id="stop3903" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop3905" /> + <a:midPointStop + style="stop-color:#CCCCCC" + offset="0" /> + <a:midPointStop + style="stop-color:#CCCCCC" + offset="0.5" /> + <a:midPointStop + style="stop-color:#F2F2F2" + offset="1" /> + </linearGradient> + <linearGradient + x1="500.70749" + y1="-13.2441" + x2="513.46442" + y2="-2.1547" + id="XMLID_1757_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop3890" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop3892" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <clipPath + id="XMLID_1755_"> + <use + id="use3874" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_343_" /> + </clipPath> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop3877" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop3879" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop3881" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop3883" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="471.0806" + y1="201.07761" + x2="481.91711" + y2="210.4977" + id="XMLID_1754_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#6498c1;stop-opacity:1" + offset="0.005618" + id="stop3863" /> + <stop + style="stop-color:#79a9cc;stop-opacity:1" + offset="0.2332" + id="stop3865" /> + <stop + style="stop-color:#a4cde2;stop-opacity:1" + offset="0.74049997" + id="stop3867" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="1" + id="stop3869" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="5.618000e-003" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="0.4438" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="1" /> + </linearGradient> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="XMLID_1753_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop3851" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop3853" /> + <a:midPointStop + style="stop-color:#B2B2B2" + offset="0" /> + <a:midPointStop + style="stop-color:#B2B2B2" + offset="0.5" /> + <a:midPointStop + style="stop-color:#F2F2F2" + offset="1" /> + </linearGradient> + <clipPath + id="XMLID_1751_"> + <use + id="use3837" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_338_" /> + </clipPath> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop3840" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop3842" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop3844" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop3846" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="468.2915" + y1="204.7612" + x2="479.39871" + y2="214.4166" + id="XMLID_1750_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop3830" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop3832" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop3818" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop3820" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <linearGradient + x1="501.0903" + y1="-19.2544" + x2="531.85413" + y2="0.72390002" + id="XMLID_1748_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop3803" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop3805" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop3807" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop3809" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="XMLID_2275_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop9947" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop9949" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop9951" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop9953" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <clipPath + id="XMLID_2273_"> + <use + id="use9933" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_960_" /> + </clipPath> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="XMLID_2274_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop9936" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop9938" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop9940" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop9942" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <linearGradient + x1="478.21341" + y1="-131.9297" + x2="469.85818" + y2="-140.28481" + id="XMLID_2272_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop9917" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop9919" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop9921" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop9923" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <marker + refX="0" + refY="0" + orient="auto" + style="overflow:visible" + id="TriangleInM"> + <path + d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z " + transform="scale(-0.4,-0.4)" + style="fill:#5c5c4f" + id="path3197" /> + </marker> + <linearGradient + x1="200.7363" + y1="100.4028" + x2="211.99519" + y2="89.143997" + id="XMLID_3298_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#bfbfbf;stop-opacity:1" + offset="0" + id="stop20103" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop20105" /> + <a:midPointStop + offset="0" + style="stop-color:#BFBFBF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#BFBFBF" /> + <a:midPointStop + offset="1" + style="stop-color:#F2F2F2" /> + </linearGradient> + <linearGradient + x1="200.7363" + y1="100.4028" + x2="211.99519" + y2="89.143997" + id="linearGradient36592" + xlink:href="#XMLID_3298_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="181.2925" + y1="110.8481" + x2="192.6369" + y2="99.5037" + id="XMLID_3297_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="stop20096" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop20098" /> + <a:midPointStop + offset="0" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="181.2925" + y1="110.8481" + x2="192.6369" + y2="99.5037" + id="linearGradient36595" + xlink:href="#XMLID_3297_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="211.77589" + y1="105.7749" + x2="212.6619" + y2="108.2092" + id="XMLID_3296_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#0f6124;stop-opacity:1" + offset="0" + id="stop20087" /> + <stop + style="stop-color:#219630;stop-opacity:1" + offset="1" + id="stop20089" /> + <a:midPointStop + offset="0" + style="stop-color:#0F6124" /> + <a:midPointStop + offset="0.5" + style="stop-color:#0F6124" /> + <a:midPointStop + offset="1" + style="stop-color:#219630" /> + </linearGradient> + <linearGradient + x1="211.77589" + y1="105.7749" + x2="212.6619" + y2="108.2092" + id="linearGradient36677" + xlink:href="#XMLID_3296_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="208.9834" + y1="116.8296" + x2="200.0811" + y2="96.834602" + id="XMLID_3295_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop20076" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.5" + id="stop20078" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop20080" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="208.9834" + y1="116.8296" + x2="200.0811" + y2="96.834602" + id="linearGradient36604" + xlink:href="#XMLID_3295_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="195.5264" + y1="97.911102" + x2="213.5213" + y2="115.9061" + id="XMLID_3294_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="0" + id="stop20069" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop20071" /> + <a:midPointStop + offset="0" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="0.5" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="195.5264" + y1="97.911102" + x2="213.5213" + y2="115.9061" + id="linearGradient36607" + xlink:href="#XMLID_3294_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="186.1938" + y1="109.1343" + x2="206.6881" + y2="88.639999" + id="XMLID_3293_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop20056" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.16850001" + id="stop20058" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.23029999" + id="stop20060" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.2809" + id="stop20062" /> + <stop + style="stop-color:#c2c2c2;stop-opacity:1" + offset="0.5" + id="stop20064" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.1685" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.2303" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.2809" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#C2C2C2" /> + </linearGradient> + <linearGradient + x1="186.1938" + y1="109.1343" + x2="206.6881" + y2="88.639999" + id="linearGradient36610" + xlink:href="#XMLID_3293_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <linearGradient + x1="184.8569" + y1="112.2676" + x2="211.94099" + y2="89.541397" + id="XMLID_3292_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop20043" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.16850001" + id="stop20045" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.23029999" + id="stop20047" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0.2809" + id="stop20049" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop20051" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.1685" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.2303" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.2809" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="184.8569" + y1="112.2676" + x2="211.94099" + y2="89.541397" + id="linearGradient36613" + xlink:href="#XMLID_3292_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.029078,0,0,1,-183.2624,-79.44655)" /> + <marker + refX="0" + refY="0" + orient="auto" + style="overflow:visible" + id="TriangleOutM"> + <path + d="M 5.77,0 L -2.88,5 L -2.88,-5 L 5.77,0 z " + transform="scale(0.4,0.4)" + style="fill:#5c5c4f;fill-rule:evenodd;stroke-width:1pt;marker-start:none" + id="path3238" /> + </marker> + <linearGradient + x1="165.3" + y1="99.5" + x2="165.3" + y2="115.9" + id="XMLID_3457_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#999;stop-opacity:1" + offset="0" + id="stop8309" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0.30000001" + id="stop8311" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="1" + id="stop8313" /> + <a:midPointstop + offset="0" + style="stop-color:#999999" /> + <a:midPointstop + offset="0.5" + style="stop-color:#999999" /> + <a:midPointstop + offset="0.3" + style="stop-color:#B2B2B2" /> + <a:midPointstop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointstop + offset="1" + style="stop-color:#B2B2B2" /> + </linearGradient> + <linearGradient + x1="165.3" + y1="99.5" + x2="165.3" + y2="115.9" + id="lg1997" + xlink:href="#XMLID_3457_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="175" + y1="99.800003" + x2="175" + y2="112.5" + id="XMLID_3456_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="0" + id="stop8300" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="0.60000002" + id="stop8302" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="1" + id="stop8304" /> + <a:midPointstop + offset="0" + style="stop-color:#737373" /> + <a:midPointstop + offset="0.5" + style="stop-color:#737373" /> + <a:midPointstop + offset="0.6" + style="stop-color:#191919" /> + <a:midPointstop + offset="0.5" + style="stop-color:#191919" /> + <a:midPointstop + offset="1" + style="stop-color:#191919" /> + </linearGradient> + <linearGradient + x1="175" + y1="99.800003" + x2="175" + y2="112.5" + id="lg2000" + xlink:href="#XMLID_3456_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="168.8" + y1="107.1" + x2="164.5" + y2="110" + id="XMLID_3455_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#666;stop-opacity:1" + offset="0" + id="stop8291" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="0.69999999" + id="stop8293" /> + <stop + style="stop-color:#191919;stop-opacity:1" + offset="1" + id="stop8295" /> + <a:midPointstop + offset="0" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.5" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.7" + style="stop-color:#191919" /> + <a:midPointstop + offset="0.5" + style="stop-color:#191919" /> + <a:midPointstop + offset="1" + style="stop-color:#191919" /> + </linearGradient> + <linearGradient + x1="168.8" + y1="107.1" + x2="164.5" + y2="110" + id="lg2003" + xlink:href="#XMLID_3455_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + id="lg63694"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop63696" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="stop63698" /> + </linearGradient> + <linearGradient + x1="458" + y1="483" + x2="465.20001" + y2="271.39999" + id="lg2006" + xlink:href="#lg63694" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(6.3e-2,0,0,6.3e-2,-1.3,-9.8)" /> + <linearGradient + x1="176.3" + y1="110.1" + x2="158.7" + y2="105" + id="XMLID_3453_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#666;stop-opacity:1" + offset="0" + id="stop8271" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="0.2" + id="stop8273" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop8275" /> + <a:midPointstop + offset="0" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.5" + style="stop-color:#666666" /> + <a:midPointstop + offset="0.2" + style="stop-color:#737373" /> + <a:midPointstop + offset="0.5" + style="stop-color:#737373" /> + <a:midPointstop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="176.3" + y1="110.1" + x2="158.7" + y2="105" + id="lg2009" + xlink:href="#XMLID_3453_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="173.60001" + y1="118.9" + x2="172.8" + y2="128.2" + id="XMLID_3449_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8232" /> + <stop + style="stop-color:#fff95e;stop-opacity:1" + offset="0.60000002" + id="stop8234" /> + <stop + style="stop-color:#ecd600;stop-opacity:1" + offset="1" + id="stop8236" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.6" + style="stop-color:#FFF95E" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFF95E" /> + <a:midPointstop + offset="1" + style="stop-color:#ECD600" /> + </linearGradient> + <linearGradient + x1="173.60001" + y1="118.9" + x2="172.8" + y2="128.2" + id="lg2016" + xlink:href="#XMLID_3449_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <radialGradient + cx="284.60001" + cy="172.60001" + r="6.5" + fx="284.60001" + fy="172.60001" + id="XMLID_3448_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8219" /> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0.30000001" + id="stop8221" /> + <stop + style="stop-color:#c96b00;stop-opacity:1" + offset="0.89999998" + id="stop8223" /> + <stop + style="stop-color:#9a5500;stop-opacity:1" + offset="1" + id="stop8225" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.3" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.9" + style="stop-color:#C96B00" /> + <a:midPointstop + offset="0.5" + style="stop-color:#C96B00" /> + <a:midPointstop + offset="1" + style="stop-color:#9A5500" /> + </radialGradient> + <radialGradient + cx="284.60001" + cy="172.60001" + r="6.5" + fx="284.60001" + fy="172.60001" + id="rg2020" + xlink:href="#XMLID_3448_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.513992,0,0,2.347576,-689.1621,-378.5717)" /> + <linearGradient + x1="158.10001" + y1="123" + x2="164.2" + y2="126.6" + id="XMLID_3447_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecd600;stop-opacity:1" + offset="0" + id="stop8204" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.30000001" + id="stop8206" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop8208" /> + <a:midPointstop + offset="0" + style="stop-color:#ECD600" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECD600" /> + <a:midPointstop + offset="0.3" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="158.10001" + y1="123" + x2="164.2" + y2="126.6" + id="lg2026" + xlink:href="#XMLID_3447_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <radialGradient + cx="280.89999" + cy="163.7" + r="10.1" + fx="280.89999" + fy="163.7" + id="XMLID_3446_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.4,0,0,1.4,-237.3,-126.8)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop8197" /> + <stop + style="stop-color:#fff95e;stop-opacity:1" + offset="1" + id="stop8199" /> + <a:midPointstop + offset="0" + style="stop-color:#FFFFFF" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointstop + offset="1" + style="stop-color:#FFF95E" /> + </radialGradient> + <radialGradient + cx="280.89999" + cy="163.7" + r="10.1" + fx="280.89999" + fy="163.7" + id="rg2029" + xlink:href="#XMLID_3446_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.7,0,0,1.7,-457.5,-266.8)" /> + <linearGradient + x1="156.5" + y1="122.7" + x2="180.10001" + y2="122.7" + id="XMLID_3445_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8184" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.2" + id="stop8186" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.30000001" + id="stop8188" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.40000001" + id="stop8190" /> + <stop + style="stop-color:#d68100;stop-opacity:1" + offset="1" + id="stop8192" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.2" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.3" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.4" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="1" + style="stop-color:#D68100" /> + </linearGradient> + <linearGradient + x1="156.5" + y1="122.7" + x2="180.10001" + y2="122.7" + id="lg2032" + xlink:href="#XMLID_3445_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="156.39999" + y1="115.4" + x2="180.10001" + y2="115.4" + id="XMLID_3444_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ecb300;stop-opacity:1" + offset="0" + id="stop8171" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.2" + id="stop8173" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.30000001" + id="stop8175" /> + <stop + style="stop-color:#ffe900;stop-opacity:1" + offset="0.40000001" + id="stop8177" /> + <stop + style="stop-color:#d68100;stop-opacity:1" + offset="1" + id="stop8179" /> + <a:midPointstop + offset="0" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.5" + style="stop-color:#ECB300" /> + <a:midPointstop + offset="0.2" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.3" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFFFB3" /> + <a:midPointstop + offset="0.4" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="0.5" + style="stop-color:#FFE900" /> + <a:midPointstop + offset="1" + style="stop-color:#D68100" /> + </linearGradient> + <linearGradient + x1="156.39999" + y1="115.4" + x2="180.10001" + y2="115.4" + id="lg2035" + xlink:href="#XMLID_3444_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.2,0,0,1.2,-175.9,-114.6)" /> + <linearGradient + x1="379.70001" + y1="167.89999" + x2="383.89999" + y2="172.89999" + id="lg4286_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s16159" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.1" + id="s16161" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="1" + id="s16163" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.1" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#737373" + offset="1" /> + </linearGradient> + <linearGradient + x1="379.60001" + y1="167.8" + x2="383.79999" + y2="172" + id="lg6416" + xlink:href="#lg4286_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.622156,0.623859,-0.623859,2.62182,-882.9706,-673.7921)" /> + <linearGradient + x1="384.20001" + y1="169.8" + x2="384.79999" + y2="170.39999" + id="lg4285_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="0" + id="s16152" /> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="1" + id="s16154" /> + <ns:midPointStop + style="stop-color:#737373" + offset="0" /> + <ns:midPointStop + style="stop-color:#737373" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#D9D9D9" + offset="1" /> + </linearGradient> + <linearGradient + x1="384.20001" + y1="169.8" + x2="384.79999" + y2="170.39999" + id="lg6453" + xlink:href="#lg4285_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" /> + <linearGradient + x1="380.5" + y1="172.60001" + x2="382.79999" + y2="173.7" + id="lg4284_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8,0.2,-0.2,0.8,78.8,38.1)"> + <stop + style="stop-color:gray;stop-opacity:1" + offset="0" + id="s16145" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="1" + id="s16147" /> + <ns:midPointStop + style="stop-color:#808080" + offset="0" /> + <ns:midPointStop + style="stop-color:#808080" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#E5E5E5" + offset="1" /> + </linearGradient> + <linearGradient + x1="380.5" + y1="172.60001" + x2="382.79999" + y2="173.7" + id="lg6456" + xlink:href="#lg4284_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.6,0.6,-0.6,2.6,-883,-673.8)" /> + <radialGradient + cx="347.29999" + cy="244.5" + r="5.1999998" + fx="347.29999" + fy="244.5" + id="lg4282_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> + <stop + style="stop-color:#333;stop-opacity:1" + offset="0" + id="s16135" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="s16137" /> + <ns:midPointStop + style="stop-color:#333333" + offset="0" /> + <ns:midPointStop + style="stop-color:#333333" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#999999" + offset="1" /> + </radialGradient> + <linearGradient + x1="310.39999" + y1="397.70001" + x2="310.89999" + y2="399.5" + id="lg4280_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="0" + id="s16111" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.60000002" + id="s16113" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="1" + id="s16115" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.6" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="1" /> + </linearGradient> + <linearGradient + x1="310.39999" + y1="397.70001" + x2="310.89999" + y2="399.5" + id="lg6467" + xlink:href="#lg4280_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> + <linearGradient + x1="310.89999" + y1="395.79999" + x2="313.29999" + y2="403.10001" + id="lg4279_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0" + id="s16100" /> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0.40000001" + id="s16102" /> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="0.89999998" + id="s16104" /> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="1" + id="s16106" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.4" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0.9" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="310.89999" + y1="395.79999" + x2="313.29999" + y2="403.10001" + id="lg6465" + xlink:href="#lg4279_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> + <linearGradient + x1="307.79999" + y1="395.20001" + x2="313.79999" + y2="413.60001" + id="lg4278_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.7,-0.7,0.7,0.7,-153.4,180.6)"> + <stop + style="stop-color:#ffffb3;stop-opacity:1" + offset="0" + id="s16091" /> + <stop + style="stop-color:#fcd72f;stop-opacity:1" + offset="0.40000001" + id="s16093" /> + <stop + style="stop-color:#ffcd00;stop-opacity:1" + offset="1" + id="s16095" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFB3" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FCD72F" + offset="0.4" /> + <ns:midPointStop + style="stop-color:#FCD72F" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFCD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="306.5" + y1="393" + x2="309" + y2="404" + id="lg6400" + xlink:href="#lg4278_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.4,-2.4,2.4,2.4,-1663.6,-195)" /> + <linearGradient + x1="352.10001" + y1="253.60001" + x2="348.5" + y2="237.8" + id="lg4276_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> + <stop + style="stop-color:#ffff87;stop-opacity:1" + offset="0" + id="s16077" /> + <stop + style="stop-color:#ffad00;stop-opacity:1" + offset="1" + id="s16079" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFAD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="335.60001" + y1="354.79999" + x2="337.89999" + y2="354.79999" + id="lg4275_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="s16057" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.80000001" + id="s16059" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="s16061" /> + <ns:midPointStop + style="stop-color:#D9D9D9" + offset="0" /> + <ns:midPointStop + style="stop-color:#D9D9D9" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.8" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="1" /> + </linearGradient> + <linearGradient + x1="335.60001" + y1="354.79999" + x2="337.89999" + y2="354.79999" + id="lg6463" + xlink:href="#lg4275_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> + <linearGradient + x1="337.39999" + y1="353.10001" + x2="339.39999" + y2="357.10001" + id="lg4274_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s16048" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.1" + id="s16050" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s16052" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.1" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="337.39999" + y1="353.10001" + x2="339.39999" + y2="357.10001" + id="lg6461" + xlink:href="#lg4274_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> + <linearGradient + x1="334.39999" + y1="355.5" + x2="335.5" + y2="356.79999" + id="lg4273_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9,-0.5,0.5,0.9,-121.7,105.1)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s16041" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s16043" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="5.6e-003" /> + <ns:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="334.39999" + y1="355.5" + x2="335.5" + y2="356.79999" + id="lg6381" + xlink:href="#lg4273_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(2.9,-1.7,1.7,2.9,-1557,-448.7)" /> + <linearGradient + x1="348.39999" + y1="247.39999" + x2="354.10001" + y2="242" + id="lg4271_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)"> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0" + id="s16025" /> + <stop + style="stop-color:#9e9e9e;stop-opacity:1" + offset="0.40000001" + id="s16027" /> + <stop + style="stop-color:black;stop-opacity:1" + offset="1" + id="s16029" /> + <ns:midPointStop + style="stop-color:#F2F2F2" + offset="0" /> + <ns:midPointStop + style="stop-color:#F2F2F2" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#000000" + offset="1" /> + </linearGradient> + <linearGradient + x1="351.29999" + y1="257.29999" + x2="346.29999" + y2="235.5" + id="lg4270_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ffff87;stop-opacity:1" + offset="0" + id="s16007" /> + <stop + style="stop-color:#ffad00;stop-opacity:1" + offset="1" + id="s16009" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0" /> + <ns:midPointStop + style="stop-color:#FFFF87" + offset="0.5" /> + <ns:midPointStop + style="stop-color:#FFAD00" + offset="1" /> + </linearGradient> + <linearGradient + x1="351.29999" + y1="257.29999" + x2="346.29999" + y2="235.5" + id="lg6459" + xlink:href="#lg4270_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(3.4,0,0,3.4,-1148,-802)" /> + <linearGradient + x1="43.799999" + y1="32.5" + x2="63.299999" + y2="66.400002" + id="XMLID_2708_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="stop75318" /> + <stop + style="stop-color:#fffcea;stop-opacity:1" + offset="1" + id="stop75320" /> + <a:midPointStop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointStop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointStop + style="stop-color:#FFFCEA" + offset="1" /> + </linearGradient> + <linearGradient + x1="43.799999" + y1="32.5" + x2="63.299999" + y2="66.400002" + id="lg1907" + xlink:href="#XMLID_2708_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)" /> + <linearGradient + x1="52.5" + y1="40.400002" + x2="58.200001" + y2="64" + id="XMLID_2707_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#ffdea0;stop-opacity:1" + offset="0" + id="stop75305" /> + <stop + style="stop-color:#ffd89e;stop-opacity:1" + offset="0.30000001" + id="stop75307" /> + <stop + style="stop-color:#ffd79e;stop-opacity:1" + offset="0.30000001" + id="stop75309" /> + <stop + style="stop-color:#dbaf6d;stop-opacity:1" + offset="0.69999999" + id="stop75311" /> + <stop + style="stop-color:#6f4c24;stop-opacity:1" + offset="1" + id="stop75313" /> + <a:midPointStop + style="stop-color:#FFDEA0" + offset="0" /> + <a:midPointStop + style="stop-color:#FFDEA0" + offset="0.6" /> + <a:midPointStop + style="stop-color:#FFD79E" + offset="0.3" /> + <a:midPointStop + style="stop-color:#FFD79E" + offset="0.5" /> + <a:midPointStop + style="stop-color:#DBAF6D" + offset="0.7" /> + <a:midPointStop + style="stop-color:#DBAF6D" + offset="0.5" /> + <a:midPointStop + style="stop-color:#6F4C24" + offset="1" /> + </linearGradient> + <linearGradient + x1="52.5" + y1="40.400002" + x2="58.200001" + y2="64" + id="lg1910" + xlink:href="#XMLID_2707_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)" /> + <linearGradient + x1="58" + y1="73.199997" + x2="44.5" + y2="19" + id="XMLID_2704_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)"> + <stop + style="stop-color:#d4a96c;stop-opacity:1" + offset="0.5" + id="stop75284" /> + <stop + style="stop-color:#dcb273;stop-opacity:1" + offset="0.60000002" + id="stop75286" /> + <stop + style="stop-color:#f0ca87;stop-opacity:1" + offset="0.80000001" + id="stop75288" /> + <stop + style="stop-color:#ffdc96;stop-opacity:1" + offset="0.69999999" + id="stop75290" /> + <stop + style="stop-color:#c18a42;stop-opacity:1" + offset="1" + id="stop75292" /> + <a:midPointStop + style="stop-color:#D4A96C" + offset="0.5" /> + <a:midPointStop + style="stop-color:#D4A96C" + offset="0.6" /> + <a:midPointStop + style="stop-color:#FFDC96" + offset="0.7" /> + <a:midPointStop + style="stop-color:#FFDC96" + offset="0.5" /> + <a:midPointStop + style="stop-color:#C18A42" + offset="1" /> + </linearGradient> + <linearGradient + x1="53.700001" + y1="32" + x2="53.700001" + y2="64.599998" + id="XMLID_2703_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e5c9b0;stop-opacity:1" + offset="0" + id="stop75268" /> + <stop + style="stop-color:#e5c9b0;stop-opacity:1" + offset="0.40000001" + id="stop75270" /> + <stop + style="stop-color:#c0aa94;stop-opacity:1" + offset="1" + id="stop75272" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0.5" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0.4" /> + <a:midPointStop + style="stop-color:#E5C9B0" + offset="0.5" /> + <a:midPointStop + style="stop-color:#C0AA94" + offset="1" /> + </linearGradient> + <linearGradient + x1="53.700001" + y1="32" + x2="53.700001" + y2="64.599998" + id="lg1916" + xlink:href="#XMLID_2703_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-29,-22.6)" /> + <linearGradient + x1="224.31" + y1="19.450001" + x2="214.33" + y2="11.46" + id="XMLID_419_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#404040;stop-opacity:1" + offset="0" + id="s1903" /> + <stop + style="stop-color:#6d6d6d;stop-opacity:1" + offset="0.33000001" + id="s1905" /> + <stop + style="stop-color:#e9e9e9;stop-opacity:1" + offset="1" + id="s1907" /> + <a:midPointStop + offset="0" + style="stop-color:#404040" /> + <a:midPointStop + offset="0.5" + style="stop-color:#404040" /> + <a:midPointStop + offset="0.33" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="0.5" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="1" + style="stop-color:#E9E9E9" /> + </linearGradient> + <linearGradient + x1="221.84" + y1="32.779999" + x2="212.2" + y2="20.27" + id="lg1988" + xlink:href="#XMLID_419_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> + <linearGradient + x1="228.35001" + y1="33.279999" + x2="215.42999" + y2="33.279999" + id="lg1900" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s1902" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="s1906" /> + <a:midPointStop + style="stop-color:#575757" + offset="0" /> + <a:midPointStop + style="stop-color:#575757" + offset="0.5" /> + <a:midPointStop + style="stop-color:#6D6D6D" + offset="0.33" /> + <a:midPointStop + style="stop-color:#6D6D6D" + offset="0.5" /> + <a:midPointStop + style="stop-color:#D3D3D3" + offset="1" /> + </linearGradient> + <linearGradient + x1="234.81" + y1="33.279999" + x2="228.27" + y2="33.279999" + id="lg1908" + xlink:href="#lg1900" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> + <linearGradient + x1="228.35001" + y1="33.279999" + x2="215.42999" + y2="33.279999" + id="XMLID_416_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#575757;stop-opacity:1" + offset="0" + id="s1874" /> + <stop + style="stop-color:#6d6d6d;stop-opacity:1" + offset="0.33000001" + id="s1876" /> + <stop + style="stop-color:#d3d3d3;stop-opacity:1" + offset="1" + id="s1878" /> + <a:midPointStop + offset="0" + style="stop-color:#575757" /> + <a:midPointStop + offset="0.5" + style="stop-color:#575757" /> + <a:midPointStop + offset="0.33" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="0.5" + style="stop-color:#6D6D6D" /> + <a:midPointStop + offset="1" + style="stop-color:#D3D3D3" /> + </linearGradient> + <linearGradient + x1="228.35001" + y1="33.279999" + x2="215.42999" + y2="33.279999" + id="lg1991" + xlink:href="#XMLID_416_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.33,0,0,1.31,-274.2,-5.2)" /> + <radialGradient + cx="603.19" + cy="230.77" + r="1.67" + fx="603.19" + fy="230.77" + id="x5010_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.1,0,0,1.1,-54.33,-75.4)"> + <stop + style="stop-color:#c9ffc9;stop-opacity:1" + offset="0" + id="stop29201" /> + <stop + style="stop-color:#23a11f;stop-opacity:1" + offset="1" + id="stop29203" /> + <a:midPointStop + offset="0" + style="stop-color:#C9FFC9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#C9FFC9" /> + <a:midPointStop + offset="1" + style="stop-color:#23A11F" /> + </radialGradient> + <radialGradient + cx="603.19" + cy="230.77" + r="1.67" + fx="603.19" + fy="230.77" + id="radialGradient5711" + xlink:href="#x5010_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.23,0,0,1.23,-709.93,-245.02)" /> + <linearGradient + x1="592.31" + y1="162.60001" + x2="609.32001" + y2="145.59" + id="lg5722" + xlink:href="#x5003_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="601.48999" + y1="170.16" + x2="613.84003" + y2="170.16" + id="x5002_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop29134" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="0.2" + id="stop29136" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="stop29138" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.20" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#FFFFFF" /> + <a:midPointStop + offset="1" + style="stop-color:#999999" /> + </linearGradient> + <linearGradient + x1="601.48999" + y1="170.16" + x2="613.84003" + y2="170.16" + id="lg5725" + xlink:href="#x5002_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.23" + id="x5004_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop29157" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop29159" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.23" + id="lg5728" + xlink:href="#x5004_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="592.31" + y1="162.60001" + x2="609.32001" + y2="145.59" + id="x5003_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0" + id="stop29143" /> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="1" + id="stop29145" /> + <a:midPointStop + offset="0" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="1" + style="stop-color:#E5E5E5" /> + </linearGradient> + <linearGradient + x1="592.31" + y1="162.60001" + x2="609.32001" + y2="145.59" + id="lg5732" + xlink:href="#x5003_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.24001" + id="x5000_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop29124" /> + <stop + style="stop-color:white;stop-opacity:1" + offset="1" + id="stop29126" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="1" + style="stop-color:#FFFFFF" /> + </linearGradient> + <linearGradient + x1="592.20001" + y1="156.45" + x2="609.98999" + y2="174.24001" + id="lg5735" + xlink:href="#x5000_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.12,0,0,1.12,-649.08,-160.62)" /> + <linearGradient + x1="308.54999" + y1="149.89999" + x2="299.72" + y2="148.83" + id="XMLID_2433_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d6d6d6;stop-opacity:1" + offset="0" + id="71615" /> + <stop + style="stop-color:#a5a5a5;stop-opacity:1" + offset="1" + id="71617" /> + <a:midPointStop + offset="0" + style="stop-color:#D6D6D6" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D6D6D6" /> + <a:midPointStop + offset="1" + style="stop-color:#A5A5A5" /> + </linearGradient> + <linearGradient + x1="308.54999" + y1="149.89999" + x2="299.72" + y2="148.83" + id="lg1952" + xlink:href="#XMLID_2433_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> + <radialGradient + cx="307.39999" + cy="121" + r="23.35" + fx="307.39999" + fy="121" + id="XMLID_2432_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.98,0,0,0.98,2.88,2.75)"> + <stop + style="stop-color:#d2d2d2;stop-opacity:1" + offset="0.19" + id="71592" /> + <stop + style="stop-color:#cfcfcf;stop-opacity:1" + offset="0.44999999" + id="71594" /> + <stop + style="stop-color:#c7c7c7;stop-opacity:1" + offset="0.60000002" + id="71596" /> + <stop + style="stop-color:#b9b9b9;stop-opacity:1" + offset="0.74000001" + id="71598" /> + <stop + style="stop-color:#a4a4a4;stop-opacity:1" + offset="0.86000001" + id="71600" /> + <stop + style="stop-color:#8a8a8a;stop-opacity:1" + offset="0.95999998" + id="71602" /> + <stop + style="stop-color:gray;stop-opacity:1" + offset="1" + id="71604" /> + <a:midPointStop + offset="0.19" + style="stop-color:#D2D2D2" /> + <a:midPointStop + offset="0.8" + style="stop-color:#D2D2D2" /> + <a:midPointStop + offset="1" + style="stop-color:#808080" /> + </radialGradient> + <radialGradient + cx="307.39999" + cy="121" + r="23.35" + fx="307.39999" + fy="121" + id="radialGradient2331" + xlink:href="#XMLID_2432_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-276.62,-121.54)" /> + <linearGradient + x1="294.13" + y1="127.07" + x2="294.13" + y2="142.2" + id="XMLID_2430_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#b5d8ff;stop-opacity:1" + offset="0" + id="71582" /> + <stop + style="stop-color:black;stop-opacity:1" + offset="1" + id="71584" /> + <a:midPointStop + offset="0" + style="stop-color:#B5D8FF" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B5D8FF" /> + <a:midPointStop + offset="1" + style="stop-color:#000000" /> + </linearGradient> + <linearGradient + x1="294.13" + y1="127.07" + x2="294.13" + y2="142.2" + id="lg2820" + xlink:href="#XMLID_2430_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> + <linearGradient + x1="279.10999" + y1="148.03" + x2="309.16" + y2="148.03" + id="XMLID_2429_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e1e1e1;stop-opacity:1" + offset="0" + id="71564" /> + <stop + style="stop-color:#e1e1e1;stop-opacity:1" + offset="0.25" + id="71566" /> + <stop + style="stop-color:#a5a5a5;stop-opacity:1" + offset="0.44" + id="71568" /> + <stop + style="stop-color:#a5a5a5;stop-opacity:1" + offset="1" + id="71570" /> + <a:midPointStop + offset="0" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.25" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E1E1E1" /> + <a:midPointStop + offset="0.44" + style="stop-color:#A5A5A5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#A5A5A5" /> + <a:midPointStop + offset="1" + style="stop-color:#A5A5A5" /> + </linearGradient> + <linearGradient + x1="279.10999" + y1="148.03" + x2="309.16" + y2="148.03" + id="lg2818" + xlink:href="#XMLID_2429_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.03,0,0,1.03,-279.57,-124.36)" /> + <radialGradient + cx="622.34302" + cy="14.449" + r="26.496" + fx="622.34302" + fy="14.449" + id="lg3499_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.851,0,0,0.849,69.297,51.658)"> + <stop + style="stop-color:#23468e;stop-opacity:1" + offset="0" + id="stop10972" /> + <stop + style="stop-color:#012859;stop-opacity:1" + offset="1" + id="stop10974" /> + <a:midPointStop + offset="0" + style="stop-color:#23468E" /> + <a:midPointStop + offset="0.5" + style="stop-color:#23468E" /> + <a:midPointStop + offset="1" + style="stop-color:#012859" /> + </radialGradient> + <radialGradient + cx="622.34302" + cy="14.449" + r="26.496" + fx="622.34302" + fy="14.449" + id="rg5791" + xlink:href="#lg3499_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.858,0,0,0.857,-511.7,9.02)" /> + <linearGradient + x1="616.112" + y1="76.247002" + x2="588.14099" + y2="60.742001" + id="lg3497_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#01326e;stop-opacity:1" + offset="0" + id="stop10962" /> + <stop + style="stop-color:#012859;stop-opacity:1" + offset="1" + id="stop10964" /> + <a:midPointStop + offset="0" + style="stop-color:#01326E" /> + <a:midPointStop + offset="0.5" + style="stop-color:#01326E" /> + <a:midPointStop + offset="1" + style="stop-color:#012859" /> + </linearGradient> + <linearGradient + x1="617.698" + y1="82.445999" + x2="585.95203" + y2="54.848999" + id="lg3496_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="stop10950" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop10952" /> + <a:midPointStop + offset="0" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="0.5" + style="stop-color:#E5E5E5" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="617.698" + y1="82.445999" + x2="585.95203" + y2="54.848999" + id="lg5794" + xlink:href="#lg3496_" + gradientUnits="userSpaceOnUse" /> + <linearGradient + x1="601.39001" + y1="55.341" + x2="588.29199" + y2="71.515999" + id="lg3495_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop10941" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.52200001" + id="stop10943" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop10945" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.522" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="601.39001" + y1="55.341" + x2="588.29199" + y2="71.515999" + id="lg5771" + xlink:href="#lg3495_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.009,0,0,1.009,-581.615,-43.098)" /> + <linearGradient + x1="611.34601" + y1="55.279999" + x2="590.39001" + y2="81.157997" + id="lg3494_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="stop10932" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.52200001" + id="stop10934" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="stop10936" /> + <a:midPointStop + offset="0" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.5" + style="stop-color:#D9D9D9" /> + <a:midPointStop + offset="0.522" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#F2F2F2" /> + <a:midPointStop + offset="1" + style="stop-color:#CCCCCC" /> + </linearGradient> + <linearGradient + x1="611.34601" + y1="55.279999" + x2="590.39001" + y2="81.157997" + id="lg5774" + xlink:href="#lg3494_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.009,0,0,1.009,-581.616,-43.098)" /> + <linearGradient + x1="798.72998" + y1="69.839996" + x2="799.04999" + y2="70.709999" + id="g3302_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#005e00;stop-opacity:1" + offset="0" + id="s6504" /> + <stop + style="stop-color:#23a11f;stop-opacity:1" + offset="1" + id="s6506" /> + <a:midPointstop + style="stop-color:#005E00" + offset="0" /> + <a:midPointstop + style="stop-color:#005E00" + offset="0.5" /> + <a:midPointstop + style="stop-color:#23A11F" + offset="1" /> + </linearGradient> + <linearGradient + x1="798.72998" + y1="69.839996" + x2="799.04999" + y2="70.709999" + id="lg5851" + xlink:href="#g3302_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> + <linearGradient + x1="779.19" + y1="122.73" + x2="811.69" + y2="149.74001" + id="g3301_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,129.19)"> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0" + id="s6483" /> + <stop + style="stop-color:#eee;stop-opacity:1" + offset="0.17" + id="s6485" /> + <stop + style="stop-color:#e3e3e3;stop-opacity:1" + offset="0.34" + id="s6487" /> + <stop + style="stop-color:#cfcfcf;stop-opacity:1" + offset="0.50999999" + id="s6489" /> + <stop + style="stop-color:#b4b4b4;stop-opacity:1" + offset="0.67000002" + id="s6491" /> + <stop + style="stop-color:#919191;stop-opacity:1" + offset="0.83999997" + id="s6493" /> + <stop + style="stop-color:#666;stop-opacity:1" + offset="1" + id="s6495" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.71" /> + <a:midPointstop + style="stop-color:#666666" + offset="1" /> + </linearGradient> + <linearGradient + x1="779.19" + y1="122.73" + x2="811.69" + y2="149.74001" + id="lg5855" + xlink:href="#g3301_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,103.123)" /> + <clipPath + id="g3299_"> + <use + id="use6469" + x="0" + y="0" + width="1005.92" + height="376.97" + xlink:href="#g101_" /> + </clipPath> + <radialGradient + cx="1189.9301" + cy="100.05" + r="40.400002" + fx="1189.9301" + fy="100.05" + id="g3300_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.34,-8.46e-2,0,0.34,394.16,137.13)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s6472" /> + <stop + style="stop-color:white;stop-opacity:0" + offset="1" + id="s6474" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointstop + style="stop-color:#000000" + offset="1" /> + </radialGradient> + <radialGradient + cx="1199.74" + cy="97.150002" + r="40.400002" + fx="1199.74" + fy="97.150002" + id="rg5860" + xlink:href="#g3300_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.409,-0.107,0,0.429,-451.489,113.149)" /> + <linearGradient + x1="796.38" + y1="67.580002" + x2="781.28003" + y2="58.549999" + id="g3298_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#4c8bca;stop-opacity:1" + offset="0" + id="s6462" /> + <stop + style="stop-color:#b7e9ff;stop-opacity:1" + offset="1" + id="s6464" /> + <a:midPointstop + style="stop-color:#4C8BCA" + offset="0" /> + <a:midPointstop + style="stop-color:#4C8BCA" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B7E9FF" + offset="1" /> + </linearGradient> + <linearGradient + x1="800.97998" + y1="140.72" + x2="777.71997" + y2="121.76" + id="g3297_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,129.19)"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="s6448" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s6450" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0.5" /> + <a:midPointstop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="800.97998" + y1="140.72" + x2="777.71997" + y2="121.76" + id="lg5890" + xlink:href="#g3297_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,129.19)" /> + <linearGradient + x1="790.03998" + y1="-16.33" + x2="779.84003" + y2="-3.73" + id="g3296_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(0,70.17)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="s6439" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.51999998" + id="s6441" /> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="1" + id="s6443" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0.5" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.52" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.5" /> + <a:midPointstop + style="stop-color:#CCCCCC" + offset="1" /> + </linearGradient> + <linearGradient + x1="790.03998" + y1="-16.33" + x2="779.84003" + y2="-3.73" + id="lg5866" + xlink:href="#g3296_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,28.6)" /> + <linearGradient + x1="785.84003" + y1="72.989998" + x2="785.26001" + y2="76.279999" + id="g3293_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s6412" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="1" + id="s6414" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointstop + style="stop-color:#737373" + offset="1" /> + </linearGradient> + <linearGradient + x1="785.84003" + y1="72.989998" + x2="785.26001" + y2="76.279999" + id="lg5871" + xlink:href="#g3293_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> + <linearGradient + x1="789.37" + y1="69.879997" + x2="791.03998" + y2="77.120003" + id="g3292_" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#999;stop-opacity:1" + offset="0" + id="s6403" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="0.28" + id="s6405" /> + <stop + style="stop-color:#666;stop-opacity:1" + offset="1" + id="s6407" /> + <a:midPointstop + style="stop-color:#999999" + offset="0" /> + <a:midPointstop + style="stop-color:#999999" + offset="0.5" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.28" /> + <a:midPointstop + style="stop-color:#F2F2F2" + offset="0.5" /> + <a:midPointstop + style="stop-color:#666666" + offset="1" /> + </linearGradient> + <linearGradient + x1="789.37" + y1="69.879997" + x2="791.03998" + y2="77.120003" + id="lg5874" + xlink:href="#g3292_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,0,0,1.263,-926.036,-60.001)" /> + <linearGradient + x1="786.65997" + y1="136.12" + x2="786.71002" + y2="134.33" + id="g3290_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1,-0.25,0,1,0,137.29)"> + <stop + style="stop-color:#d9d9d9;stop-opacity:1" + offset="0" + id="s6380" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="1" + id="s6382" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0" /> + <a:midPointstop + style="stop-color:#D9D9D9" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="1" /> + </linearGradient> + <linearGradient + x1="786.65997" + y1="136.12" + x2="786.71002" + y2="134.33" + id="lg5878" + xlink:href="#g3290_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(1.204,-0.316,0,1.263,-926.036,113.351)" /> + <radialGradient + cx="1458.77" + cy="-5.0999999" + r="35.130001" + fx="1458.77" + fy="-5.0999999" + id="g3289_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)"> + <stop + style="stop-color:white;stop-opacity:1" + offset="0" + id="s6371" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="s6373" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0" /> + <a:midPointstop + style="stop-color:#FFFFFF" + offset="0.5" /> + <a:midPointstop + style="stop-color:#999999" + offset="1" /> + </radialGradient> + <radialGradient + cx="1458.77" + cy="-5.0999999" + r="35.130001" + fx="1458.77" + fy="-5.0999999" + id="rg5881" + xlink:href="#g3289_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" /> + <radialGradient + cx="1612.98" + cy="-4.4699998" + r="36.580002" + fx="1612.98" + fy="-4.4699998" + id="g3288_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.34,0,0,0.36,238.56,86.87)"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="s6362" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0.63999999" + id="s6364" /> + <stop + style="stop-color:#737373;stop-opacity:1" + offset="1" + id="s6366" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.64" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.5" /> + <a:midPointstop + style="stop-color:#737373" + offset="1" /> + </radialGradient> + <radialGradient + cx="1612.98" + cy="-4.4699998" + r="36.580002" + fx="1612.98" + fy="-4.4699998" + id="rg5884" + xlink:href="#g3288_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.408,0,0,0.448,-638.943,49.495)" /> + <radialGradient + cx="1470.5" + cy="-10.21" + r="33.290001" + fx="1470.5" + fy="-10.21" + id="g3287_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.42,0,0,0.42,167.09,79.84)"> + <stop + style="stop-color:#e5e5e5;stop-opacity:1" + offset="0" + id="s6347" /> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0.38999999" + id="s6349" /> + <stop + style="stop-color:#b1b1b1;stop-opacity:1" + offset="0.75" + id="s6351" /> + <stop + style="stop-color:#aaa;stop-opacity:1" + offset="0.88" + id="s6353" /> + <stop + style="stop-color:#9e9e9e;stop-opacity:1" + offset="0.97000003" + id="s6355" /> + <stop + style="stop-color:#999;stop-opacity:1" + offset="1" + id="s6357" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0" /> + <a:midPointstop + style="stop-color:#E5E5E5" + offset="0.5" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.39" /> + <a:midPointstop + style="stop-color:#B2B2B2" + offset="0.87" /> + <a:midPointstop + style="stop-color:#999999" + offset="1" /> + </radialGradient> + <radialGradient + cx="1470.5" + cy="-10.21" + r="33.290001" + fx="1470.5" + fy="-10.21" + id="rg5887" + xlink:href="#g3287_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.505,0,0,0.53,-724.957,40.636)" /> + <pattern + patternTransform="matrix(0.592927,0,0,0.592927,78,462)" + id="cream-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-365.3146,-513.505)" + id="g3047"> + id="path2858" /> + <path + inkscape:label="#path2854" + sodipodi:nodetypes="czzzz" + style="fill:#e3dcc0" + id="path3060" + d="M 390.31462,529.50504 C 390.31462,534.47304 386.28262,538.50504 381.31462,538.50504 C 376.34662,538.50504 372.31462,534.47304 372.31462,529.50504 C 372.31462,524.53704 376.34662,520.50504 381.31462,520.50504 C 386.28262,520.50504 390.31462,524.53704 390.31462,529.50504 z " /> +</g> + </pattern> + <pattern + patternTransform="matrix(0.733751,0,0,0.733751,67,367)" + id="dark-cream-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-408.0946,-513.505)" + id="dark-cream-spot" + inkscape:label="#g3043"> + <path + sodipodi:nodetypes="czzzz" + style="fill:#c8c5ac" + d="M 433.09458,529.50504 C 433.09458,534.47304 429.06258,538.50504 424.09458,538.50504 C 419.12658,538.50504 415.09458,534.47304 415.09458,529.50504 C 415.09458,524.53704 419.12658,520.50504 424.09458,520.50504 C 429.06258,520.50504 433.09458,524.53704 433.09458,529.50504 z " + id="path2953" /> + </g> + </pattern> + <pattern + patternTransform="matrix(0.375,0,0,0.375,379,400)" + id="white-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-484.3997,-513.505)" + id="white-spot" + inkscape:label="#g3035"> + <path + style="opacity:0.25;fill:white" + id="path3033" + d="M 509.39967,529.50504 C 509.39967,534.47304 505.36767,538.50504 500.39967,538.50504 C 495.43167,538.50504 491.39967,534.47304 491.39967,529.50504 C 491.39967,524.53704 495.43167,520.50504 500.39967,520.50504 C 505.36767,520.50504 509.39967,524.53704 509.39967,529.50504 z " + sodipodi:nodetypes="czzzz" /> + </g> + </pattern> + <pattern + patternTransform="matrix(0.455007,0,0,0.455007,-5e-5,1.9e-5)" + id="black-spots" + height="32" + width="32" + patternUnits="userSpaceOnUse"> + <g + transform="translate(-448.3997,-513.505)" + id="black-spot" + inkscape:label="#g3039"> + <path + sodipodi:nodetypes="czzzz" + d="M 473.39967,529.50504 C 473.39967,534.47304 469.36767,538.50504 464.39967,538.50504 C 459.43167,538.50504 455.39967,534.47304 455.39967,529.50504 C 455.39967,524.53704 459.43167,520.50504 464.39967,520.50504 C 469.36767,520.50504 473.39967,524.53704 473.39967,529.50504 z " + id="path2961" + style="opacity:0.25;fill:black" /> + </g> + </pattern> + <linearGradient + x1="501.0903" + y1="-19.2544" + x2="531.85413" + y2="0.72390002" + id="linearGradient17334" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop17336" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop17338" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop17340" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop17342" /> + <a:midPointStop + offset="0" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.5112" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B4DAEA" /> + <a:midPointStop + offset="0.6461" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="1" + style="stop-color:#16336E" /> + </linearGradient> + <linearGradient + x1="415.73831" + y1="11.854" + x2="418.13361" + y2="18.8104" + id="linearGradient17426" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.8362,0.5206,-1.1904,0.992,147.62,-30.9374)"> + <stop + style="stop-color:#ccc;stop-opacity:1" + offset="0" + id="stop17428" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop17430" /> + <a:midPointStop + offset="0" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="0.5" + style="stop-color:#CCCCCC" /> + <a:midPointStop + offset="1" + style="stop-color:#F2F2F2" /> + </linearGradient> + <linearGradient + x1="478.21341" + y1="-131.9297" + x2="469.85818" + y2="-140.28481" + id="linearGradient17434" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.5592,0.829,-0.829,0.5592,101.3357,-104.791)"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop17436" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop17438" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop17440" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop17442" /> + <a:midPointStop + offset="0" + style="stop-color:#F3403F" /> + <a:midPointStop + offset="0.4213" + style="stop-color:#F3403F" /> + <a:midPointStop + offset="1" + style="stop-color:#A6100C" /> + </linearGradient> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17709" + xlink:href="#XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" /> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17711" + xlink:href="#XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="linearGradient17713" + xlink:href="#XMLID_1753_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17715" + xlink:href="#XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="500.70749" + y1="-13.2441" + x2="513.46442" + y2="-2.1547" + id="linearGradient17717" + xlink:href="#XMLID_1757_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="linearGradient17721" + xlink:href="#XMLID_2274_" + gradientUnits="userSpaceOnUse" /> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="linearGradient17723" + xlink:href="#XMLID_2275_" + gradientUnits="userSpaceOnUse" /> + <linearGradient + x1="500.70749" + y1="-13.2441" + x2="513.46442" + y2="-2.1547" + id="linearGradient17416" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop17418" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop17420" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <defs + id="defs9929"> + <path + d="M 489.21,209.35 L 485.35,203.63 C 483.63,204.25 473.47,208.93 471.5,210.18 C 470.57,210.77 470.17,211.16 469.72,212.48 C 470.93,212.31 471.72,212.49 473.42,213.04 C 473.26,214.77 473.24,215.74 473.57,218.2 C 474.01,216.88 474.41,216.49 475.34,215.9 C 477.33,214.65 487.49,209.97 489.21,209.35 z " + id="XMLID_960_" /> + </defs> + <clipPath + id="clipPath17448"> + <use + id="use17450" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_960_" /> + </clipPath> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="linearGradient17452" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop17454" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop17456" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop17458" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop17460" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="linearGradient17463" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#f3403f;stop-opacity:1" + offset="0" + id="stop17465" /> + <stop + style="stop-color:#d02a28;stop-opacity:1" + offset="0.37889999" + id="stop17467" /> + <stop + style="stop-color:#b21714;stop-opacity:1" + offset="0.77649999" + id="stop17469" /> + <stop + style="stop-color:#a6100c;stop-opacity:1" + offset="1" + id="stop17471" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0" /> + <a:midPointStop + style="stop-color:#F3403F" + offset="0.4213" /> + <a:midPointStop + style="stop-color:#A6100C" + offset="1" /> + </linearGradient> + <linearGradient + x1="481.23969" + y1="212.5742" + x2="472.92981" + y2="207.4967" + id="linearGradient17807" + xlink:href="#XMLID_2275_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-177.1654,35.43307)" /> + <linearGradient + x1="473.7681" + y1="209.17529" + x2="486.98099" + y2="213.2001" + id="linearGradient17810" + xlink:href="#XMLID_2274_" + gradientUnits="userSpaceOnUse" + gradientTransform="translate(-177.1654,35.43307)" /> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17812" + xlink:href="#XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)" /> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17814" + xlink:href="#XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="linearGradient17816" + xlink:href="#XMLID_1753_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17818" + xlink:href="#XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17347" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,11.0227,-35.6159)"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop17349" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop17351" /> + <a:midPointStop + offset="0" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="0.5" + style="stop-color:#5387BA" /> + <a:midPointStop + offset="1" + style="stop-color:#96BAD6" /> + </linearGradient> + <linearGradient + x1="516.57672" + y1="-15.769" + x2="516.57672" + y2="0.84280002" + id="linearGradient17379" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b2b2b2;stop-opacity:1" + offset="0" + id="stop17381" /> + <stop + style="stop-color:#f2f2f2;stop-opacity:1" + offset="1" + id="stop17383" /> + <a:midPointStop + offset="0" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="0.5" + style="stop-color:#B2B2B2" /> + <a:midPointStop + offset="1" + style="stop-color:#F2F2F2" /> + </linearGradient> + <linearGradient + x1="502.70749" + y1="115.3013" + x2="516.39001" + y2="127.1953" + id="linearGradient17862" + xlink:href="#XMLID_1749_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.9703,0.2419,-0.2419,0.9703,-166.1427,-0.18283)" /> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17864" + xlink:href="#XMLID_1756_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <defs + id="defs3859"> + <polygon + points="465.54,213.52 481.94,217.46 482.74,216.71 487.46,198.05 471.08,194.07 470.26,194.83 465.54,213.52 " + id="XMLID_343_" /> + </defs> + <linearGradient + x1="471.0806" + y1="201.07761" + x2="481.91711" + y2="210.4977" + id="linearGradient17389" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#6498c1;stop-opacity:1" + offset="0.005618" + id="stop17391" /> + <stop + style="stop-color:#79a9cc;stop-opacity:1" + offset="0.2332" + id="stop17393" /> + <stop + style="stop-color:#a4cde2;stop-opacity:1" + offset="0.74049997" + id="stop17395" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="1" + id="stop17397" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="5.618000e-003" /> + <a:midPointStop + style="stop-color:#6498C1" + offset="0.4438" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="1" /> + </linearGradient> + <clipPath + id="clipPath17400"> + <use + id="use17402" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_343_" /> + </clipPath> + <linearGradient + x1="505.62939" + y1="-14.9526" + x2="527.49402" + y2="-0.7536" + id="linearGradient17404" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop17406" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop17408" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop17410" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop17412" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17882" + xlink:href="#XMLID_1752_" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)" /> + <defs + id="defs3826"> + <polygon + points="463.52,216.14 480.56,220.24 481.36,219.5 483.03,202.04 469.05,196.69 468.24,197.45 463.52,216.14 " + id="XMLID_338_" /> + </defs> + <linearGradient + x1="468.2915" + y1="204.7612" + x2="479.39871" + y2="214.4166" + id="linearGradient17357" + gradientUnits="userSpaceOnUse"> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0" + id="stop17359" /> + <stop + style="stop-color:#96bad6;stop-opacity:1" + offset="1" + id="stop17361" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#96BAD6" + offset="1" /> + </linearGradient> + <clipPath + id="clipPath17364"> + <use + id="use17366" + x="0" + y="0" + width="744.09448" + height="600" + xlink:href="#XMLID_338_" /> + </clipPath> + <linearGradient + x1="506.09909" + y1="-11.5137" + x2="527.99609" + y2="2.7063999" + id="linearGradient17368" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.6868,0.4269,-0.9821,0.821,111.6149,-5.7901)"> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0" + id="stop17370" /> + <stop + style="stop-color:#b4daea;stop-opacity:1" + offset="0.51120001" + id="stop17372" /> + <stop + style="stop-color:#5387ba;stop-opacity:1" + offset="0.64609998" + id="stop17374" /> + <stop + style="stop-color:#16336e;stop-opacity:1" + offset="1" + id="stop17376" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5112" /> + <a:midPointStop + style="stop-color:#B4DAEA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.6461" /> + <a:midPointStop + style="stop-color:#5387BA" + offset="0.5" /> + <a:midPointStop + style="stop-color:#16336E" + offset="1" /> + </linearGradient> + <linearGradient + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" + id="linearGradient2387" + xlink:href="#linearGradient2381" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> + <linearGradient + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" + id="linearGradient5105" + xlink:href="#linearGradient2381" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> + <linearGradient + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" + id="linearGradient5145" + xlink:href="#linearGradient2381" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" /> + <linearGradient + inkscape:collect="always" + xlink:href="#linearGradient2381" + id="linearGradient2371" + gradientUnits="userSpaceOnUse" + gradientTransform="matrix(0.90776,0,0,0.90776,24.35648,49.24131)" + x1="296.4996" + y1="188.81061" + x2="317.32471" + y2="209.69398" /> + </defs> + <g + transform="matrix(0.437808,-0.437808,0.437808,0.437808,-220.8237,43.55311)" + id="g5089"> + <path + d="M 8.4382985,-6.28125 C 7.8309069,-6.28125 4.125,-0.33238729 4.125,1.96875 L 4.125,28.6875 C 4.125,29.533884 4.7068159,29.8125 5.28125,29.8125 L 30.84375,29.8125 C 31.476092,29.8125 31.968751,29.319842 31.96875,28.6875 L 31.96875,23.46875 L 32.25,23.46875 C 32.74684,23.46875 33.156249,23.059339 33.15625,22.5625 L 33.15625,-5.375 C 33.15625,-5.8718398 32.74684,-6.28125 32.25,-6.28125 L 8.4382985,-6.28125 z " + transform="translate(282.8327,227.1903)" + style="fill:#5c5c4f;stroke:black;stroke-width:3.23021388;stroke-miterlimit:4;stroke-dasharray:none" + id="path5091" /> + <rect + width="27.85074" + height="29.369793" + rx="1.1414107" + ry="1.1414107" + x="286.96509" + y="227.63805" + style="fill:#032c87" + id="rect5093" /> + <path + d="M 288.43262,225.43675 L 313.67442,225.43675 L 313.67442,254.80655 L 287.29827,254.83069 L 288.43262,225.43675 z " + style="fill:white" + id="rect5095" /> + <path + d="M 302.44536,251.73726 C 303.83227,259.59643 301.75225,263.02091 301.75225,263.02091 C 303.99609,261.41329 305.71651,259.54397 306.65747,257.28491 C 307.62455,259.47755 308.49041,261.71357 310.9319,263.27432 C 310.9319,263.27432 309.33686,256.07392 309.22047,251.73726 L 302.44536,251.73726 z " + style="fill:#a70000;fill-opacity:1;stroke-width:2" + id="path5097" /> + <rect + width="25.241802" + height="29.736675" + rx="0.89682275" + ry="0.89682275" + x="290.73544" + y="220.92249" + style="fill:#809cc9" + id="rect5099" /> + <path + d="M 576.47347,725.93939 L 582.84431,726.35441 L 583.25121,755.8725 C 581.35919,754.55465 576.39694,752.1117 574.98889,754.19149 L 574.98889,727.42397 C 574.98889,726.60151 575.65101,725.93939 576.47347,725.93939 z " + transform="matrix(0.499065,-0.866565,0,1,0,0)" + style="fill:#4573b3;fill-opacity:1" + id="rect5101" /> + <path + d="M 293.2599,221.89363 L 313.99908,221.89363 C 314.45009,221.89363 314.81318,222.25673 314.81318,222.70774 C 315.02865,229.0361 295.44494,244.47124 292.44579,240.30491 L 292.44579,222.70774 C 292.44579,222.25673 292.80889,221.89363 293.2599,221.89363 z " + style="opacity:0.65536726;fill:url(#linearGradient2371);fill-opacity:1" + id="path5103" /> + </g> +</svg> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/master.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/master.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/en-US/master.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,41 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.3CR3//EN" +"http://www.oasis-open.org/docbook/xml/4.3CR3/docbookx.dtd" + +[<!ENTITY Overview SYSTEM "Overview.xml"> +<!ENTITY NewFeatures SYSTEM "New_Features.xml"> +<!ENTITY ComponentVersions SYSTEM "Component_Versions.xml"> +<!ENTITY FixedIssues SYSTEM "Fixed_Issues.xml"> +<!ENTITY KnownIssues SYSTEM "Known_Issues.xml"> +]> + +<article> + + <articleinfo> + <title>Release Notes</title> + + + <author> + <firstname>Isaac</firstname> + <surname>Rooskov</surname> + <email>irooskov(a)redhat.com</email> + </author> + <copyright> + <year>2011</year> + <holder>JBoss by Red Hat</holder> + </copyright> + <releaseinfo> + Version: 3.2.1.GA + </releaseinfo> + + + </articleinfo> + + <toc/> + &Overview; +  + &ComponentVersions; + &FixedIssues; + + +</article> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/pom.xml =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/pom.xml (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/pom.xml 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,239 @@ +<?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"> + + <modelVersion>4.0.0</modelVersion> + <groupId>org.jboss.tools</groupId> + <artifactId>${docname}-${translation}</artifactId> + <version>1.0</version> + <packaging>jdocbook</packaging> + <name>${bookname}-(${translation})</name> + + <properties> + <translation>en-US</translation> + <docname>Release_Notes</docname> + <bookname>Release Notes</bookname> + </properties> + + <profiles> + +  + <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> + +  + <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> + +  + <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> + +  + <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> + +  + <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> +  + <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> Added: branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/publican.cfg =================================================================== --- branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/publican.cfg (rev 0) +++ branches/jbosstools-3.2.x/documentation/guides/JBDS_Release_Notes/publican.cfg 2011-07-18 01:46:34 UTC (rev 32971) @@ -0,0 +1,7 @@ +# Config::Simple 4.59 +# Mon Dec 21 12:14:29 2009 + +xml_lang: en-US +type: Article +brand: JBoss +

14 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits July 2011