January 2011 - jbosstools-commits

JBoss Tools SVN: r28433 - trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/preferences.

by jbosstools-commits＠lists.jboss.org

Author: dvinnichek Date: 2011-01-20 07:11:40 -0500 (Thu, 20 Jan 2011) New Revision: 28433 Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/preferences/TemplatesPreferencePage.java Log: fixed diabling/enabling for buttons on Visual Page Editor Preferences page (https://issues.jboss.org/browse/JBIDE-8141) Modified: trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/preferences/TemplatesPreferencePage.java =================================================================== --- trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/preferences/TemplatesPreferencePage.java 2011-01-20 06:50:09 UTC (rev 28432) +++ trunk/vpe/plugins/org.jboss.tools.vpe/src/org/jboss/tools/vpe/editor/preferences/TemplatesPreferencePage.java 2011-01-20 12:11:40 UTC (rev 28433) @@ -10,22 +10,12 @@ ******************************************************************************/ package org.jboss.tools.vpe.editor.preferences; -import java.util.ArrayList; -import java.util.Collections; -import java.util.Comparator; -import java.util.HashMap; import java.util.List; -import java.util.Map; -import java.util.Set; -import java.util.TreeMap; -import java.util.TreeSet; - import org.eclipse.jface.preference.PreferencePage; import org.eclipse.jface.viewers.ColumnLayoutData; import org.eclipse.jface.viewers.ColumnWeightData; import org.eclipse.jface.viewers.TableLayout; import org.eclipse.swt.SWT; -import org.eclipse.swt.SWTException; import org.eclipse.swt.layout.GridData; import org.eclipse.swt.layout.GridLayout; import org.eclipse.swt.widgets.Button; @@ -35,7 +25,6 @@ import org.eclipse.swt.widgets.Listener; import org.eclipse.swt.widgets.Table; import org.eclipse.swt.widgets.TableColumn; -import org.eclipse.swt.widgets.TableItem; import org.eclipse.swt.widgets.Widget; import org.eclipse.ui.IWorkbench; import org.eclipse.ui.IWorkbenchPreferencePage; @@ -117,7 +106,19 @@ /* * Fill the table with stored tags */ - VpeImportExportWizardsUtils.updateTagsTable(tagsTable, tagsList, true); + VpeImportExportWizardsUtils.updateTagsTable(tagsTable, tagsList, true); + + /* + * Add selection listener to the table + */ + Listener tableItemSelectionListener = new Listener() { + @Override + public void handleEvent(Event event) { + editButton.setEnabled(true); + removeButton.setEnabled(true); + } + }; + tagsTable.addListener(SWT.Selection, tableItemSelectionListener); /* * Add buttons @@ -142,6 +143,8 @@ importButton.setLayoutData(new GridData(SWT.FILL, SWT.TOP, false, false, 1, 1)); importButton.setText(VpeUIMessages.TemplatesPreferencePage_Import); + evaluateButtonsEnabling(); + /* * Adding event listeners to the buttons */ @@ -175,6 +178,7 @@ */ tagsList.add(data); tagListWasChanged = true; + evaluateButtonsEnabling(); } } else if (source == editButton) { /* @@ -206,9 +210,13 @@ tagsTable.remove(selectIndex); tagsList.remove(selectIndex); tagListWasChanged = true; + if (selectIndex == 0 && !tagsList.isEmpty()) { + tagsTable.setSelection(selectIndex); + } if (selectIndex > 0) { tagsTable.setSelection(selectIndex - 1); } + evaluateButtonsEnabling(); } } else if (source == exportButton) { /* @@ -230,6 +238,7 @@ * Re-initialize tags list from the file */ tagsList.addAll(dlg.getImportedList()); + evaluateButtonsEnabling(); } else { /* * Handle default event @@ -276,5 +285,24 @@ VpeImportExportWizardsUtils.updateTagsTable(tagsTable, tagsList, true); } - + private void evaluateButtonsEnabling() { + + boolean editButtonEnabling = false; + boolean removeButtonEnabling = false; + boolean exportButtonEnabling = false; + + if (!tagsList.isEmpty()) { + + exportButtonEnabling = true; + + if (tagsTable.getSelection().length != 0) { + editButtonEnabling = true; + removeButtonEnabling = true; + } + } + + editButton.setEnabled(editButtonEnabling); + removeButton.setEnabled(removeButtonEnabling); + exportButton.setEnabled(exportButtonEnabling); + } }

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28432 - trunk/hibernatetools/docs/reference/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-20 01:50:09 -0500 (Thu, 20 Jan 2011) New Revision: 28432 Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml trunk/hibernatetools/docs/reference/en-US/setup.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-20 06:39:33 UTC (rev 28431) +++ trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-20 06:50:09 UTC (rev 28432) @@ -89,7 +89,7 @@ <guimenuitem>New</guimenuitem> <guimenuitem>File</guimenuitem> <guimenuitem>Hibernate Configuration 3.0</guimenuitem> - </menuchoice>. After selecting the wanted location for the <filename>hibernate.cfg.xml</filename> file, you will see the following page:</para> + </menuchoice>. After selecting the desired location for the <filename>hibernate.cfg.xml</filename> file, you will see the following page:</para> <figure> <title>Hibernate Configuration File Wizard</title> <mediaobject> @@ -103,49 +103,39 @@ </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> + <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 <filename>hibernate.cfg.xml</filename> file 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 <filename>hibernate.cfg.xml</filename> file for the basis of a Console configuration.</para> + <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> 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, 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> + <para> + A Console configuration describes how the <property>Hibernate plugin</property> should configure <property>Hibernate</property> and what configuration files, including which 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 by your project. + </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> + <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 and auto-detect the - settings which you then can just approve or modify to suit your needs.</para> + <para> + The wizard will look at the current selection in the IDE and try to auto-detect the appropriate 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> + <guilabel>Main</guilabel> for the basic and required settings</para> </listitem> </itemizedlist> <figure> @@ -159,10 +149,9 @@ </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> + <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"> @@ -199,9 +188,9 @@ <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> + <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> @@ -212,8 +201,7 @@ <para>Project</para> </entry> <entry> - <para>The name of a java project which classpath should be used in the console - configuration</para> + <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> @@ -224,9 +212,9 @@ <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> + <para> + DTP provided connection that you can use instead of what is defined in the <filename>cfg.xml</filename> and <filename>jpa 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> @@ -237,10 +225,10 @@ <para>Property file</para> </entry> <entry> - <para>Path to a hibernate.properties file</para> + <para>Path to a <filename>hibernate.properties</filename> file</para> </entry> <entry> - <para>First hibernate.properties file found in the selected project</para> + <para>First <filename>hibernate.properties</filename> file found in the selected project</para> </entry> </row> <row> @@ -248,10 +236,10 @@ <para>Configuration file</para> </entry> <entry> - <para>Path to a hibernate.cfg.xml file</para> + <para>Path to a <filename>hibernate.cfg.xml</filename> file</para> </entry> <entry> - <para>First hibernate.cfg.xml file found in the selected project</para> + <para>First <filename>hibernate.cfg.xml</filename> file found in the selected project</para> </entry> </row> <row> @@ -262,8 +250,9 @@ <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> + <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> @@ -271,16 +260,8 @@ </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> + <para> + The two latter settings are usually not required if you specify a project and it has a <filename> /hibernate.cfg.xml </filename> or <filename>/META-INF/persistence.xml</filename> file in the projects classpath.</para> </note> <itemizedlist> <listitem> @@ -298,10 +279,7 @@ </imageobject> </mediaobject> </figure> - <para>The next table describes Hibernate Console Configuration options available on the - <emphasis> - <property>Options</property> - </emphasis> tab.</para> + <para>The next table describes Hibernate Console Configuration options available on the <guilabel>Options</guilabel> tab.</para> <table> <title>Hibernate Console Configuration Options</title> <tgroup cols="3"> Modified: trunk/hibernatetools/docs/reference/en-US/setup.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/setup.xml 2011-01-20 06:39:33 UTC (rev 28431) +++ trunk/hibernatetools/docs/reference/en-US/setup.xml 2011-01-20 06:50:09 UTC (rev 28432) @@ -71,7 +71,7 @@ </listitem> <listitem> - <para>Unpack <property>Hibernate Tools</property> in <filename>eclipse/dropins</filename> folder</para> + <para>Unpack <property>Hibernate Tools</property> in the <filename>eclipse/dropins</filename> folder</para> </listitem> </itemizedlist> <note>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28431 - trunk/hibernatetools/docs/reference/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-20 01:39:33 -0500 (Thu, 20 Jan 2011) New Revision: 28431 Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml trunk/hibernatetools/docs/reference/en-US/setup.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-20 06:22:06 UTC (rev 28430) +++ trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-20 06:39:33 UTC (rev 28431) @@ -1,49 +1,47 @@ <?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> + <para> + This chapter will introduce you to the set of wizards and editors that <property>Hibernate Tools</property> provide within Eclipse for simplifying 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"/> to find all benefits that you - can take advantage of while using the tools within Eclipse.</para> + <para> + Hibernate Eclipse Tools include wizards for creating Hibernate mapping files, configuration files (<filename>.cfg.xml</filename>), <filename>revenge.xml</filename> files 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"/> to find all 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 functionality of <property>Hibernate</property>. The tools make working with <property>Hibernate</property> easier, - but you are still encouraged 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> + <para> + Please note that these tools do not try to hide any functionality of <property>Hibernate</property>; rather the tools make working with <property>Hibernate</property> easier. You are still encouraged 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> + 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>Also you need start the <ulink url="http://docs.jboss.org/tools/resources/GSG_database.zip">database</ulink>.</para> <note> <title>Note:</title> - <para>How to run database is documented in the <ulink url="http://docs.jboss.org/tools/3.0.1.GA/en/GettingStartedGuide/html/first_se...">Getting Started Guide</ulink>.</para> + <para>The stes for running the database are documented in the <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 <filename>.hbm.xml</filename> files, Hibernate Tools provide a basic wizard which you can bring up selecting <menuchoice><guimenuitem>New</guimenuitem> + <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 bring up selecting <menuchoice><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'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> + </menuchoice>. + </para> + <para> + At first you will be asked to select a package or multiple individual classes to map. It's also possible to create an empty file: do not select any packages or classes and an empty <filename>.hbm</filename> 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> @@ -52,9 +50,9 @@ </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> + <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> @@ -63,7 +61,7 @@ </imageobject> </mediaobject> </figure> - <para>This wizard page outputs a generated .hbm files preview.</para> + <para>This wizard page outputs a generated <filename>.hbm</filename> files preview.</para> <figure> <title>Preview Generated Mapping Files</title> <mediaobject> @@ -72,17 +70,18 @@ </imageobject> </mediaobject> </figure> - <para>Pressing <property>Finish</property> creates the files.</para> + <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 reverse engineer, 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. The <property>Hibernate Tools</property> provide a wizard for - generating the <filename>hibernate.cfg.xml</filename> file if you do not already have such one.</para> + <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>New</guimenuitem> <guimenuitem>Other</guimenuitem> </menuchoice> (<keycombo><keycap>Ctrl</keycap> <keycap>N</keycap> - </keycombo>), then + </keycombo>), then select <menuchoice><guimenuitem>Hibernate</guimenuitem> <guimenuitem>Hibernate Configuration File (cfg.xml)</guimenuitem> @@ -528,7 +527,9 @@ <itemizedlist> <listitem> <para> - Right-click on the configuration in <menuchoice><guimenuitem>Hibernate Configurations View</guimenuitem><guimenuitem>Edit Configuration</guimenuitem></menuchoice> or just double-click on <property>Console Configuration</property> + Right-click on the configuration in <menuchoice><guimenuitem>Hibernate Configurations View</guimenuitem> + <guimenuitem>Edit Configuration</guimenuitem> + </menuchoice> or just double-click on <property>Console Configuration</property> item. </para> <figure> @@ -540,7 +541,8 @@ </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"/>. + 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> @@ -686,7 +688,9 @@ already existing Hibernate configuration, be that mapping files or annotated classes. Some of these are POJO Java source file, Hibernate <filename>.hbm.xml</filename>, <filename>hibernate.cfg.xml</filename> 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 <menuchoice><guimenuitem>Run</guimenuitem><guimenuitem>Hibernate Code Generation</guimenuitem></menuchoice> menu item. + 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 <menuchoice><guimenuitem>Run</guimenuitem> + <guimenuitem>Hibernate Code Generation</guimenuitem> + </menuchoice> menu item. </para> <section id="code_gen"> <title>Code Generation Launcher</title> @@ -1269,7 +1273,9 @@ 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 <menuchoice><guimenuitem>Open With</guimenuitem><guimenuitem>Hibernate 3.0 XML Editor</guimenuitem></menuchoice> option from the context menu of the file. The editor should look as follows: + To open any mapping file in the editor, choose <menuchoice><guimenuitem>Open With</guimenuitem> + <guimenuitem>Hibernate 3.0 XML Editor</guimenuitem> + </menuchoice> option from the context menu of the file. The editor should look as follows: </para> <figure> <title>Structured hbm.xml Editor</title> @@ -1279,7 +1285,9 @@ </imageobject> </mediaobject> </figure> - <para>For the configuration file you should choose <menuchoice><guimenuitem>Open With</guimenuitem><guimenuitem>Hibernate Configuration 3.0 XML Editor</guimenuitem></menuchoice> option.</para> + <para>For the configuration file you should choose <menuchoice><guimenuitem>Open With</guimenuitem> + <guimenuitem>Hibernate Configuration 3.0 XML Editor</guimenuitem> + </menuchoice> option.</para> <figure> <title>Structured cfg.xml Editor</title> <mediaobject> @@ -1309,7 +1317,9 @@ </figure> <para>In the <emphasis> <property>Name</property> - </emphasis> field press <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> to invoke the content assist. It will suggest <emphasis> + </emphasis> field press <keycombo><keycap>Ctrl</keycap> + <keycap>Space</keycap> + </keycombo> 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> @@ -1367,7 +1377,11 @@ is there. To understand the full flexibility of the <filename>reveng.xml</filename>, please see <xref linkend="hibernaterevengxmlfile"/> </para> </note> - <para>The editor is activated as soon as an <filename>.reveng.xml </filename> file is opened. To get an initial <filename>reveng.xml </filename> file the <property>Reverse Engineering File Wizard</property> can be started via <keycombo><keycap>Ctrl</keycap><keycap>N</keycap></keycombo> and <menuchoice><guimenuitem>Hibernate</guimenuitem><guimenuitem>Hibernate Reverse Engineering File (reveng.xml)</guimenuitem></menuchoice> then.</para> + <para>The editor is activated as soon as an <filename>.reveng.xml </filename> file is opened. To get an initial <filename>reveng.xml </filename> file the <property>Reverse Engineering File Wizard</property> can be started via <keycombo><keycap>Ctrl</keycap> + <keycap>N</keycap> + </keycombo> and <menuchoice><guimenuitem>Hibernate</guimenuitem> + <guimenuitem>Hibernate Reverse Engineering File (reveng.xml)</guimenuitem> + </menuchoice> then.</para> <figure> <title>ChooseReverse Engineering File Wizard </title> <mediaobject> @@ -1800,7 +1814,13 @@ <para>Scroll the diagram content</para> </entry> <entry> - <para><keycombo><keycap>Ctrl</keycap><keycap>Shift</keycap><keycap>arrows</keycap></keycombo></para> + <para> + <keycombo> + <keycap>Ctrl</keycap> + <keycap>Shift</keycap> + <keycap>arrows</keycap> + </keycombo> + </para> </entry> </row> <row> @@ -1808,7 +1828,9 @@ <para>Collapse/Expand selected item(s)</para> </entry> <entry> - <para> <keycap>Enter</keycap> </para> + <para> + <keycap>Enter</keycap> + </para> </entry> </row> <row> @@ -1816,7 +1838,9 @@ <para>Show/Hide selected item(s)</para> </entry> <entry> - <para> <keycap>+</keycap> </para> + <para> + <keycap>+</keycap> + </para> </entry> </row> <row> @@ -1824,7 +1848,9 @@ <para>Sort items in alphabetical order or return the initial state</para> </entry> <entry> - <para><keycap>Space</keycap></para> + <para> + <keycap>Space</keycap> + </para> </entry> </row> <row> @@ -1832,13 +1858,17 @@ <para>Navigate between the items</para> </entry> <entry> - <para><keycap>Arrows</keycap></para> + <para> + <keycap>Arrows</keycap> + </para> </entry> </row> </tbody> </tgroup> </table> - <para>It's possible to save the diagram in the eclipse workspace. Click the usual <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>Save As</guimenuitem></menuchoice> option, the wizard will ask you to set the location within you project where + <para>It's possible to save the diagram in the eclipse workspace. Click the usual <menuchoice><guimenuitem>File</guimenuitem> + <guimenuitem>Save As</guimenuitem> + </menuchoice> 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> @@ -2018,7 +2048,9 @@ <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 <keycombo><keycap>Ctrl</keycap><keycap>Enter</keycap></keycombo>.</para> + 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 project <property>Console @@ -2062,7 +2094,10 @@ </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 (<keycombo><keycap>Ctrl</keycap><keycap>1</keycap></keycombo>). + 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 (<keycombo><keycap>Ctrl</keycap> + <keycap>1</keycap> + </keycombo>). </para> <figure> <title>Quick Fix Option Demonstration</title> @@ -2093,7 +2128,9 @@ </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 <menuchoice><guimenuitem>Property View</guimenuitem><guimenuitem>Tab name field</guimenuitem></menuchoice>. </para> + Click the tab, and type a new name in <menuchoice><guimenuitem>Property View</guimenuitem> + <guimenuitem>Tab name field</guimenuitem> + </menuchoice>. </para> <figure> <title>Tab Renaming</title> <mediaobject> @@ -2249,7 +2286,9 @@ Annotations Documentation</ulink> .</para> </note> <para> - To open this wizard you should right click the class you want to enrich with annotations and select <menuchoice><guimenuitem>Source</guimenuitem><guimenuitem>Generate Hibernate/JPA annotations</guimenuitem></menuchoice>. You will see the Hibernate:add JPA annotations dialog. + To open this wizard you should right click the class you want to enrich with annotations and select <menuchoice><guimenuitem>Source</guimenuitem> + <guimenuitem>Generate Hibernate/JPA annotations</guimenuitem> + </menuchoice>. You will see the Hibernate:add JPA annotations dialog. </para> <figure> <title>Starting Hibernate:add JPA annotations dialog</title> @@ -2365,7 +2404,13 @@ <section id="jpa_project_with_hibernate"> <title>Creating JPA project with Hibernate support</title> <para>When starting a new JPA project from - <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 <property>JPA Perspective</property>), the first wizard page looks as + <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 <property>JPA Perspective</property>), the first wizard page looks as follows.</para> <figure> <title>Starting JPA Project</title> @@ -2399,8 +2444,10 @@ <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 <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> + For that find <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> Modified: trunk/hibernatetools/docs/reference/en-US/setup.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/setup.xml 2011-01-20 06:22:06 UTC (rev 28430) +++ trunk/hibernatetools/docs/reference/en-US/setup.xml 2011-01-20 06:39:33 UTC (rev 28431) @@ -1,115 +1,98 @@ <?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> + <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 the case with <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.2.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 the <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> + + </listitem> + <listitem> + <para>Unpack <property>Hibernate Tools</property> in <filename>eclipse/dropins</filename> 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 the use of 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 has not always 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 <filename>hibernate-tools.jar</filename> 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 <filename>/plugins/org.hibernate.eclipse.x.x.x/lib/tools/</filename>. 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> </chapter>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28430 - trunk/hibernatetools/docs/reference/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-20 01:22:06 -0500 (Thu, 20 Jan 2011) New Revision: 28430 Modified: trunk/hibernatetools/docs/reference/en-US/introduction.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/introduction.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/introduction.xml 2011-01-20 06:14:39 UTC (rev 28429) +++ trunk/hibernatetools/docs/reference/en-US/introduction.xml 2011-01-20 06:22:06 UTC (rev 28430) @@ -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 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 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 of <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 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> - <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 Hibernate Eclipse tools to quickly create common Hibernate files such as configuration (<filename>cfg.xml</filename>) files, mapping files and <filename>revenge.xml</filename> 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> - <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> + 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 <filename>reveng.xml</filename> 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>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 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>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 structure of entities and 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> + 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> - </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> + 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> </chapter>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28429 - trunk/hibernatetools/docs/reference/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-20 01:14:39 -0500 (Thu, 20 Jan 2011) New Revision: 28429 Modified: trunk/hibernatetools/docs/reference/en-US/ant.xml trunk/hibernatetools/docs/reference/en-US/plugins.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/ant.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/ant.xml 2011-01-20 05:24:46 UTC (rev 28428) +++ trunk/hibernatetools/docs/reference/en-US/ant.xml 2011-01-20 06:14:39 UTC (rev 28429) @@ -8,22 +8,18 @@ <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 + <para>The <filename>hibernate-tools.jar</filename> 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> + from tools.hibernate.org. The <filename>hibernate-tools.jar</filename> 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 + <para>There might be incompatibilities with respect to the <filename>Hibernate3.jar</filename> 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 + <filename>hibernate3.jar</filename> and <filename>hibernate-annotations.jar</filename> 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> </note> @@ -34,10 +30,8 @@ <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> + </emphasis> task defined. That is done in your <filename>build.xml</filename> by inserting the following xml (assuming the jars are in the + <filename>lib</filename> directory): </para> <programlisting role="XML"><![CDATA[<path id="toolslib"> <path location="lib/hibernate-tools.jar" /> @@ -55,9 +49,7 @@ <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> + </emphasis> which now can be used anywhere in your ant <filename>build.xml</filename> files. It is important to include all the <property>Hibernate Tools</property> dependencies as well as the jdbc driver.</para> <para>Notice that to use the annotation based Configuration you must <ulink @@ -203,10 +195,8 @@ <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> + <filename>hibernate.cfg.xml</filename> + </property>. </emphasis> The output will be put in the <filename>${build.dir}/generated</filename> directory.</para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> <classpath> @@ -220,13 +210,7 @@ <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 + and finally runs a custom code generation via <code><hbmtemplate></code>. This is again from a normal <filename>hibernate.cfg.xml</filename> and the output is still put in the <filename>${build.dir}/generated</filename> 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> @@ -278,9 +262,7 @@ <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> + configuration reads the mappings from a <filename>cfg.xml</filename> and/or a fileset.</para> <programlisting role="XML"><![CDATA[<configuration configurationfile="hibernate.cfg.xml" @@ -382,7 +364,7 @@ <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 + 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> @@ -399,13 +381,7 @@ <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> exists, and a <filename> hibernate.properties </filename> and fileset is used instead. </para> <note> <title>Note:</title> @@ -473,16 +449,12 @@ <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> + 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> 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> + classpath, e.g. look for <filename>META-INF/persistence.xml</filename>.</para> <para>The <emphasis> <property>persistenceunit</property> @@ -535,11 +507,7 @@ <para>A <code><jdbcconfiguration></code> is used to perform reverse engineering of the 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 <filename>hibernate.cfg.xml</filename> or <filename>hibernate.properties</filename> with a fileset.</para> <para>The <code><jdbcconfiguration></code> has the same attributes as a <code><configuration></code> @@ -616,7 +584,7 @@ <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 + addition to) a <filename>reveng.xml</filename> file gives you full programmatic control of the reverse engineering.</para> </entry> @@ -668,10 +636,7 @@ <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> + is read from a <filename> hibernate.properties </filename> file but could just as well have been read from a <filename>hibernate.cfg.xml</filename></para> <programlisting role="XML"><![CDATA[<hibernatetool> <jdbcconfiguration propertyfile="etc/hibernate.properties" /> @@ -861,8 +826,7 @@ <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> + 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"/> @@ -957,8 +921,7 @@ <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> + configuration. e.g. to convert from annotation based pojo's to <filename>hbm.xml</filename>.</para> <note> <title>Note:</title> @@ -999,8 +962,7 @@ <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> + <para><code><hbm2cfgxml></code> generates a <filename>hibernate.cfg.xml</filename>. 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> @@ -1039,7 +1001,7 @@ </entry> <entry> - <para>The generated cfg.xml will have <mapping class=".."/>, opposed + <para>The generated <filename>cfg.xml</filename> will have <mapping class=".."/>, opposed to <mapping resource="..."/> for each mapping.</para> </entry> @@ -1094,8 +1056,7 @@ </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> + In this example we also let the output be dumped to <filename>queryresult.txt</filename>.</para> <note> <title>Note:</title> Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-20 05:24:46 UTC (rev 28428) +++ trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-20 06:14:39 UTC (rev 28429) @@ -1,2674 +1,2546 @@ <?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 + <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, + <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 + HQL and Criteria queries are also provided in Hibernate Console. Refer to <xref linkend="hibernate_key_features"/> 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 + <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 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 + </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 is documented in the <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. + <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 bring up selecting <menuchoice><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'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 + <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 + <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 + <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 <filename>hibernate.properties</filename> or <filename>hibernate.cfg.xml</filename> file is needed. The <property>Hibernate Tools</property> provide a wizard for + generating the <filename>hibernate.cfg.xml</filename> file if you do not already have such one.</para> + <para>Start the wizard by clicking <menuchoice><guimenuitem>New</guimenuitem> + <guimenuitem>Other</guimenuitem> + </menuchoice> (<keycombo><keycap>Ctrl</keycap> + <keycap>N</keycap> + </keycombo>), then + + <menuchoice><guimenuitem>Hibernate</guimenuitem> + <guimenuitem>Hibernate Configuration File (cfg.xml)</guimenuitem> + </menuchoice> and click the <guibutton>Next</guibutton> button or on a web Seam project in the <property>Web Projects</property> select <menuchoice><guimenuitem>WebContent</guimenuitem> + <guimenuitem>New</guimenuitem> + <guimenuitem>File</guimenuitem> + <guimenuitem>Hibernate Configuration 3.0</guimenuitem> + </menuchoice>. After selecting the wanted location for the <filename>hibernate.cfg.xml</filename> 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 + </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> + <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> + </emphasis> to create the configuration file, after optionally creating a Console + configuration, the <filename>hibernate.cfg.xml</filename> file 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 + </emphasis> 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, 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 + <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> + </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 + </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> + </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 + </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". + <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 + </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 + </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 + </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 + </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> + </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 + </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 + </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 + </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 + </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 + </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 + </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 + </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 + <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> + </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 + </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 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 2 ways: </para> + <itemizedlist> + <listitem> + <para> + Right-click on the configuration in <menuchoice><guimenuitem>Hibernate Configurations View</guimenuitem><guimenuitem>Edit Configuration</guimenuitem></menuchoice> 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 + <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 <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 <filename>cfg.xml</filename> and jpa <filename>persistence.xml</filename>. 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 <guilabel>Hibernate Console Configuration</guilabel> you need do right-click + your configuration and choose <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>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 + </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, + these are POJO Java source file, Hibernate <filename>.hbm.xml</filename>, <filename>hibernate.cfg.xml</filename> 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 <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 <guimenuitem>Open Hibernate Code Generation Dialog...</guimenuitem> 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 + <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 + </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> + </note> + <para> + The dialog also have the standard tabs <guilabel>Refresh</guilabel> and <guilabel>Common</guilabel> 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 + </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 + </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 - <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 available via the + </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 + </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 + </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. 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 + process. Clicking "setup" 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 <filename>reveng.xml</filename> 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 + </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. + </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. + </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) + </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 + <filename>hbm.xml</filename> 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 + </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> + </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 + </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 + <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 + <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 + </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> 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 + </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 + </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 + </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> + </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 + </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 + <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 + </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 + </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 + </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 + </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 + </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 <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 + </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 <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 + </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 + <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 + possible to navigate from the <filename>hbm.xml</filename> 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 <keycap>F3</keycap> while the cursor is on a class/field or by pressing <keycap>Ctrl</keycap> 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 + <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 <filename>hbm.xml</filename> 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 + </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 + <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 + </note> + </section> + <section> + <title>Configuration property completion</title> + <para>In <filename>cfg.xml</filename> 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 + <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 + <para> + To open any mapping file in the editor, choose <menuchoice><guimenuitem>Open With</guimenuitem><guimenuitem>Hibernate 3.0 XML Editor</guimenuitem></menuchoice> 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 <menuchoice><guimenuitem>Open With</guimenuitem><guimenuitem>Hibernate Configuration 3.0 XML Editor</guimenuitem></menuchoice> 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 + <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> + <para>To add the property in the <property>Properties</property> 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 <emphasis> <property>Name</property> - </emphasis> field press <emphasis> - <property>Ctrl+Space</property> - </emphasis> to invoke the content assist. It will suggest <emphasis> + </emphasis> field press <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> to invoke the content assist. It will suggest <emphasis> <property>'hibernate.'</property> - </emphasis> which is the prefix for all hibernate properties. After selecting <emphasis> + </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 + </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> + <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 + </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 + <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 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 + <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 + <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>, please see <xref linkend="hibernaterevengxmlfile"/> + </para> + </note> + <para>The editor is activated as soon as an <filename>.reveng.xml </filename> file is opened. To get an initial <filename>reveng.xml </filename> file the <property>Reverse Engineering File Wizard</property> can be started via <keycombo><keycap>Ctrl</keycap><keycap>N</keycap></keycombo> and <menuchoice><guimenuitem>Hibernate</guimenuitem><guimenuitem>Hibernate Reverse Engineering File (reveng.xml)</guimenuitem></menuchoice> 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> + </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 + </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> + <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> 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> + </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 + </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> + tables press the <guibutton>Refresh</guibutton> 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 + </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 + <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 + 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 + <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 + click the <guibutton>Reload</guibutton> 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> + </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 + </emphasis> to open a proper <filename>.hbm.xml</filename>. + </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> + <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> + </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 + </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 + </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> + <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> + </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 + </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 + <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 + <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> + <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> <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 + </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 <filename>.png</filename>,<filename>.jpeg</filename> or <filename>.bmp </filename> + </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 + <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 + </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 + </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 + <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/Expand selected item(s)</para> + </entry> + <entry> + <para> <keycap>Enter</keycap> </para> + </entry> + </row> + <row> + <entry> + <para>Show/Hide selected item(s)</para> + </entry> + <entry> + <para> <keycap>+</keycap> </para> + </entry> + </row> + <row> + <entry> + <para>Sort items in alphabetical order or return 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's possible to save the diagram in the eclipse workspace. Click the usual <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>Save As</guimenuitem></menuchoice> 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 + <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 + </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 + </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>) + 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 + </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 + 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 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 + </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 + <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> + </emphasis> you should double-click it. This will open the <property>HQL Editor</property> with the associated query.</para> - <para>Choosing <emphasis> + <para>Choosing <emphasis> <property>HQL Editor</property> - </emphasis> in the context menu for any entity (or any entity child node) will also open + </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 + </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 + <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 (<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 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 + <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 + </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 + <para> Moreover you are able to rename tab in <property>Hibernate Query Result</property>. + Click the tab, and type a new name in <menuchoice><guimenuitem>Property View</guimenuitem><guimenuitem>Tab name field</guimenuitem></menuchoice>. </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 + <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 + <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 + </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 + <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 + </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 + <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> + </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> + </emphasis>,<emphasis> <property>@Entity</property> - </emphasis>,<emphasis> + </emphasis>,<emphasis> <property>@ManyToOne</property> - </emphasis>,<emphasis> + </emphasis>,<emphasis> <property>@OneToMany</property> - </emphasis>,<emphasis> + </emphasis>,<emphasis> <property>@OneToOne</property> - </emphasis>,<emphasis> + </emphasis>,<emphasis> <property>@ManyToMany</property> - </emphasis>,<emphasis> + </emphasis>,<emphasis> <property>@MappedSuperclass</property> - </emphasis>,<emphasis> + </emphasis>,<emphasis> <property>@Id</property> - </emphasis>,<emphasis> + </emphasis>,<emphasis> <property>@GeneratedValue</property> - </emphasis> ,<emphasis> + </emphasis> ,<emphasis> <property>@Version </property> - </emphasis> - </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> + </emphasis> + </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> + </emphasis>,<emphasis> <property>@OneToOne</property> - </emphasis>,<emphasis> + </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> + </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 + </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 + </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 + </note> + <para> + To open this wizard you should right click the class you want to enrich with annotations and select <menuchoice><guimenuitem>Source</guimenuitem><guimenuitem>Generate Hibernate/JPA annotations</guimenuitem></menuchoice>. 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 <guibutton>Back</guibutton> 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 + just press the <guibutton>Next</guibutton> 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 + <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> + </emphasis>in <emphasis> <property> Preferred location of Annotations</property> - </emphasis> dropdownlist and then all the annotations will be added to the getter methods. If + </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 + </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 + <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 + </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 + <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. + </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 + </emphasis> is not inserted into the current class. </para> + <para>After defining all necessary settings in the current step click the <guibutton>Next</guibutton> button 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> + </inlinemediaobject> ,<inlinemediaobject> <imageobject> <imagedata fileref="images/plugins/butt2.png"/> - </imageobject> - </inlinemediaobject> ,<inlinemediaobject> + </imageobject> + </inlinemediaobject> ,<inlinemediaobject> <imageobject> <imagedata fileref="images/plugins/butt3.png"/> - </imageobject> - </inlinemediaobject> ,<inlinemediaobject> + </imageobject> + </inlinemediaobject> ,<inlinemediaobject> <imageobject> <imagedata fileref="images/plugins/butt4.png"/> - </imageobject> - </inlinemediaobject> buttons you can quickly navigate between the differences in the code. If + </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> + <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 + </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 + <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 <filename>hibernate-log4j.properties</filename> in <filename>org.hibernate.eclipse/ directory/jar</filename>. 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 + 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 + <section id="jpa_project_with_hibernate"> + <title>Creating JPA project with Hibernate support</title> + <para>When starting a new JPA project from + <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 <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, + <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, + <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 <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>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 + </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 <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>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 + </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> + <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> + </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> + </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. + </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 + <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 + <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 + </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> + </section> + </section> </chapter>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28428 - trunk/drools/docs/guvnor_ref/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-20 00:24:46 -0500 (Thu, 20 Jan 2011) New Revision: 28428 Modified: trunk/drools/docs/guvnor_ref/en-US/Revision_History.xml trunk/drools/docs/guvnor_ref/en-US/conclusion.xml trunk/drools/docs/guvnor_ref/en-US/functionality_overview.xml trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml Log: General Updates Modified: trunk/drools/docs/guvnor_ref/en-US/Revision_History.xml =================================================================== --- trunk/drools/docs/guvnor_ref/en-US/Revision_History.xml 2011-01-20 05:20:28 UTC (rev 28427) +++ trunk/drools/docs/guvnor_ref/en-US/Revision_History.xml 2011-01-20 05:24:46 UTC (rev 28428) @@ -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>Restructure 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>Restructure 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: trunk/drools/docs/guvnor_ref/en-US/conclusion.xml =================================================================== --- trunk/drools/docs/guvnor_ref/en-US/conclusion.xml 2011-01-20 05:20:28 UTC (rev 28427) +++ trunk/drools/docs/guvnor_ref/en-US/conclusion.xml 2011-01-20 05:24:46 UTC (rev 28428) @@ -1,54 +1,53 @@ <?xml version='1.0' encoding='UTF-8'?> <chapter id="conclusion"> - <?dbhtml filename="conclusion.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Tools</keyword> - <keyword>Eclipse Guvnor Tools</keyword> - </keywordset> - </chapterinfo> + <?dbhtml filename="conclusion.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Eclipse Guvnor Tools</keyword> + </keywordset> + </chapterinfo> - <title>Summary</title> + <title>Summary</title> - <para>As stated at the beginning of this document, the key goal of the <property>EGT</property> - is to provide a way of interacting with Guvnor repository resources in a local Eclipse - workspace. While clearly there is a lot more that could be done, and no doubt there will be - aspects of the current tooling that require revision going forward, we feel that the current - state of the <property>EGT</property> is sufficient for the major use cases.</para> + <para> + As stated at the beginning of this document, the key goal of the <property>EGT</property> is to provide a way to interact with Guvnor repository resources in a local Eclipse workspace. While clearly there is a lot more that could be done, and no doubt there will be aspects of the current tooling that require revision going forward, we feel that the current state of the <property>EGT</property> is sufficient for the major use cases. + </para> - <section> - <title>Other relevant resources on the topic</title> - <para>For more information visit the following resources:</para> - <itemizedlist> - <listitem> - <para>Guvnor <ulink url="http://www.jboss.org/community/wiki/Guvnor">wiki page</ulink></para> - </listitem> - - <listitem> - <para>Drools on <ulink url="http://www.jboss.org/drools/">JBoss.org</ulink></para> - </listitem> - - <listitem> - <para> - <ulink url="http://www.jboss.org/tools/">JBoss Tools Home Page</ulink> - </para> - </listitem> - - <listitem> - <para> - <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">The latest - JBossTools/JBDS documentation builds</ulink> - </para> - </listitem> - - <listitem> - <para> - <ulink url="http://docs.jboss.org/tools/">JBossTools/JBDS - release documentation</ulink></para> - </listitem> - </itemizedlist> - <para>If you have some questions, comments or suggestions on the topic, please feel free to ask in the - <ulink url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=201" - >Jboss Tools Forum</ulink>.</para> - </section> + <section> + <title>Other relevant resources on the topic</title> + <para>For more information visit the following resources:</para> + <itemizedlist> + <listitem> + <para>Guvnor <ulink url="http://www.jboss.org/community/wiki/Guvnor">wiki page</ulink> + </para> + </listitem> + + <listitem> + <para>Drools on <ulink url="http://www.jboss.org/drools/">JBoss.org</ulink> + </para> + </listitem> + + <listitem> + <para> + <ulink url="http://www.jboss.org/tools/">JBoss Tools Home Page</ulink> + </para> + </listitem> + + <listitem> + <para> + <ulink url="http://download.jboss.org/jbosstools/nightly-docs/">The latest JBossTools/JBDS documentation builds</ulink> + </para> + </listitem> + + <listitem> + <para> + <ulink url="http://docs.jboss.org/tools/">JBossTools/JBDS release documentation</ulink> + </para> + </listitem> + </itemizedlist> + <para> + If you have some questions, comments or suggestions on the topic, please feel free to ask in the <ulink url="http://www.jboss.org/index.html?module=bb&op=viewforum&f=201">Jboss Tools Forum</ulink>. + </para> + </section> </chapter> Modified: trunk/drools/docs/guvnor_ref/en-US/functionality_overview.xml =================================================================== --- trunk/drools/docs/guvnor_ref/en-US/functionality_overview.xml 2011-01-20 05:20:28 UTC (rev 28427) +++ trunk/drools/docs/guvnor_ref/en-US/functionality_overview.xml 2011-01-20 05:24:46 UTC (rev 28428) @@ -236,9 +236,9 @@ </mediaobject> </figure> - <guilabel> + <para> This editor uses Eclipse-standard comparison techniques to show the differences in the two versions. In cases where there are no differences, the editor will not open, rather a dialog saying that there are no differences will appear. - </guilabel> + </para> <figure> <title>Alert Dialog</title> <mediaobject> Modified: trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml =================================================================== --- trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml 2011-01-20 05:20:28 UTC (rev 28427) +++ trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml 2011-01-20 05:24:46 UTC (rev 28428) @@ -95,7 +95,7 @@ </figure> <para> - Default values appear in the <guilabel>Location</guilabel>,</guilabel>Port</guilabel> and <guilabel>Repository</guilabel> fields (See the <xref linkend="guvnor_preferences"/> section below for details about how to change these default values.) Of course, any of these fields can be edited by typing in the corresponding text box. Drag-and-drop or paste into the <guilabel>Location</guilabel> field of a typical Guvnor repository URL such as: + Default values appear in the <guilabel>Location</guilabel>,<guilabel>Port</guilabel> and <guilabel>Repository</guilabel> fields (See the <xref linkend="guvnor_preferences"/> section below for details about how to change these default values.) Of course, any of these fields can be edited by typing in the corresponding text box. Drag-and-drop or paste into the <guilabel>Location</guilabel> field of a typical Guvnor repository URL such as: </para> <para>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28427 - trunk/drools/docs/guvnor_ref/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-20 00:20:28 -0500 (Thu, 20 Jan 2011) New Revision: 28427 Modified: trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml Log: General Updates Modified: trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml =================================================================== --- trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml 2011-01-20 04:45:00 UTC (rev 28426) +++ trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml 2011-01-20 05:20:28 UTC (rev 28427) @@ -124,45 +124,35 @@ <para>If an authentication failure error occurs, you can retry the same operation and supply different authentication information.</para> </note> - <para>Note that the <property>EGT</property> calls the Guvnor repository at various times, - such as when determining if resource updates are available. Thus if you use session - authentication, the authentication dialog will appear at different times during the - Eclipse workbench session, depending on what actions you take. For ease of use, we - recommend saving the authentication information in the Eclipse key-ring.</para> + <para> + Note that the <property>EGT</property> calls the Guvnor repository at various times, such as when determining if resource updates are available. Thus if you use session authentication, the authentication dialog will appear at different times during the Eclipse workbench session, depending on what actions you take. For ease of use, we recommend saving the authentication information in the Eclipse key-ring. + </para> <note> <title>Note:</title> - <para>The Eclipse key-ring file is distinct from key-ring files found in some platforms - such as Mac OS X and many forms of Linux. Thus, sometimes if you access a Guvnor - repository outside the <property>EGT</property>, the key-ring files might become - unsynchronized and you will be unexpectedly prompted for authentication in Eclipse. - This is nuisance, but your usual credentials should apply in this case.</para> + <para> + The Eclipse key-ring file is distinct from key-ring files found in some platforms such as Mac OS X and many forms of Linux. Thus, sometimes if you access a Guvnor repository outside the <property>EGT</property>, the key-ring files might become unsynchronized and you will be unexpectedly prompted for authentication in Eclipse. This is nuisance, but your usual credentials should apply in this case. + </para> </note> </section> <section id="resources_from_guvnor"> <title>Resource from Guvnor Wizard</title> - <para>In addition to the single file drag-and-drop from the <property>Guvnor Repositories - view</property>, the <property>EGT</property> also includes a wizard for copying one - or more files from a Guvnor repository to the local workspace (and setting the - association with the Guvnor repository). This wizard is available from the <emphasis> - <property>File > Import > Guvnor > Resource from - Guvnor</property> - </emphasis> and the <emphasis> - <property>File > New > Other > Guvnor > Resource from - Guvnor</property> - </emphasis> menu items.</para> + <para> + In addition to the single file drag-and-drop from the <guilabel>Guvnor Repositories view</guilabel>, the <property>EGT</property> also includes a wizard for copying one or more files from a Guvnor repository to the local workspace (and setting the association with the Guvnor repository). This wizard is available by selecting <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>Import</guimenuitem><guimenuitem>Guvnor</guimenuitem><guimenuitem>Resource from Guvnor</guimenuitem></menuchoice> or <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>Guvnor</guimenuitem><guimenuitem>Resource from Guvnor</guimenuitem></menuchoice>. + </para> <note> <title>Note:</title> - <para>Note that the wizard is identical but appears in both locations to accommodate - users who tend to view this functionality as being in either category.</para> + <para> + Note that the wizard is identical but appears in both locations to accommodate users who tend to view this functionality as being in either category. + </para> </note> - <para>The first page of the wizard asks for the selection of the source Guvnor repository - and gives the choice to create a new Guvnor repository connection (in which case the - second page is the same as the <xref linkend="guvnor_connection_wizard"/>).</para> + <para> + The first page of the wizard asks for the selection of the source Guvnor repository and gives the choice to create a new Guvnor repository connection (in which case the second page is the same as the <xref linkend="guvnor_connection_wizard"/>). + </para> <figure> <title>Resource from Guvnor Wizard</title> @@ -194,9 +184,9 @@ </mediaobject> </figure> - <para>On completion the wizard copies the selected files from the Guvnor repository to the local workspace. - If a file with the same name already exists in the destination, the wizard uses the Eclipse standard - "prompt for rename" dialog:</para> + <para> + On completion the wizard copies the selected files from the Guvnor repository to the local workspace. If a file with the same name already exists in the destination, the wizard uses the Eclipse standard <guilabel>prompt for rename</guilabel> dialog: + </para> <figure> <title>Prompt for Rename Dialog</title> @@ -211,8 +201,7 @@ <section id="guvnor_repositories_view"> <title>Guvnor Repositories View</title> - <para>The <property>Guvnor Repositories view</property> contains tree structures for Guvnor - repository contents.</para> + <para>The <guilabel>Guvnor Repositories view</guilabel> contains tree structures representing Guvnor repository contents.</para> <figure> <title>Guvnor Repositories View</title> @@ -223,8 +212,7 @@ </mediaobject> </figure> - <para>You can perform the following actions under the resources in the - <property>Guvnor Repositories view</property>:</para> + <para>You can perform the following actions under the resources in the <guilabel>Guvnor Repositories view</guilabel>:</para> <itemizedlist> <listitem> @@ -232,52 +220,30 @@ </listitem> <listitem> - <para>remove a Guvnor repository connection. Use the Delete button - ( <inlinemediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/delete_connection_button.png"/> - </imageobject> - </inlinemediaobject> ) in the tool-bar or the <emphasis> - <property>Delete</property> - </emphasis> option in the context menu to remove a repository connection.</para> + <para> + Remove a Guvnor repository connection. Use the Delete button ( <inlinemediaobject><imageobject><imagedata fileref="images/functionality_overview/delete_connection_button.png"/></imageobject></inlinemediaobject> ) in the tool-bar or the <guimenuitem>Delete</guimenuitem> option in the context menu to remove a repository connection. + </para> </listitem> <listitem> - <para>refresh Guvnor repository resorces. Use the <emphasis> - <property>Refresh</property> - </emphasis> context menu item to reload a tree content for the selected node.</para> + <para> + Refresh Guvnor repository resorces. Use the <guimenuitem>Refresh</guimenuitem> context menu item to reload a tree content for the selected node. + </para> </listitem> <listitem> - <para>make use of "drill-into" functionality. It's represented by a number of tool-bar/context menu items such as <emphasis><property>Go Home</property> - </emphasis> - ( <inlinemediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/go_home_button.png"/> - </imageobject> - </inlinemediaobject> ), <emphasis><property>Go Back</property> - </emphasis> - ( <inlinemediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/go_back_button.png"/> - </imageobject> - </inlinemediaobject> ) and <emphasis> - <property>Go Into</property> - </emphasis> - ( <inlinemediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/go_into_button.png"/> - </imageobject> - </inlinemediaobject> ).</para> + <para> + Make use of "drill-into" functionality. It's represented by a number of tool-bar/context menu items such as <guibutton>Go Home</guibutton> ( <inlinemediaobject><imageobject><imagedata fileref="images/functionality_overview/go_home_button.png"/></imageobject></inlinemediaobject> ), <guibutton>Go Back</guibutton> ( <inlinemediaobject><imageobject><imagedata fileref="images/functionality_overview/go_back_button.png"/></imageobject></inlinemediaobject> ) and <guibutton>Go Into</guibutton> ( <inlinemediaobject><imageobject><imagedata fileref="images/functionality_overview/go_into_button.png"/></imageobject></inlinemediaobject> ). + </para> </listitem> </itemizedlist> - <para>Drill-down is useful when working with deeply nested tree structures and when you wish to concentrate on only branch of the tree. For example, drilling into the <emphasis> - <property>"defaultPackage"</property> - </emphasis> node changes the tree view to:</para> + <para> + Drill-down is useful when working with deeply nested tree structures and when you wish to concentrate on only branch of the tree. For example, drilling into the <guilabel>defaultPackage</guilabel> node changes the tree view to: + </para> <figure> - <title>Going Into the <emphasis>"defaultPackage"</emphasis> + <title>Going Into the <guilabel>defaultPackage</guilabel> </title> <mediaobject> <imageobject> @@ -286,18 +252,13 @@ </mediaobject> </figure> - <para>Clicking on the Go Home button ( <inlinemediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/go_home_button.png"/> - </imageobject> - </inlinemediaobject> ) or selecting <emphasis> - <property>Go Home</property> - </emphasis> in the context menu returns the tree to the top-level structure shown in the previous picture above. - </para> + <para> + Clicking on the <guibutton>Go Home</guibutton> button ( <inlinemediaobject><imageobject><imagedata fileref="images/functionality_overview/go_home_button.png"/></imageobject></inlinemediaobject> ) or selecting <guimenuitem>Go Home</guimenuitem> in the context menu returns the tree to the top-level structure shown in the previous picture above. + </para> - <para>There are a number of operations that can be performed on Guvnor repository files. Selecting a file in - the Guvnor repository causes the Eclipse <property>Properties view</property> to update with details about that file: - </para> + <para> + There are a number of operations that can be performed on Guvnor repository files. Selecting a file in the Guvnor repository causes the Eclipse <guilabel>Properties view</guilabel> to update with details about that file: + </para> <figure> <title>Guvnor Repository Files Properties</title> @@ -314,9 +275,9 @@ <section id="guvnor_history_view"> <title>Guvnor Resource History View</title> - <para>The <property>Guvnor Resource History view</property> should details about revision - history for selected files, both local and those in Guvnor repositories. The initial - state of this view is shown on the figure below.</para> + <para> + The <guilabel>Guvnor Resource History view</guilabel> shows details about revision history for selected files, both local and those in Guvnor repositories. The initial state of this view is shown on the figure below. + </para> <figure> <title>Initial State of the Guvnor Resource History View</title> @@ -327,13 +288,9 @@ </mediaobject> </figure> - <para>The <property>Guvnor Resource History view</property> is populated by <emphasis> - <property>Show History</property> - </emphasis> actions in either the local <emphasis> - <property>Guvnor</property> - </emphasis> context menu or in the context menu for - a Guvnor repository file in the <xref linkend="guvnor_repositories_view"/>. Once this action is performed, the <property>Guvnor - Resource History view</property> updates to show the revision history:</para> + <para> + The <guilabel>Guvnor Resource History view</guilabel> is populated by <guilabel>Show History</guilabel> actions in either the local <guilabel>Guvnor</guilabel> context menu or in the context menu for a Guvnor repository file in the <xref linkend="guvnor_repositories_view"/>. Once this action is performed, the <guilabel>Guvnor Resource History view</guilabel> updates to show the revision history: + </para> <figure> <title>Guvnor Resource History View</title> @@ -344,11 +301,9 @@ </mediaobject> </figure> - <para>Here we see that the file <emphasis> - <property>test.txt</property> - </emphasis> has seven revisions. Double clicking on a revision row (or the context menu <emphasis> - <property>Open (Read only)</property>)</emphasis> opens an Eclipse read-only editor - with the revision contents.</para> + <para> + Here we see that the file <filename>test.txt</filename> has seven revisions. Double clicking on a revision row (or the context menu <guimenuitem>Open (Read only)</guimenuitem>) opens an Eclipse read-only editor with the revision contents. + </para> <figure> <title>Eclipse Read-only Editor with the Revision Contents</title> @@ -360,11 +315,9 @@ </figure> <note> <title>Note:</title> - <para>You can also use the <emphasis> - <property>Save As...</property> - </emphasis> option when a file is open in a read-only editor to save a local - writable copy of the contents. Doing so, however, will not associate the file - created with its Guvnor source.</para> + <para> + You can also use the <guimenuitem>Save As...</guimenuitem> option when a file is open in a read-only editor to save a local writable copy of the contents. Doing so, however, will not associate the file created with its Guvnor source. + </para> </note> </section> @@ -373,9 +326,7 @@ <title>Guvnor Preferences</title> - <para>The <property>EGT</property> provides a preference page in the <emphasis> - <property>Guvnor</property> - </emphasis> category:</para> + <para>The <property>EGT</property> provides a preference page in the <guilabel>Guvnor</guilabel> category:</para> <figure> <title>Resource Selection</title> @@ -393,56 +344,44 @@ </listitem> <listitem> - <para>Local Guvnor - repository resource decorations.</para> + <para>Local Guvnor repository resource decorations.</para> </listitem> </itemizedlist> <section id="repo_connection_preferences"> <title>Guvnor Repository Connection Preferences</title> - <para>There are two preferences that can be set for Guvnor repository connections, that are - used when creating new connections:</para> + <para>There are two preferences that can be set for Guvnor repository connections, that are used when creating new connections:</para> <itemizedlist> <listitem> - <para>The first is a default Guvnor repository URL template, which can make it - easier to create multiple similar connections by simply changing part of the - field, such as the host name.</para> + <para> + The first is a default Guvnor repository URL template, which can make it easier to create multiple similar connections by simply changing part of the field, such as the host name. + </para> </listitem> <listitem> - <para>The second is whether saving of authentication information in the Eclipse - platform key-ring should be enabled by default.</para> + <para> + The second is whether authentication information should be saved in the Eclipse platform key-ring by default.</para> </listitem> </itemizedlist> - <para>As with the Guvnor repository URL template, actually whether to save a specific - instance of authentication information in the Eclipse platform key-ring can be - determined when actually creating the connection. That is, both of these preferences are - simply convenience values set to reasonable defaults.</para> + <para> + As with the Guvnor repository URL template, the decision whether to save authentication information in the Eclipse platform key-ring can be determined when creating the connection. That is, both of these preferences are simply convenience values set to reasonable defaults. + </para> </section> <section id="resource_decoration_preferences"> <title>Local Guvnor Repository Resource Decoration Preferences</title> - <para>The second category of preferences provided by the <property>EGT</property> deals with how the decoration of - local resources associated with Guvnor repository resources is presented. Since the - Guvnor repository is not a substitute for a SCM, and since SCM tools in Eclipse tend to - decorate local resources, it is useful to be able to control just how the <property>EGT</property> decorate - its local resources to avoid messy conflicts with SCM packages.</para> + <para> + The second category of preferences provided by the <property>EGT</property> deals with how the decoration of local resources associated with Guvnor repository resources is presented. Since the Guvnor repository is not a substitute for a SCM, and since SCM tools in Eclipse tend to decorate local resources, it is useful to be able to control just how the <property>EGT</property> decorate its local resources to avoid messy conflicts with SCM packages. + </para> - <para>In the <emphasis> - <property>File Decoration</property> - </emphasis> - section of the preference page, you can choose the location (Top right, Top left, Bottom right, - Bottom left) of the decoration icon, or you can choose not to display it. In - the <emphasis> - <property>Text</property> - </emphasis> section, you can format the Guvnor metadata that is appended to the file - names:</para> + <para> + In the <guilabel>File Decoration</guilabel> section of the preference page, you can choose the location (Top right, Top left, Bottom right, Bottom left) of the decoration icon, or you can choose not to display it. In the <guilabel>Text</guilabel> section, you can format the Guvnor metadata that is appended to the file names: + </para> <itemizedlist> <listitem> - <para>Whether to show an indicator (>) when the local file has changes not committed back to the - Guvnor repository</para> + <para>Whether to show an indicator (>) when the local file has changes not committed back to the Guvnor repository</para> </listitem> <listitem> <para>Whether to show the revision number</para> @@ -452,11 +391,9 @@ </listitem> </itemizedlist> - <para>Any changes to these preferences take effect immediately upon clicking the <emphasis> - <property>Apply</property> - </emphasis> and then <emphasis> - <property>Ok</property> - </emphasis> buttons.</para> + <para> + Any changes to these preferences take effect immediately upon clicking the <guibutton>Apply</guibutton> and then <guibutton>OK</guibutton> buttons. + </para> </section> </section> </chapter>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28426 - trunk/drools/docs/guvnor_ref/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-19 23:45:00 -0500 (Wed, 19 Jan 2011) New Revision: 28426 Modified: trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml Log: General Updates Modified: trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml =================================================================== --- trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml 2011-01-20 04:32:56 UTC (rev 28425) +++ trunk/drools/docs/guvnor_ref/en-US/guvnor_preferences.xml 2011-01-20 04:45:00 UTC (rev 28426) @@ -1,467 +1,462 @@ <?xml version='1.0' encoding='UTF-8'?> <chapter id="guvnor_preferences"> - <?dbhtml filename="guvnor_preferences.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Tools</keyword> - <keyword>Eclipse Guvnor Tools</keyword> - </keywordset> - </chapterinfo> + <?dbhtml filename="guvnor_preferences.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Eclipse Guvnor Tools</keyword> + </keywordset> + </chapterinfo> - <title>Reference</title> - <para>This chapter includes detailed reference information about Views and Wizards used to manage Guvnor Tools.</para> - - <section id="guvnor_perspective"> - <title>Guvnor Repository Exploring Perspective</title> - - <para>The <property>Guvnor Repository Exploring perspective</property> contains two views - supplied by <property>EGT</property> – <xref linkend="guvnor_repositories_view"/> and - <xref linkend="guvnor_history_view"/>, that will be the center of most interactions - with Guvnor, and Eclipse standard views such as <property>Properties</property> and - <property>Resource Navigator</property> that are also useful.</para> - - <para>While each of these views can be opened and positioned independently within an Eclipse - workbench, the <property>Guvnor perspective</property> provides a convenient method of - getting a suggested layout. In the Eclipse workbench menu, choose <emphasis> - <property>Window > Open Perspective > Other</property> - </emphasis> to get the perspective list:</para> - - <figure> - <title>Enabling the Guvnor Repository Perspective</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/open_guvnor_perspectine.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>And then choose <emphasis> - <property>Guvnor Repository Exploring</property>.</emphasis> This opens the - <property>Guvnor perspective</property>.</para> - </section> - - <section id="connection_wizard"> - <title>Guvnor Connection Wizard</title> - - <para>This wizard appears in a number of places within the - <property>EGT</property> (as detailed below), but in this section we will cover only - the two most basic entry points.</para> - - <para>The <property>Guvnor Connection wizard</property> can be started in the following - ways:</para> - - <itemizedlist> - <listitem> - <para>using the Eclipse menu <emphasis> - <property>File > New > Other > Guvnor > Guvnor - repository location</property> - </emphasis></para> - - <figure> - <title>New Guvnor Repository Location</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/start_guvnor_connection1.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - - <listitem> - <para>in the <property>Guvnor Repositories view</property> using the drop-down menu</para> - - <figure> - <title>Adding New Guvnor Connection</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/start_guvnor_connection2.png"/> - </imageobject> - </mediaobject> - </figure> - </listitem> - - <listitem> - <para>using the menu button + <title>Reference</title> + <para>This chapter includes detailed reference information about Views and Wizards used to manage Guvnor Tools.</para> + + <section id="guvnor_perspective"> + <title>Guvnor Repository Exploring Perspective</title> + + <para> + The <property>Guvnor Repository Exploring perspective</property> contains two views supplied by <property>EGT</property> – <xref linkend="guvnor_repositories_view"/> and <xref linkend="guvnor_history_view"/>, that will be the center of most interactions with Guvnor, and Eclipse standard views such as <guilabel>Properties</guilabel> and <guilabel>Resource Navigator</guilabel> that are also useful. + </para> + + <para> + While each of these views can be opened and positioned independently within an Eclipse workbench, the <property>Guvnor perspective</property> provides a convenient method of getting a suggested layout. In the Eclipse workbench menu, choose <menuchoice><guimenuitem>Window</guimenuitem><guimenuitem>Open Perspective</guimenuitem><guimenuitem>Other</guimenuitem></menuchoice> to get the perspective list: + </para> + + <figure> + <title>Enabling the Guvnor Repository Perspective</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/open_guvnor_perspectine.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>And then choose <guimenuitem>Guvnor Repository Exploring</guimenuitem>. This opens the <guilabel>Guvnor perspective</guilabel>.</para> + </section> + + <section id="connection_wizard"> + <title>Guvnor Connection Wizard</title> + + <para> + This wizard appears in a number of places within the <property>EGT</property> (as detailed below), but in this section we will cover only the two most basic entry points. + </para> + + <para>The <guilabel>Guvnor Connection wizard</guilabel> can be started in the following ways:</para> + + <itemizedlist> + <listitem> + <para> + Using the Eclipse menu <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem> <guimenuitem>Guvnor</guimenuitem><guimenuitem>Guvnor repository location</guimenuitem></menuchoice> + </para> + + <figure> + <title>New Guvnor Repository Location</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/start_guvnor_connection1.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + + <listitem> + <para>In the <guilabel>Guvnor Repositories view</guilabel> using the drop-down menu</para> + + <figure> + <title>Adding New Guvnor Connection</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/start_guvnor_connection2.png"/> + </imageobject> + </mediaobject> + </figure> + </listitem> + + <listitem> + <para>using the menu button ( <inlinemediaobject> <imageobject> <imagedata fileref="images/functionality_overview/guvnor_connection_button.png"/> - </imageobject> - </inlinemediaobject> ) + </imageobject> + </inlinemediaobject> ) </para> - </listitem> - </itemizedlist> - - <para>Choosing either of these will start the <property>Guvnor Connection - wizard</property>.</para> - - <figure id="guvnor_connection_wizard"> - <title>Guvnor Connection Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/guvnor_connection_wizard.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Default values appear in the <emphasis> - <property>Location</property>,</emphasis> - <emphasis> - <property>Port</property>,</emphasis> and <emphasis> - <property>Repository</property> - </emphasis> fields (See the <xref linkend="guvnor_preferences"/> section below for details about how to - change these default values.) Of course, any of these fields can be edited by typing in - the corresponding text box. Drag-and-drop or paste into the <emphasis> - <property>Location</property> - </emphasis> field of a typical Guvnor repository URL such as:</para> - - <para> - <emphasis> - <property>http://localhost:8080/drools-guvnor/org.drools.guvnor.Guvnor/webdav</property> - </emphasis> - </para> - - <para>Results in the URL being parsed into the respective fields as well. The authentication - information (user name and password) can optionally be stored in the Eclipse - workbench's key-ring file based on the selection of <emphasis> - <property>Save user name and password</property>.</emphasis></para> - - <note> - <title>Note:</title> - <para>If the authentication information is not stored in the key-ring, then the - <property>EGT</property> uses a session authentication, what means that the - credentials supplied are used only for the lifetime of the Eclipse workbench - instance.</para> - </note> - - <para>If authentication information is not stored in the key-ring or the authentication - information (key-ring or session) is not valid, the <property>EGT</property> will prompt - for authentication information when it has to access the Guvnor repository.</para> - - <para>If authentication fails, the <property>EGT</property> will retry once and then issue - an authentication failure error.</para> - - <note> - <title>Tip:</title> - <para>If an authentication failure error occurs, you can retry the same operation and - supply different authentication information.</para> - </note> - - <para>Note that the <property>EGT</property> calls the Guvnor repository at various times, + </listitem> + </itemizedlist> + + <para>Choosing either of these will start the <guilabel>Guvnor Connection wizard</guilabel>.</para> + + <figure id="guvnor_connection_wizard"> + <title>Guvnor Connection Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/guvnor_connection_wizard.png"/> + </imageobject> + </mediaobject> + </figure> + + <para> + Default values appear in the <guilabel>Location</guilabel>,</guilabel>Port</guilabel> and <guilabel>Repository</guilabel> fields (See the <xref linkend="guvnor_preferences"/> section below for details about how to change these default values.) Of course, any of these fields can be edited by typing in the corresponding text box. Drag-and-drop or paste into the <guilabel>Location</guilabel> field of a typical Guvnor repository URL such as: + </para> + + <para> + <ulink url="http://localhost:8080/drools-guvnor/org.drools.guvnor.Guvnor/webdav">http://localhost:8080/drools-guvnor/org.drools.guvnor.Guvnor/webdav</ulink> + </para> + + <para> + Results in the URL being parsed into the respective fields as well. The authentication information (user name and password) can optionally be stored in the Eclipse workbench's key-ring file based on the selection of <guilabel>Save user name and password</guilabel>. + </para> + + <note> + <title>Note:</title> + <para> + If the authentication information is not stored in the key-ring, then the <property>EGT</property> uses a session authentication, what means that the credentials supplied are used only for the lifetime of the Eclipse workbench instance. + </para> + </note> + + <para> + If authentication information is not stored in the key-ring or the authentication information (key-ring or session) is not valid, the <property>EGT</property> will prompt for authentication information when it has to access the Guvnor repository. + </para> + + <para>If authentication fails, the <property>EGT</property> will retry once and then issue an authentication failure error.</para> + + <note> + <title>Tip:</title> + <para>If an authentication failure error occurs, you can retry the same operation and supply different authentication information.</para> + </note> + + <para>Note that the <property>EGT</property> calls the Guvnor repository at various times, such as when determining if resource updates are available. Thus if you use session authentication, the authentication dialog will appear at different times during the Eclipse workbench session, depending on what actions you take. For ease of use, we recommend saving the authentication information in the Eclipse key-ring.</para> - - <note> - <title>Note:</title> - <para>The Eclipse key-ring file is distinct from key-ring files found in some platforms + + <note> + <title>Note:</title> + <para>The Eclipse key-ring file is distinct from key-ring files found in some platforms such as Mac OS X and many forms of Linux. Thus, sometimes if you access a Guvnor repository outside the <property>EGT</property>, the key-ring files might become unsynchronized and you will be unexpectedly prompted for authentication in Eclipse. This is nuisance, but your usual credentials should apply in this case.</para> - </note> - </section> - - <section id="resources_from_guvnor"> - <title>Resource from Guvnor Wizard</title> - - <para>In addition to the single file drag-and-drop from the <property>Guvnor Repositories + </note> + </section> + + <section id="resources_from_guvnor"> + <title>Resource from Guvnor Wizard</title> + + <para>In addition to the single file drag-and-drop from the <property>Guvnor Repositories view</property>, the <property>EGT</property> also includes a wizard for copying one or more files from a Guvnor repository to the local workspace (and setting the association with the Guvnor repository). This wizard is available from the <emphasis> <property>File > Import > Guvnor > Resource from Guvnor</property> - </emphasis> and the <emphasis> + </emphasis> and the <emphasis> <property>File > New > Other > Guvnor > Resource from Guvnor</property> - </emphasis> menu items.</para> - <note> - <title>Note:</title> - - <para>Note that the wizard is identical but appears in both locations to accommodate + </emphasis> menu items.</para> + <note> + <title>Note:</title> + + <para>Note that the wizard is identical but appears in both locations to accommodate users who tend to view this functionality as being in either category.</para> - </note> - - <para>The first page of the wizard asks for the selection of the source Guvnor repository + </note> + + <para>The first page of the wizard asks for the selection of the source Guvnor repository and gives the choice to create a new Guvnor repository connection (in which case the second page is the same as the <xref linkend="guvnor_connection_wizard"/>).</para> - - <figure> - <title>Resource from Guvnor Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/add_toGuvnor_wizard.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Once the source Guvnor repository is chosen, the wizard prompts for resource selection:</para> - - <figure> - <title>Resource Selection</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/resource_from_guvnor.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Finally, the target location in the local workspace should be chosen:</para> - <figure> - <title>Choosing the Target Location</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/resource_from_guvnor2.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>On completion the wizard copies the selected files from the Guvnor repository to the local workspace. + + <figure> + <title>Resource from Guvnor Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/add_toGuvnor_wizard.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Once the source Guvnor repository is chosen, the wizard prompts for resource selection:</para> + + <figure> + <title>Resource Selection</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/resource_from_guvnor.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Finally, the target location in the local workspace should be chosen:</para> + <figure> + <title>Choosing the Target Location</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/resource_from_guvnor2.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>On completion the wizard copies the selected files from the Guvnor repository to the local workspace. If a file with the same name already exists in the destination, the wizard uses the Eclipse standard "prompt for rename" dialog:</para> - - <figure> - <title>Prompt for Rename Dialog</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/resource_from_guvnor3.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - - <section id="guvnor_repositories_view"> - <title>Guvnor Repositories View</title> - - <para>The <property>Guvnor Repositories view</property> contains tree structures for Guvnor - repository contents.</para> - - <figure> - <title>Guvnor Repositories View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/guvnor_repository.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>You can perform the following actions under the resources in the + + <figure> + <title>Prompt for Rename Dialog</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/resource_from_guvnor3.png"/> + </imageobject> + </mediaobject> + </figure> + </section> + + <section id="guvnor_repositories_view"> + <title>Guvnor Repositories View</title> + + <para>The <property>Guvnor Repositories view</property> contains tree structures for Guvnor + repository contents.</para> + + <figure> + <title>Guvnor Repositories View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/guvnor_repository.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>You can perform the following actions under the resources in the <property>Guvnor Repositories view</property>:</para> - - <itemizedlist> - <listitem> - <para>create a new Guvnor repository connection. How to do this is describe above in the <xref linkend="connection_wizard"/> section.</para> - </listitem> - - <listitem> - <para>remove a Guvnor repository connection. Use the Delete button + + <itemizedlist> + <listitem> + <para>create a new Guvnor repository connection. How to do this is describe above in the <xref linkend="connection_wizard"/> section.</para> + </listitem> + + <listitem> + <para>remove a Guvnor repository connection. Use the Delete button ( <inlinemediaobject> <imageobject> <imagedata fileref="images/functionality_overview/delete_connection_button.png"/> - </imageobject> - </inlinemediaobject> ) in the tool-bar or the <emphasis> - <property>Delete</property></emphasis> option in the context menu to remove a repository connection.</para> - </listitem> - - <listitem> - <para>refresh Guvnor repository resorces. Use the <emphasis> - <property>Refresh</property></emphasis> context menu item to reload a tree content for the selected node.</para> - </listitem> - - <listitem> - <para>make use of "drill-into" functionality. It's represented by a number of tool-bar/context menu items such as <emphasis><property>Go Home</property></emphasis> + </imageobject> + </inlinemediaobject> ) in the tool-bar or the <emphasis> + <property>Delete</property> + </emphasis> option in the context menu to remove a repository connection.</para> + </listitem> + + <listitem> + <para>refresh Guvnor repository resorces. Use the <emphasis> + <property>Refresh</property> + </emphasis> context menu item to reload a tree content for the selected node.</para> + </listitem> + + <listitem> + <para>make use of "drill-into" functionality. It's represented by a number of tool-bar/context menu items such as <emphasis><property>Go Home</property> + </emphasis> ( <inlinemediaobject> <imageobject> <imagedata fileref="images/functionality_overview/go_home_button.png"/> - </imageobject> - </inlinemediaobject> ), <emphasis><property>Go Back</property></emphasis> + </imageobject> + </inlinemediaobject> ), <emphasis><property>Go Back</property> + </emphasis> ( <inlinemediaobject> <imageobject> <imagedata fileref="images/functionality_overview/go_back_button.png"/> - </imageobject> - </inlinemediaobject> ) and <emphasis> - <property>Go Into</property></emphasis> + </imageobject> + </inlinemediaobject> ) and <emphasis> + <property>Go Into</property> + </emphasis> ( <inlinemediaobject> <imageobject> <imagedata fileref="images/functionality_overview/go_into_button.png"/> - </imageobject> - </inlinemediaobject> ).</para> - </listitem> - </itemizedlist> - - <para>Drill-down is useful when working with deeply nested tree structures and when you wish to concentrate on only branch of the tree. For example, drilling into the <emphasis> - <property>"defaultPackage"</property></emphasis> node changes the tree view to:</para> - - <figure> - <title>Going Into the <emphasis>"defaultPackage"</emphasis></title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/go_into_defaultPackage.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Clicking on the Go Home button ( <inlinemediaobject> + </imageobject> + </inlinemediaobject> ).</para> + </listitem> + </itemizedlist> + + <para>Drill-down is useful when working with deeply nested tree structures and when you wish to concentrate on only branch of the tree. For example, drilling into the <emphasis> + <property>"defaultPackage"</property> + </emphasis> node changes the tree view to:</para> + + <figure> + <title>Going Into the <emphasis>"defaultPackage"</emphasis> + </title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/go_into_defaultPackage.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Clicking on the Go Home button ( <inlinemediaobject> <imageobject> <imagedata fileref="images/functionality_overview/go_home_button.png"/> - </imageobject> - </inlinemediaobject> ) or selecting <emphasis> - <property>Go Home</property></emphasis> in the context menu returns the tree to the top-level structure shown in the previous picture above. + </imageobject> + </inlinemediaobject> ) or selecting <emphasis> + <property>Go Home</property> + </emphasis> in the context menu returns the tree to the top-level structure shown in the previous picture above. </para> - - <para>There are a number of operations that can be performed on Guvnor repository files. Selecting a file in + + <para>There are a number of operations that can be performed on Guvnor repository files. Selecting a file in the Guvnor repository causes the Eclipse <property>Properties view</property> to update with details about that file: </para> - - <figure> - <title>Guvnor Repository Files Properties</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/repository_files_properties.png"/> - </imageobject> - </mediaobject> - </figure> - - <para></para> - </section> - - <section id="guvnor_history_view"> - <title>Guvnor Resource History View</title> - - <para>The <property>Guvnor Resource History view</property> should details about revision + + <figure> + <title>Guvnor Repository Files Properties</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/repository_files_properties.png"/> + </imageobject> + </mediaobject> + </figure> + + <para></para> + </section> + + <section id="guvnor_history_view"> + <title>Guvnor Resource History View</title> + + <para>The <property>Guvnor Resource History view</property> should details about revision history for selected files, both local and those in Guvnor repositories. The initial state of this view is shown on the figure below.</para> - - <figure> - <title>Initial State of the Guvnor Resource History View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/resource_history_view.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>The <property>Guvnor Resource History view</property> is populated by <emphasis> + + <figure> + <title>Initial State of the Guvnor Resource History View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/resource_history_view.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>The <property>Guvnor Resource History view</property> is populated by <emphasis> <property>Show History</property> - </emphasis> actions in either the local <emphasis> - <property>Guvnor</property></emphasis> context menu or in the context menu for + </emphasis> actions in either the local <emphasis> + <property>Guvnor</property> + </emphasis> context menu or in the context menu for a Guvnor repository file in the <xref linkend="guvnor_repositories_view"/>. Once this action is performed, the <property>Guvnor Resource History view</property> updates to show the revision history:</para> - - <figure> - <title>Guvnor Resource History View</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/resource_history_view2.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Here we see that the file <emphasis> + + <figure> + <title>Guvnor Resource History View</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/resource_history_view2.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>Here we see that the file <emphasis> <property>test.txt</property> - </emphasis> has seven revisions. Double clicking on a revision row (or the context menu <emphasis> + </emphasis> has seven revisions. Double clicking on a revision row (or the context menu <emphasis> <property>Open (Read only)</property>)</emphasis> opens an Eclipse read-only editor with the revision contents.</para> - - <figure> - <title>Eclipse Read-only Editor with the Revision Contents</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/resource_history_view3.png"/> - </imageobject> - </mediaobject> - </figure> - <note> - <title>Note:</title> - <para>You can also use the <emphasis> + + <figure> + <title>Eclipse Read-only Editor with the Revision Contents</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/resource_history_view3.png"/> + </imageobject> + </mediaobject> + </figure> + <note> + <title>Note:</title> + <para>You can also use the <emphasis> <property>Save As...</property> - </emphasis> option when a file is open in a read-only editor to save a local + </emphasis> option when a file is open in a read-only editor to save a local writable copy of the contents. Doing so, however, will not associate the file created with its Guvnor source.</para> - </note> + </note> + + </section> + + <section id="preferences"> + <title>Guvnor Preferences</title> - </section> - - <section id="preferences"> - <title>Guvnor Preferences</title> - - - <para>The <property>EGT</property> provides a preference page in the <emphasis> + + <para>The <property>EGT</property> provides a preference page in the <emphasis> <property>Guvnor</property> - </emphasis> category:</para> - - <figure> - <title>Resource Selection</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/guvnor_preferences/guvnor_preferences.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>The preferences cover two categories:</para> - <itemizedlist> - <listitem><para>Guvnor repository connections</para></listitem> - - <listitem><para>Local Guvnor - repository resource decorations.</para></listitem> - </itemizedlist> - - <section id="repo_connection_preferences"> - <title>Guvnor Repository Connection Preferences</title> - <para>There are two preferences that can be set for Guvnor repository connections, that are + </emphasis> category:</para> + + <figure> + <title>Resource Selection</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/guvnor_preferences/guvnor_preferences.png"/> + </imageobject> + </mediaobject> + </figure> + + <para>The preferences cover two categories:</para> + <itemizedlist> + <listitem> + <para>Guvnor repository connections</para> + </listitem> + + <listitem> + <para>Local Guvnor + repository resource decorations.</para> + </listitem> + </itemizedlist> + + <section id="repo_connection_preferences"> + <title>Guvnor Repository Connection Preferences</title> + <para>There are two preferences that can be set for Guvnor repository connections, that are used when creating new connections:</para> - - <itemizedlist> - <listitem> - <para>The first is a default Guvnor repository URL template, which can make it + + <itemizedlist> + <listitem> + <para>The first is a default Guvnor repository URL template, which can make it easier to create multiple similar connections by simply changing part of the field, such as the host name.</para> - </listitem> - <listitem> - <para>The second is whether saving of authentication information in the Eclipse + </listitem> + <listitem> + <para>The second is whether saving of authentication information in the Eclipse platform key-ring should be enabled by default.</para> - </listitem> - </itemizedlist> - - <para>As with the Guvnor repository URL template, actually whether to save a specific + </listitem> + </itemizedlist> + + <para>As with the Guvnor repository URL template, actually whether to save a specific instance of authentication information in the Eclipse platform key-ring can be determined when actually creating the connection. That is, both of these preferences are simply convenience values set to reasonable defaults.</para> - </section> - - <section id="resource_decoration_preferences"> - <title>Local Guvnor Repository Resource Decoration Preferences</title> - - <para>The second category of preferences provided by the <property>EGT</property> deals with how the decoration of + </section> + + <section id="resource_decoration_preferences"> + <title>Local Guvnor Repository Resource Decoration Preferences</title> + + <para>The second category of preferences provided by the <property>EGT</property> deals with how the decoration of local resources associated with Guvnor repository resources is presented. Since the Guvnor repository is not a substitute for a SCM, and since SCM tools in Eclipse tend to decorate local resources, it is useful to be able to control just how the <property>EGT</property> decorate its local resources to avoid messy conflicts with SCM packages.</para> - - <para>In the <emphasis> - <property>File Decoration</property></emphasis> + + <para>In the <emphasis> + <property>File Decoration</property> + </emphasis> section of the preference page, you can choose the location (Top right, Top left, Bottom right, Bottom left) of the decoration icon, or you can choose not to display it. In the <emphasis> - <property>Text</property></emphasis> section, you can format the Guvnor metadata that is appended to the file + <property>Text</property> + </emphasis> section, you can format the Guvnor metadata that is appended to the file names:</para> - <itemizedlist> - <listitem> - <para>Whether to show an indicator (>) when the local file has changes not committed back to the + <itemizedlist> + <listitem> + <para>Whether to show an indicator (>) when the local file has changes not committed back to the Guvnor repository</para> - </listitem> - <listitem> - <para>Whether to show the revision number</para> - </listitem> - <listitem> - <para>Whether to show the date/time stamp</para> - </listitem> - </itemizedlist> - - <para>Any changes to these preferences take effect immediately upon clicking the <emphasis> - <property>Apply</property></emphasis> and then <emphasis> - <property>Ok</property></emphasis> buttons.</para> - </section> - </section> + </listitem> + <listitem> + <para>Whether to show the revision number</para> + </listitem> + <listitem> + <para>Whether to show the date/time stamp</para> + </listitem> + </itemizedlist> + + <para>Any changes to these preferences take effect immediately upon clicking the <emphasis> + <property>Apply</property> + </emphasis> and then <emphasis> + <property>Ok</property> + </emphasis> buttons.</para> + </section> + </section> </chapter>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28425 - trunk/build/aggregate/site.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-19 23:32:56 -0500 (Wed, 19 Jan 2011) New Revision: 28425 Modified: trunk/build/aggregate/site/build.xml Log: refactor; simplify cleanup step + reduce log clutter Modified: trunk/build/aggregate/site/build.xml =================================================================== --- trunk/build/aggregate/site/build.xml 2011-01-20 04:31:18 UTC (rev 28424) +++ trunk/build/aggregate/site/build.xml 2011-01-20 04:32:56 UTC (rev 28425) @@ -59,37 +59,37 @@  <var unset="true" name="ALL_ZIPS" /> <var unset="true" name="wget.return" /> - <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> + <exec executable="wget" dir="${aggregate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/logs/zip.list.txt -q --no-clobber" /> </exec> <echo level="verbose">Fetch SVN_REVISION.txt if it exists (return 8 if not found)</echo> - <var name="svnRevTXT" value="${aggegate.zips.dir}/SVN_REVISION.txt" /> - <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> + <var name="svnRevTXT" value="${aggregate.zips.dir}/SVN_REVISION.txt" /> + <exec executable="wget" dir="${aggregate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/logs/SVN_REVISION.txt -q --no-clobber" /> </exec> <echo level="verbose">Fetch SVN_REVISION.xml if it exists (return 8 if not found)</echo> - <var name="svnRevXML" value="${aggegate.zips.dir}/SVN_REVISION.xml" /> - <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> + <var name="svnRevXML" value="${aggregate.zips.dir}/SVN_REVISION.xml" /> + <exec executable="wget" dir="${aggregate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/logs/SVN_REVISION.xml -q --no-clobber" /> </exec> <echo level="verbose">Fetch build.properties if it exists (return 8 if not found)</echo> - <var name="buildProperties" value="${aggegate.zips.dir}/build.properties" /> - <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> + <var name="buildProperties" value="${aggregate.zips.dir}/build.properties" /> + <exec executable="wget" dir="${aggregate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/logs/build.properties -q --no-clobber" /> </exec> <if> <and> <equals arg1="${wget.return}" arg2="0" /> - <available file="${aggegate.zips.dir}/zip.list.txt" type="file" /> + <available file="${aggregate.zips.dir}/zip.list.txt" type="file" /> </and> <then>  <var unset="true" name="ALL_ZIPS" /> - <property file="${aggegate.zips.dir}/zip.list.txt" /> + <property file="${aggregate.zips.dir}/zip.list.txt" /> <if> <isset property="ALL_ZIPS" /> <then> @@ -104,24 +104,24 @@ <propertyregex override="true" property="buildPropertiesPath" defaultvalue="" input="@{zipPath}" regexp=".zip" replace=".build.properties" /> <propertyregex override="true" property="buildPropertiesPath" defaultvalue="${buildPropertiesPath}" input="${buildPropertiesPath}" regexp="-Sources-|-Update-" replace="-" /> - <mkdir dir="${aggegate.zips.dir}/${relativePath}" /> + <mkdir dir="${aggregate.zips.dir}/${relativePath}" />  <echo level="verbose">repoNum = @{repoNum} relativePath = ${relativePath} svnrevPath = ${svnrevPath} buildPropertiesPath = ${buildPropertiesPath} zipPath = @{zipPath} -DEST = ${aggegate.zips.dir}/@{zipPath} +DEST = ${aggregate.zips.dir}/@{zipPath} </echo> <echo> Zip URL = ${location.cleaned}/@{zipPath}</echo> <if> <isset property="isTest" /> <then> - <touch file="${aggegate.zips.dir}/@{zipPath}" /> + <touch file="${aggregate.zips.dir}/@{zipPath}" /> </then> <else> <var name="wget.return" unset="true" /> - <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="false" resultproperty="wget.return" outputproperty="null"> + <exec executable="wget" dir="${aggregate.zips.dir}" failonerror="false" failifexecutionfails="false" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/@{zipPath} -q --no-clobber" /> </exec> <if> @@ -134,24 +134,24 @@ </if> </else> </if> - +  <if> <available file="${svnRevTXT}" type="file" /> <then> - <copy file="${svnRevTXT}" tofile="${aggegate.zips.dir}/${svnrevPath}.txt" /> + <copy file="${svnRevTXT}" tofile="${aggregate.zips.dir}/${svnrevPath}.txt" /> </then> </if> <if> <available file="${svnRevXML}" type="file" /> <then> - <copy file="${svnRevXML}" tofile="${aggegate.zips.dir}/${svnrevPath}.xml" /> + <copy file="${svnRevXML}" tofile="${aggregate.zips.dir}/${svnrevPath}.xml" /> </then> </if> <if> <available file="${buildProperties}" type="file" /> <then> - <copy file="${buildProperties}" tofile="${aggegate.zips.dir}/${buildPropertiesPath}.txt" /> + <copy file="${buildProperties}" tofile="${aggregate.zips.dir}/${buildPropertiesPath}.txt" /> </then> </if> </sequential> @@ -162,16 +162,15 @@ </then> </if> <var unset="true" name="ALL_ZIPS" /> - <delete file="${aggegate.zips.dir}/zip.list.txt" quiet="true" /> </then> <else> <echo> ** Error [${wget.return}] ** Could not wget ${location.cleaned}/logs/zip.list.txt</echo> </else> </if> <var name="location.cleaned" unset="true" /> - <delete file="${svnRevXML}" quiet="true" /> - <delete file="${svnRevTXT}" quiet="true" /> - <delete file="${buildProperties}" quiet="true" /> + <delete quiet="true"> + <fileset dir="${aggregate.zips.dir}" includes="zip.list.txt, SVN_REVISION.txt, SVN_REVISION.xml, build.properties" /> + </delete> <var name="svnRevFile" unset="true" /> </sequential> </macrodef> @@ -185,17 +184,17 @@ <echo level="verbose">repo = @{repo}</echo>  <var name="wget.return" unset="true" /> - <exec executable="wget" dir="${aggegate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> + <exec executable="wget" dir="${aggregate.zips.dir}" failonerror="false" failifexecutionfails="true" resultproperty="wget.return" outputproperty="null"> <arg line="@{repo}/compositeArtifacts.xml -q --no-clobber" /> </exec> <if> <and> <equals arg1="${wget.return}" arg2="0" /> - <available file="${aggegate.zips.dir}/compositeArtifacts.xml" type="file" /> + <available file="${aggregate.zips.dir}/compositeArtifacts.xml" type="file" /> </and> <then> - <echo level="verbose">Got ${aggegate.zips.dir}/compositeArtifacts.xml</echo> - <xmlproperty file="${aggegate.zips.dir}/compositeArtifacts.xml" validate="false" collapseAttributes="true" /> + <echo level="verbose">Got ${aggregate.zips.dir}/compositeArtifacts.xml</echo> + <xmlproperty file="${aggregate.zips.dir}/compositeArtifacts.xml" validate="false" collapseAttributes="true" /> <echo level="verbose">Found ${repository.children.size} contained repos to search</echo>  <for param="location" list="${repository.children.child.location}"> @@ -204,7 +203,7 @@ <fetchZipsFromList repo="@{location}" /> </sequential> </for> - <delete file="${aggegate.zips.dir}/compositeArtifacts.xml" quiet="true" /> + <delete file="${aggregate.zips.dir}/compositeArtifacts.xml" quiet="true" /> </then> <else> <echo> ** Error [${wget.return}] ** Could not wget @{repo}/compositeArtifacts.xml</echo> @@ -342,9 +341,9 @@  <target name="collect.zips" description="collect zips from the sites we aggregated"> - <property name="aggegate.zips.dir" value="${output.dir}/zips" /> - <delete dir="${aggegate.zips.dir}" quiet="true" /> - <mkdir dir="${aggegate.zips.dir}" /> + <property name="aggregate.zips.dir" value="${output.dir}/zips" /> + <delete dir="${aggregate.zips.dir}" quiet="true" /> + <mkdir dir="${aggregate.zips.dir}" /> <for list="${inputRepos}" delimiter=", " keepgoing="true" param="repoNum"> <sequential> <var name="repo" value="${inputRepo@{repoNum}}" /> @@ -409,11 +408,11 @@ </target> <target name="test.collect.zips" depends="test.collect.zips.from.metadata,test.collect.zips.from.list.txt,test.collect.zips.from.list.xml"> - <delete dir="${aggegate.zips.dir}" quiet="true" /> + <delete dir="${aggregate.zips.dir}" quiet="true" /> </target> <target name="test.collect.zips.with.error" depends="test.collect.zips.from.metadata.with.errors,test.collect.zips.from.list.with.errors"> - <delete dir="${aggegate.zips.dir}" quiet="true" /> + <delete dir="${aggregate.zips.dir}" quiet="true" /> </target> <target name="collect.metadata" description="collect svn revision files + other metadata (JOB_NAME, BUILD_ID, BUILD_NUMBER, WORKSPACE, HUDSON_SLAVE)">

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28424 - trunk/drools/docs/guvnor_ref/en-US.

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-19 23:31:18 -0500 (Wed, 19 Jan 2011) New Revision: 28424 Modified: trunk/drools/docs/guvnor_ref/en-US/functionality_overview.xml Log: General Updates Modified: trunk/drools/docs/guvnor_ref/en-US/functionality_overview.xml =================================================================== --- trunk/drools/docs/guvnor_ref/en-US/functionality_overview.xml 2011-01-20 04:19:02 UTC (rev 28423) +++ trunk/drools/docs/guvnor_ref/en-US/functionality_overview.xml 2011-01-20 04:31:18 UTC (rev 28424) @@ -1,349 +1,299 @@ <?xml version='1.0' encoding='UTF-8'?> <chapter id="functionality_overview"> - <?dbhtml filename="functionality_overview.html"?> - <chapterinfo> - <keywordset> - <keyword>JBoss Tools</keyword> - <keyword>Eclipse Guvnor Tools</keyword> - </keywordset> - </chapterinfo> + <?dbhtml filename="functionality_overview.html"?> + <chapterinfo> + <keywordset> + <keyword>JBoss Tools</keyword> + <keyword>Eclipse Guvnor Tools</keyword> + </keywordset> + </chapterinfo> - <title>Tasks</title> + <title>Tasks</title> - <para>This chapter will give an overview on all functionality the <property>Guvnor Tools</property> provides.</para> - - <section > - <title>Creating a New Guvnor Connection</title> - <para>As mentioned in the <xref linkend="introduction"/>, the main purpose - of the <property>EGT</property> is to allow development using resources held in a Guvnor - repository. The first task is to make a connection to a Guvnor repository. - This is handled by the <xref linkend="connection_wizard"/>. </para> - </section> - - <section id="local_copies"> - <title>Getting Local Copies of Guvnor Files</title> - <para>There are two methods of getting local copies of Guvnor repository - resources:</para> + <para>This chapter will give an overview on all functionality the <property>Guvnor Tools</property> provides.</para> - <orderedlist> - <listitem> - <para>Drag-and-drop from the <xref linkend="guvnor_repositories_view"/></para> - </listitem> - <listitem> - <para>Using the <xref linkend="resources_from_guvnor"/>, as described further in this document</para> - </listitem> - </orderedlist> + <section> + <title>Creating a New Guvnor Connection</title> + <para> + As mentioned in the <xref linkend="introduction"/> section, the main purposeof the <property>EGT</property> is to allow development using resources held in a Guvnor repository. The first task is to make a connection to a Guvnor repository. This is handled by the <guilabel>Connection Wizard</guilabel> (see <xref linkend="connection_wizard"/>). + </para> + </section> - <para>When local copies of Guvnor repository files are created, the <property>EGT</property> - sets an association between the local copy and the master file in the repository. This - information is kept in the (normally) hidden <emphasis> - <property>.guvnorinfo</property> - </emphasis> folder in the local project and, like all metadata, should not be changed by - end users.</para> + <section id="local_copies"> + <title>Getting Local Copies of Guvnor Files</title> + <para>There are two methods of getting local copies of Guvnor repository resources:</para> - <figure> - <title>.guvnorinfo metadata</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/guvnorinfo.png"/> - </imageobject> - </mediaobject> - </figure> + <orderedlist> + <listitem> + <para>Drag-and-drop from the Guvnor Repositories View, as described in the <xref linkend="guvnor_repositories_view"/> section</para> + </listitem> + <listitem> + <para>Using the Resource from Guvnor Wizard, as described in the <xref linkend="resources_from_guvnor"/> section</para> + </listitem> + </orderedlist> - <para>The association allows for operations such as update and commit in - synchronization with the master copy held in the Guvnor repository.</para> + <para> + When local copies of Guvnor repository files are created, the <property>EGT</property> sets an association between the local copy and the master file in the repository. This information is kept in the (normally) hidden <filename>.guvnorinfo</filename> folder in the local project and, like all metadata, should not be changed by end users. + </para> + + <figure> + <title>.guvnorinfo metadata</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/guvnorinfo.png"/> + </imageobject> + </mediaobject> + </figure> + + <para> + The association allows for operations such as update and commit in synchronization with the master copy held in the Guvnor repository. + </para> - <para>The <property>EGT</property> decorates local resources associated with Guvnor - repository master copies. This decoration appears in Eclipse views conforming to the - Eclipse Common Navigator framework, such as the Eclipse <property>Resource - Navigator</property> and the Java <property>Package Explorer</property>. On the image - above you can see the <emphasis> - <property>Dummy rule.drl</property></emphasis> file with the decoration in the <property>Resource Navigator</property>. The Guvnor icon decorator is on the top right of the file image, and the Guvnor - revision details are appended to the file name. (The presence/location of these can be - changed in the <xref linkend="resource_decoration_preferences"/>.)</para> + <para> + The <property>EGT</property> decorates local resources associated with Guvnor repository master copies. This decoration appears in Eclipse views conforming to the Eclipse Common Navigator framework, such as the Eclipse <guilabel>Resource Navigator</guilabel> and the Java <guilabel>Package Explorer</guilabel>. In the image above you can see the <filename>Dummy rule.drl</filename> file with the decoration in the <guilabel>Resource Navigator</guilabel>. The Guvnor icon decorator is on the top right of the file image, and the Guvnor revision details are appended to the file name. The presence/location of these can be changed in the <guilabel>Local Guvnor Repository Resource Decoration Preferences</guilabel> (see the <xref linkend="resource_decoration_preferences"/> section). + </para> - <para>Here we see that, <emphasis><property>Dummy rule.drl</property></emphasis> is associated with a Guvnor repository - resource and the local copy is based on revision 0, with a <code>02-10-2008, 4:21:53</code> date/time - stamp. The file <emphasis><property>Sample.drl</property>,</emphasis> however, is not associated with a Guvnor repository - file. Further details about the association can be found in the standard Eclipse - properties page, accessed via the <emphasis><property>Properties</property></emphasis> option in the context menu:</para> + <para> + Here we see that the <filename>Dummy rule.drl</filename> file is associated with a Guvnor repository resource and the local copy is based on revision 0, with a <code>02-10-2008, 4:21:53</code> date/time stamp. However, the file <filename>Sample.drl</filename> is not associated with a Guvnor repository file. Further details about the association can be found in the standard Eclipse properties page, accessed via the <guilabel>Properties</guilabel> option in the context menu: + </para> + + <figure> + <title>Association Details</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/association_details.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Association Details</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/association_details.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + The <property>EGT</property> adds a property page to the standard Eclipse properties dialog, the contents of which are shown above. It displays the specific Guvnor repository, the location within the repository, the version (date/time stamp) and the revision number. + </para> + </section> - <para>The <property>EGT</property> contributes a property page to the standard Eclipse - properties dialog, the contents of which are shown above. It displays the specific Guvnor - repository, the location within the repository, the version (date/time stamp) and - the revision number.</para> - </section> - - <section id="actions"> - <title>Managing Guvnor Resources</title> + <section id="actions"> + <title>Managing Guvnor Resources</title> - <para>The <property>EGT</property> provides a number of actions (available through the - <emphasis><property>Guvnor</property></emphasis> context menu on files) for working with files, both those associated with - Guvnor repository master copies and those not associated. The actions are:</para> + <para> + The <property>EGT</property> provides a number of actions (available through the <guilabel>Guvnor</guilabel> context menu on files) for working with files, both those associated with Guvnor repository master copies and those not associated. The actions are: + </para> - <itemizedlist> - <listitem> - <para> - <xref linkend="update_action"/> - </para> - </listitem> - <listitem> - <para> - <xref linkend="add_action"/> - </para> - </listitem> - <listitem> - <para> - <xref linkend="commit_action"/> - </para> - </listitem> - <listitem> - <para> - <xref linkend="show_history_action"/> - </para> - </listitem> - <listitem> - <para> - <xref linkend="compare_with_version"/> - </para> - </listitem> - <listitem> - <para> - <xref linkend="switch_to_version"/> - </para> - </listitem> - <listitem> - <para> - <xref linkend="delete_action"/> - </para> - </listitem> - <listitem> - <para> - <xref linkend="disconnect_action"/> - </para> - </listitem> - </itemizedlist> + <itemizedlist> + <listitem> + <para> + <xref linkend="update_action"/> + </para> + </listitem> + <listitem> + <para> + <xref linkend="add_action"/> + </para> + </listitem> + <listitem> + <para> + <xref linkend="commit_action"/> + </para> + </listitem> + <listitem> + <para> + <xref linkend="show_history_action"/> + </para> + </listitem> + <listitem> + <para> + <xref linkend="compare_with_version"/> + </para> + </listitem> + <listitem> + <para> + <xref linkend="switch_to_version"/> + </para> + </listitem> + <listitem> + <para> + <xref linkend="delete_action"/> + </para> + </listitem> + <listitem> + <para> + <xref linkend="disconnect_action"/> + </para> + </listitem> + </itemizedlist> - <para>Each of these actions is described below.</para> + <para>Each of these actions is described below.</para> - <section id="update_action"> - <title>Update Action</title> + <section id="update_action"> + <title>Update Action</title> - <para>The <emphasis> - <property>Update</property> - </emphasis> action is available for one or more Guvnor resources that are not in - synchronization with the Guvnor repository master copies. These resources would not - be in synchronization because either/both</para> + <para> + The <guilabel>Update</guilabel> action is available for one or more Guvnor resources that are not in synchronization with the Guvnor repository master copies. These resources would not be in synchronization due to one or or both of the following conditions: + </para> + + <orderedlist> + <listitem> + <para>There are local changes to these resources</para> + </listitem> + <listitem> + <para>The master copies have been changed in the Guvnor repository</para> + </listitem> + </orderedlist> - <orderedlist> - <listitem><para>There are local changes to these - resources</para></listitem> - <listitem><para>The master copies have been changed in the Guvnor repository</para></listitem> - </orderedlist> + <para> + Performing the <guilabel>Update</guilabel> action replaces the local file contents with the current contents from the Guvnor repository master copies (equivalent to <xref linkend="switch_to_version"/> for the latest version). + </para> + </section> - <para>Performing the <emphasis> - <property>Update</property> - </emphasis> action replaces the local file contents with the current contents from - the Guvnor repository master copies (equivalent to <emphasis> - <xref linkend="switch_to_version"/> - </emphasis> for the latest version).</para> - </section> + <section id="add_action"> + <title>Add Action</title> - <section id="add_action"> - <title>Add Action</title> + <para>The <guilabel>Add</guilabel> action is available for one or more local files that are not associated with a Guvnor repository master copy. Choosing the <guilabel>Add</guilabel> action launches the <guilabel>Add to Guvnor wizard</guilabel>:</para> + + <figure> + <title>Add to Guvnor Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/add_toGuvnor_wizard.png"/> + </imageobject> + </mediaobject> + </figure> - <para>The <emphasis> - <property>Add</property> - </emphasis> action is available for one or more local files that are not associated - with a Guvnor repository master copy. Choosing the <emphasis> - <property>Add</property> - </emphasis> action launches the <property>Add to Guvnor wizard</property>:</para> + <para> + The first page of the wizard asks for the selection of the target Guvnor repository and gives the choice to create a new Guvnor repository connection (in which case the second page is the same as the <xref linkend="guvnor_connection_wizard"/>). Once the target Guvnor repository is chosen, the wizard then asks for the folder location to add the selection files: + </para> + + <figure> + <title>Selecting a Target Folder</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/select_target_folder.png"/> + </imageobject> + </mediaobject> + </figure> - <figure> - <title>Add to Guvnor Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/add_toGuvnor_wizard.png"/> - </imageobject> - </mediaobject> - </figure> + <para>Here the <filename>"defaultPackage"</filename> folder is selected as the destination location.</para> - <para>The first page of the wizard asks for the selection of the target Guvnor - repository and gives the choice to create a new Guvnor repository connection (in - which case the second page is the same as the <xref linkend="guvnor_connection_wizard"/>). Once the target Guvnor repository is chosen, - the wizard then asks for the folder location to add the selection files:</para> + <note> + <title>Note:</title> + <para> + Note that the <filename>"snapshot"</filename> folder in the Guvnor repository is read-only for <property>EGT</property>, and hence not visible as a candidate location in this wizard. The Guvnor repository web administration tools must be used to add snapshot content. + </para> + </note> - <figure> - <title>Selecting a Target Folder</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/select_target_folder.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + Clicking on the <guibutton>Finish</guibutton> adds the selected files to the Guvnor repository and creates an association between the local and Guvnor repository files. + </para> - <para>Here the <emphasis> - <property>"defaultPackage"</property></emphasis> folder is selected as the destination - location.</para> + <note> + <title>Note:</title> + <para>Note that the wizard will not allow for overwrite of existing Guvnor repository files. Another target location must be chosen.</para> + </note> + </section> - <note> - <title>Note:</title> - <para>Note that the <emphasis> - <property>"snapshot"</property></emphasis> folder in the Guvnor repository is read-only for - <property>EGT</property>, and hence not visible as a candidate location in - this wizard. The Guvnor repository web administration tools must be used to add - snapshot content.</para> - </note> + <section id="commit_action"> + <title>Commit Action</title> - <para>Clicking on <emphasis> - <property>Finish</property> - </emphasis> adds the selected files to the Guvnor repository and creates an - association between the local and Guvnor repository files.</para> + <para> + The <guilabel>Commit</guilabel> action is enabled for one or more Guvnor repository associated files that have local changes. The <guilabel>Commit</guilabel> action will write the local changes back to the associated Guvnor repository files and update the association for the new revision created. + </para> - <note> - <title>Note:</title> - <para>Note that the wizard will not allow for overwrite of existing Guvnor - repository files. Another target location must be chosen.</para> - </note> - </section> + <para> + If a local change is based on an older revision of a file that is currently in the Guvnor repository (for example, someone else changed the same file), then the <guilabel>Commit</guilabel> action will ask whether you wish to overwrite the current version in the Guvnor repository with the local content. When such conflicts occur, however, you should use the Eclipse Guvnor version tools, along with Eclipse standard tools, to determine the differences and merge content based on the current version in the Guvnor repository. + </para> + </section> - <section id="commit_action"> - <title>Commit Action</title> + <section id="show_history_action"> + <title>Show History Action</title> - <para>The <emphasis> - <property>Commit</property> - </emphasis> action is enabled for one or more Guvnor repository associated files - that have local changes. The <emphasis> - <property>Commit</property> - </emphasis> action will write the local changes back to the associated Guvnor - repository files and update the association for the new revision created.</para> + <para> + The <guilabel>Show History</guilabel> action is enabled for one Guvnor repository associated file and causes the <xref linkend="guvnor_history_view"/> to be populated with revision history for the selected file. + </para> + </section> - <para>If a local change is based on an older revision of a file that is currently in the - Guvnor repository (for example, someone else changed the same file), then the <emphasis> - <property>Commit</property> - </emphasis> action will ask whether you wish to overwrite the current version in the - Guvnor repository with the local content. When such conflicts occur, however, you - should use the Eclipse Guvnor version tools, along with Eclipse standard tools, to - determine the differences and merge content based on the current version in the - Guvnor repository.</para> - </section> + <section id="compare_with_version"> + <title>Compare with Version Action</title> - <section id="show_history_action"> - <title>Show History Action</title> + <para> + The <guilabel>Compare with Version</guilabel> action is enabled for one Guvnor repository associated file. This action first opens a wizard asking for the version for comparison (with the local file contents): + </para> + + <figure> + <title>Compare with Version Wizard</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/compare_with_version.png"/> + </imageobject> + </mediaobject> + </figure> - <para>The <emphasis> - <property>Show History</property> - </emphasis> action is enabled for one Guvnor repository associated file and causes - the <xref linkend="guvnor_history_view"/> to be - populated with revision history for the selected file.</para> - </section> + <para>Once the revision is selected, the action opens the Eclipse <guilabel>Compare editor</guilabel> (read-only):</para> + <figure> + <title>Eclipse Compare Editor</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/compare_with_version2.png"/> + </imageobject> + </mediaobject> + </figure> - <section id="compare_with_version"> - <title>Compare with Version Action</title> + <guilabel> + This editor uses Eclipse-standard comparison techniques to show the differences in the two versions. In cases where there are no differences, the editor will not open, rather a dialog saying that there are no differences will appear. + </guilabel> + <figure> + <title>Alert Dialog</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/compare_with_version3.png"/> + </imageobject> + </mediaobject> + </figure> + </section> - <para>The <emphasis> - <property>Compare with Version</property> - </emphasis> action is enabled for one Guvnor repository associated file. This action - first opens a wizard asking for the version for comparison (with the local file - contents):</para> + <section id="switch_to_version"> + <title>Switch to Version Action</title> - <figure> - <title>Compare with Version Wizard</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/compare_with_version.png"/> - </imageobject> - </mediaobject> - </figure> + <para>The <guilabel>Switch to Version</guilabel> action is enabled for one Guvnor repository associated file.</para> + <para>First the <guilabel>Switch to Version</guilabel> action prompts for selection of version:</para> + + <figure> + <title>Select Version Window</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/compare_with_version.png"/> + </imageobject> + </mediaobject> + </figure> - <para>Once the revision is selected, the action opens the Eclipse <property>Compare - editor</property> (read-only):</para> - <figure> - <title>Eclipse Compare Editor</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/compare_with_version2.png"/> - </imageobject> - </mediaobject> - </figure> + <para> + Once the version is selected, the <guilabel>Switch to Version</guilabel> action replaces the local file contents with those from the revision selected. + </para> + </section> - <para>This editor uses Eclipse-standard comparison techniques to show the differences in - the two versions. In cases where there are no differences, the editor will not open, - rather a dialog saying that there are no differences will appear.</para> - <figure> - <title>Alert Dialog</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/compare_with_version3.png"/> - </imageobject> - </mediaobject> - </figure> - </section> + <section id="delete_action"> + <title>Delete Action</title> - <section id="switch_to_version"> - <title>Switch to Version Action</title> + <para> + The <guilabel>Delete</guilabel> action is enabled for one or more Guvnor repository associated files. After confirmation via a dialog, the <guilabel>Delete</guilabel> action removes the files in the Guvnor repository and deletes local metadata for the Guvnor repository association. + </para> + + <figure> + <title>Comfirm Delete Dialog</title> + <mediaobject> + <imageobject> + <imagedata fileref="images/functionality_overview/confirm_delete.png"/> + </imageobject> + </mediaobject> + </figure> + </section> - <para>The <emphasis> - <property>Switch to Version</property> - </emphasis> action is enabled for one Guvnor repository associated file.</para> - <para>First the <emphasis> - <property>Switch to Version</property> - </emphasis> action prompts for selection of version:</para> + <section id="disconnect_action"> + <title>Disconnect Action</title> - <figure> - <title>Select Version Window</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/compare_with_version.png"/> - </imageobject> - </mediaobject> - </figure> - - <para>Once the version is selected, the <emphasis> - <property>Switch to Version</property> - </emphasis> action replaces the local file contents with those from the revision - selected.</para> - </section> - - <section id="delete_action"> - <title>Delete Action</title> - - <para>The <emphasis> - <property>Delete</property> - </emphasis> action is enabled for one or more Guvnor repository associated files. - After confirmation via a dialog, the <emphasis> - <property>Delete</property> - </emphasis> action removes the files in the Guvnor repository and deletes local - metadata for the Guvnor repository association.</para> - - <figure> - <title>Comfirm Delete Dialog</title> - <mediaobject> - <imageobject> - <imagedata fileref="images/functionality_overview/confirm_delete.png"/> - </imageobject> - </mediaobject> - </figure> - </section> - - <section id="disconnect_action"> - <title>Disconnect Action</title> - - <para>The <emphasis> - <property>Disconnect</property> - </emphasis> action is enabled for one or more Guvnor repository associated files, - and removes local metadata for the Guvnor repository association.</para> - </section> - </section> + <para> + The <guilabel>Disconnect</guilabel> action is enabled for one or more Guvnor repository associated files, and removes local metadata for the Guvnor repository association. + </para> + </section> + </section> - + </chapter>

15 years, 2 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 January 2011