January 2011 - jbosstools-commits

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

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-20 20:20:16 -0500 (Thu, 20 Jan 2011) New Revision: 28453 Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-21 01:02:16 UTC (rev 28452) +++ trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-21 01:20:16 UTC (rev 28453) @@ -760,7 +760,7 @@ </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 the <guiButton>setup</guiButton> button allows you to select an existing <filename>reveng.xml</filename> file or create a new one. See more details about the <filename>reveng.xml</filename> file in <xref linkend="reverseengineering"/>. + 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 the <guibutton>setup</guibutton> button allows you to select an existing <filename>reveng.xml</filename> file or create a new one. See more details about the <filename>reveng.xml</filename> file in <xref linkend="reverseengineering"/>. </para> </entry> </row> @@ -2094,8 +2094,7 @@ </para> <itemizedlist> <listitem> - <para> - <code>@Column<code> is added to all String properties.</para> + <para><code>@Column</code> is added to all String properties.</para> </listitem> <listitem> <para> @@ -2187,32 +2186,28 @@ It is possible to configure the Eclipse plugin to route all logging made by the plugins and hibernate code it self to the <guilabel>Error Log View</guilabel> 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 <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> + The <guilabel>Error Log View</guilabel> is very useful tool to help solve any problem which appears in Hibernate Tools Plugins. You can use if there are troubles with setting up <guilabel>Hibernate Console Configuration</guilabel>. + </para> + <para> + This is done by editing the <filename>hibernate-log4j.properties</filename> file in the <filename>org.hibernate.eclipse/</filename> directory/jar. This file includes a default configuration that only logs WARN and above to a set of custom appenders (PluginFileAppender and PluginLogAppender). You can change these settings to be as verbose or silent as you please - see <ulink url="http://www.hibernate.org/5.html">Hibernate Documentation</ulink> for more information on logging categories and Log4j documentation. + </para> <section> <title>Relevant Resources Links</title> - <para>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> + <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> + <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 - <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> + <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 the <guilabel>JPA Perspective</guilabel>), the first wizard page is shwn in the image below. + </para> <figure> <title>Starting JPA Project</title> <mediaobject> @@ -2221,10 +2216,10 @@ </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 <guilabel>Add connection</guilabel> link.</para> + <para>You can select a target runtime and change the project configuration, or you can leave everything as it is.</para> + <para> + On the JPA Facet page you should choose <guilabel>Hibernate</guilabel> as a target platform. Also select the proper database connection, if it is defined, or add a new one by clicking the <guilabel>Add connection</guilabel> link. + </para> <para>Clicking the <guibutton>Finish</guibutton> button will generate the project.</para> <figure> <title>Targeting at Hibernate Platform</title> @@ -2236,19 +2231,16 @@ </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> + <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 <guilabel>Hibernate Tools</guilabel> 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 <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> + <para> + By enabling Hibernate platform specific features you can now generate DDL and Entities. To do that select the <menuchoice><guimenuitem>JPA Tools</guimenuitem><guimenuitem>Generate Tables from Entities/Generate Entities from Tables</guimenuitem></menuchoice> options in the context menu of your JPA project. + </para> <figure> <title>Generate DDL/Entities</title> <mediaobject> @@ -2259,11 +2251,9 @@ </figure> <note> <title>Note:</title> - <para>Please, remember to put the proper database driver to the classpath of your - project.</para> + <para>Please, remember to put the proper database driver to the classpath of your project.</para> </note> - <para>The <property>Generate Entities wizard</property> first will ask you to choose the - directory where all output will be written.</para> + <para>The <guilabel>Generate Entities wizard</guilabel> will first ask you to choose the directory where all output will be written.</para> <figure> <title>Generate Entities Wizard</title> <mediaobject> @@ -2276,11 +2266,9 @@ <itemizedlist> <listitem> <para>a Hibernate Console Configuration (proposed by default)</para> - <para>Just make sure that the <emphasis> - <property>Use Console Configuration</property> - </emphasis> checkbox is selected and choose a needed configuration from the <emphasis> - <property>Console configurations</property> - </emphasis> list box.</para> + <para> + Just make sure that the <guilabel>Use Console Configuration</guilabel> checkbox is selected and choose a needed configuration from the <guilabel>Console configurations</guilabel> list box. + </para> <figure> <title>Generate Entities Wizard</title> <mediaobject> @@ -2294,14 +2282,12 @@ <itemizedlist> <listitem> <para>or a DTP connection directly</para> - <para>Just uncheck <emphasis> - <property>Use Console Configuration</property> - </emphasis> and adjust database settings.</para> + <para>Just uncheck the <guilabel>Use Console Configuration</guilabel> option and adjust the 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> + <para> + The options you define in the <guilabel>Generate Entities Wizard</guilabel> can also be set with the <guilabel>Generate DDL wizard</guilabel>. The <guilabel>Generate DDL</guilabel> wizard also allows you automatically generate DDL for the database. + </para> <figure> <title>Generate DDL Wizard</title> <mediaobject> @@ -2314,12 +2300,12 @@ </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> + <para> + Hibernate Annotations are also supported in <guilabel>Dali Java Persistence Tools</guilabel>. The next annotations are integrated with <guilabel>JPA Details</guilabel> view: + </para> <itemizedlist> <listitem> - <para>Id Generator annotations - <property>@GenericGenerator</property> and <property>@GeneratedValue</property> + <para>Id Generator annotations - <code>@GenericGenerator</code> and <code>@GeneratedValue</code> </para> <figure> <title>@GenericGenerator support in Dali</title> @@ -2339,7 +2325,7 @@ </figure> </listitem> <listitem> - <para>Property annotations- <property>@DiscriminatorFormula</property>, <property>@Generated Annotation</property>, <property>@Index annotation</property> + <para>Property annotations- <code>@DiscriminatorFormula</code>, <code>@Generated Annotation</code>, <code>@Index annotation</code> </para> <figure> <title>@Index support in Dali</title> @@ -2351,7 +2337,7 @@ </figure> </listitem> <listitem> - <para>Mapping Queries annotations - <property>@NamedQuery</property> and <property>@NamedNativeQuery</property> + <para>Mapping Queries annotations - <code>@NamedQuery</code> and <code>@NamedNativeQuery</code> </para> <figure> <title>Add New Named Query Dialog with Hibernate Support</title> @@ -2371,7 +2357,9 @@ </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> + <para> + Association annotations in an <property>embeddable</property> object (<code>@OneToOne</code>, <code>@ManyToOne</code>, <code>@OneToMany</code> or <code>@ManyToMany</code>) + </para> <figure> <title>Hibernate Support for Embeddable Object</title> <mediaobject> @@ -2382,13 +2370,15 @@ </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> + <para> + More information about Hibernate Annotation can be found in the <ulink url="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html/">Hibernate Annotations Reference Guide</ulink>. + </para> </section> <section> <title>Relevant Resources Links</title> - <para>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> + <para> + More 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> </chapter>

15 years, 2 months

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-20 20:02:16 -0500 (Thu, 20 Jan 2011) New Revision: 28452 Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-21 00:39:59 UTC (rev 28451) +++ trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-21 01:02:16 UTC (rev 28452) @@ -1324,7 +1324,7 @@ Or you can get it via the <guilabel>Code Generation Launcher</guilabel> by checking the proper section in the <guilabel>Main</guilabel> tab of the <guilabel>Getting Hibernate Code Generation Wizard</guilabel> (see <xref linkend="hib_code_gen"/>). </para> <para> - The following screenshot shows the <guilabel>Overview</guilabel> page where the wanted console configuration is selected (auto-detected if Hibernate 3 support is enabled for the project) + The following screenshot shows the <guilabel>Overview</guilabel> page where the appropriate console configuration is selected (auto-detected if Hibernate 3 support is enabled for the project). </para> <figure> <title>Overview Page</title> @@ -1337,12 +1337,9 @@ </imageobject> </mediaobject> </figure> - <para>The <emphasis> - <property>Table Filter</property> - </emphasis> page allows you to specify which tables to include and exclude. Pressing - <emphasis> - <property>Refresh</property> - </emphasis> shows the tables from the database that have not yet been excluded.</para> + <para> + The <guilabel>Table Filter</guilabel> page allows you to specify which tables to include and exclude. Clicking the <guibutton>Refresh</guibutton> button shows the tables from the database that have not yet been excluded. + </para> <figure> <title>Table Filters Page</title> <mediaobject> @@ -1354,11 +1351,9 @@ </imageobject> </mediaobject> </figure> - <para>The <emphasis> - <property>Type Mappings</property> - </emphasis> page is used for specifying type mappings from JBDC types to any Hibernate type - (including usertypes) if the default rules are not applicable. Here again to see the database - tables press the <guibutton>Refresh</guibutton> button underneath. More about type mappings you can find further in the <xref linkend="type_map"/> section.</para> + <para> + The <guilabel>Type Mappings</guilabel> page is used to specify 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 the <guibutton>Refresh</guibutton> button underneath. For more information on type mappings please see the <xref linkend="type_map"/> section. + </para> <figure> <title>Type Mappings Page</title> <mediaobject> @@ -1370,11 +1365,9 @@ </imageobject> </mediaobject> </figure> - <para>The <emphasis> - <property>Table and Columns</property> - </emphasis> page allows you to explicit set e.g. which hibernatetype and propertyname that - should be used in the reverse engineered model. For more details on how to configure the - tables while reverse engineering read the <xref linkend="tab_and_col"/> section.</para> + <para> + The <guilabel>Table and Columns</guilabel> page allows you to explicit set which details (e.g. which hibernatetype and propertyname) should be used in the reverse engineered model. For more details on how to configure the tables while reverse engineering read the <xref linkend="tab_and_col"/> section. + </para> <figure> <title>Table and Columns Page</title> <mediaobject> @@ -1386,18 +1379,18 @@ </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> + <para>Now that you have configured all the necessary settings, 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> + <para> + The <guilabel>Hibernate Console Perspective</guilabel> 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 <guilabel>Hibernate Console Configuration</guilabel> (see <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> + <para> + To view your new configuration and entity/class structure, switch to the <guilabel>Hibernate Configurations View</guilabel>. Expanding the tree allows you to browse the class/entity structure and see the relationships. + </para> <figure> <title>Hibernate Console Perspective</title> <mediaobject> @@ -1409,17 +1402,12 @@ </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 <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> - <property>Open Mapping File</property> - </emphasis> to open a proper <filename>.hbm.xml</filename>. + <para> + The <guilabel>Console Configuration</guilabel> does not dynamically adjust to changes done in mappings and Java code. To reload the configuration select the configuration and click the <guibutton>Reload</guibutton> button in the view toolbar or in the context menu. </para> + <para> + It is possible to open source and mapping files for objects showed in the <guilabel>Hibernate Configurations View</guilabel>. Just bring up the context menu for a necessary object and select <guimenuitem>Open Source File</guimenuitem> to see appropriate Java class or <guimenuitem>Open Mapping File</guimenuitem> to open a proper <filename>.hbm.xml</filename> file. + </para> <figure> <title>Opening Source for Objects</title> <mediaobject> @@ -1430,10 +1418,8 @@ </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> + In order to visualize on how entities are related as well as view their structures, a <guilabel>Mapping Diagram</guilabel> is provided. It is available by right clicking on the entity you want view a mapping diagram for and then choosing <guilabel>Mapping Diagram</guilabel>. </para> <figure> <title>Mapping Diagram</title> @@ -1446,10 +1432,9 @@ </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> + <para> + To make <guilabel>Mapping Diagram</guilabel> usage easier you can use <guilabel>Rules</guilabel>, <guilabel>Grid</guilabel>, <guilabel>Snap to Geometry</guilabel> checkboxes in the <guimenu>View</guimenu> menu. + </para> <figure> <title>View menu</title> <mediaobject> @@ -1458,14 +1443,9 @@ </imageobject> </mediaobject> </figure> - <para>If you will select <emphasis> - <property>Rules</property> - </emphasis> checkbox, the view print page scale will be added to the page. The numbers on - the scale show its size in inches.If you click on the scale a <emphasis> - <property>Ruler Guide</property> - </emphasis> will appear on the diagram. You can connect any diagram item to it.To connect - the items you should move their tops to the Ruler Guide. And while moving the ruler guide, - the items will be moved together with it as a whole.</para> + <para> + If you will select <guilabel>Rules</guilabel> 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 <guilabel>Ruler Guide</guilabel> will appear on the diagram. You can connect any diagram item to it. To connect the items you should move their tops to the Ruler Guide. And while moving the ruler guide, the items will be moved together with it as a whole. + </para> <figure> <title>Moving the Ruler guide</title> <mediaobject> @@ -1474,9 +1454,7 @@ </imageobject> </mediaobject> </figure> - <para>If you'll select <emphasis> - <property>Grid</property> - </emphasis> checkbox, the grid will appear on the diagram.</para> + <para>If you select the <guilabel>Grid</guilabel> checkbox, the grid will appear on the diagram.</para> <figure> <title>Grid on Mapping diagram</title> <mediaobject> @@ -1485,11 +1463,8 @@ </imageobject> </mediaobject> </figure> - <para>The checkbox <emphasis> - <property>Snap to Geometry</property> - </emphasis> helps to put the items of the diagram into allineation with the grid.</para> - <para>For better navigating through the diagram use <property>Outline view</property> which - is available in the structural and graphical modes.</para> + <para>The checkbox <guilabel>Snap to Geometry</guilabel> helps to put the items of the diagram into alignment with the grid.</para> + <para>For better navigating through the diagram use <guilabel>Outline view</guilabel> which is available in the structural and graphical modes.</para> <figure> <title>Navigating in the Structural Mode</title> <mediaobject> @@ -1498,8 +1473,7 @@ </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> + <para>To switch over between the modes use the buttons in the top-right corner of the <guilabel>Outline view</guilabel>.</para> <figure> <title>Navigating in the Graphical Mode</title> <mediaobject> @@ -1508,8 +1482,7 @@ </imageobject> </mediaobject> </figure> - <para>The options in the context menu of the mapping diagram are listed in the next - table.</para> + <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"> @@ -1601,15 +1574,14 @@ <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>Allows the diagram to be exported as a <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> + <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> @@ -1653,8 +1625,9 @@ <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> + <para> + Makes it possible to open the source file for a chosen object or element. The selected element will be highlighted in the open file. + </para> </entry> </row> <row> @@ -1671,8 +1644,9 @@ <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> + <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> @@ -1706,7 +1680,7 @@ <para>Expand|Collapse shape(s)</para> </entry> <entry> - <para>Used for expanding/collapsing fields of the item</para> + <para>Used for expanding and collapsing fields of the item</para> </entry> </row> </tbody> @@ -1714,10 +1688,9 @@ </table> <note> <title>Tip:</title> - <para>All the described types of the context menu are also available in the <property>Outline</property> view.</para> + <para>All the described types of the context menu are also available in the <guilabel>Outline</guilabel> view.</para> </note> - <para>The below table lists the actions that could be performed using the keyboard keys (or - keys combinations).</para> + <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"> @@ -1750,7 +1723,7 @@ </row> <row> <entry> - <para>Collapse/Expand selected item(s)</para> + <para>Collapse or Expand selected item(s)</para> </entry> <entry> <para> @@ -1760,7 +1733,7 @@ </row> <row> <entry> - <para>Show/Hide selected item(s)</para> + <para>Show or Hide selected item(s)</para> </entry> <entry> <para> @@ -1770,7 +1743,7 @@ </row> <row> <entry> - <para>Sort items in alphabetical order or return the initial state</para> + <para>Sort items in alphabetical order or return to the initial state</para> </entry> <entry> <para> @@ -1791,12 +1764,9 @@ </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> + <para> + It is 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 <filename>.hibernate</filename> extension. + </para> <figure> <title>The Diagram saved in the Workspace</title> <mediaobject> @@ -1807,9 +1777,9 @@ </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> + <para> + If you restart Eclipse with the mapping diagram opened, the mapping diagram will be restored with the message like on the figure below. To view the diagram content, you should perform the refreshing. + </para> </note> <figure> <title>The Diagram after Restarting the Eclipse</title> @@ -1871,8 +1841,7 @@ <para>Refresh Visual Mapping</para> </entry> <entry> - <para>It update <property>Mapping Diagram</property> if <property>Console - Configuration</property> was changed. </para> + <para>It will update the <guilabel>Mapping Diagram</guilabel> the if <guilabel>Console Configuration</guilabel> was changed. </para> </entry> </row> <row> @@ -1889,8 +1858,9 @@ <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> + <para> + Used to define scale of the diagram. Also it's used for <guilabel>Mapping Diagram</guilabel> printing. If you want to put the whole <guilabel>diagram</guilabel> to one print page, you need select <guilabel>Page</guilabel> option in the <guilabel>Zoom Box</guilabel>. + </para> </entry> </row> <row> @@ -1924,10 +1894,9 @@ <para>Show|Hide connections</para> </entry> <entry> - <para>Used to show or hide connection on the diagram. Moreover you can choose what - type of connections must be present on the diagram (<property>Property - Mappings</property>, <property>Class Mappings</property>, <property>Associations</property> or <property>Foreign key constraints</property>) - .</para> + <para> + Used to show or hide a connection on the diagram. Moreover you can choose what type of connections must be present on the diagram (<guilabel>Property Mappings</guilabel>, <guilabel>Class Mappings</guilabel>, <guilabel>Associations</guilabel> or <guilabel>Foreign key constraints</guilabel>). + </para> </entry> </row> <row> @@ -1961,7 +1930,7 @@ <para> Show|Hide shape(s)</para> </entry> <entry> - <para>Used to hide/show an item on the mapping diagram.</para> + <para>Used to hide or show an item on the mapping diagram.</para> </entry> </row> </tbody> @@ -1971,15 +1940,14 @@ </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 <keycombo><keycap>Ctrl</keycap> - <keycap>Enter</keycap> - </keycombo>.</para> + <para> + Queries can be prototyped by entering them into the <guilabel>HQL</guilabel> or <guilabel>Criteria Editor</guilabel>. 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> <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> + <para> + To open the query editors right-click your projects <guilabel>Console Configuration</guilabel> and select <guimenuitem>HQL Editor</guimenuitem> (or <guimenuitem>Hibernate Criteria Editor</guimenuitem>). + </para> <figure> <title>Opening HQL Editor</title> <mediaobject> @@ -1990,23 +1958,17 @@ </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> + <para> + If the context menu items are disabled then you need at first to create a <guilabel>Session Factory</guilabel>. That is done by simply expanding the <guilabel>Session Factory</guilabel> node. + </para> </note> - <para>When open the editors they should automatically detect the chosen Console - Configuration.</para> - <para>To get a prefill query for any entity (or any entity child node) listed in the - <emphasis> - <property>Session Factory</property> - </emphasis> you should double-click it. This will open the <property>HQL Editor</property> - with the associated query.</para> - <para>Choosing <emphasis> - <property>HQL Editor</property> - </emphasis> in the context menu for any entity (or any entity child node) will also open - the HQL editor with the associated query. If you choose <emphasis> - <property>Hibernate Criteria Editor</property> - </emphasis> in the context menu, it will open <property>Hibernate Criteria - Editor</property> with the associated criteria.</para> + <para>When open the editors they should automatically detect the chosen <guilabel>Console Configuration</guilabel>.</para> + <para> + To get a prefill query for any entity (or any entity child node) listed in the <guilabel>Session Factory</guilabel> you should double-click it. This will open the <guilabel>HQL Editor</guilabel> with the associated query. + </para> + <para> + Choosing <guimenuitem>HQL Editor</guimenuitem> in the context menu for any entity (or any entity child node) will also open the HQL editor with the associated query. If you choose <guimenuitem>Hibernate Criteria Editor</guimenuitem> in the context menu, it will open <guilabel>Hibernate Criteria Editor</guilabel> with the associated criteria. + </para> <figure> <title>Generating Simple Queries</title> <mediaobject> @@ -2019,10 +1981,7 @@ </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 is also possible to copy a portion of code from a <filename>.java</filename> file into the <guilabel>HQL</guilabel> or <guilabel>Criteria editor</guilabel>. To do this make use of the Quick Fix option (<keycombo><keycap>Ctrl</keycap><keycap>1</keycap></keycombo>). </para> <figure> <title>Quick Fix Option Demonstration</title> @@ -2032,9 +1991,9 @@ </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> + <para> + You can also update the original java code with changes made in the HQL or Criteria editor. For that you should save your HQL/Criteria query and submit the replacing in appeared confirmation dialog. + </para> <figure> <title>Updating Java Code</title> <mediaobject> @@ -2043,19 +2002,12 @@ </imageobject> </mediaobject> </figure> - <para>Also you can pin <property>HQL editor</property> and <property>Criteria - editor</property> for one tab in <property>Hibernate Query Result</property> view. For - that you need click on <property>Stick result to one tab</property> - button(<inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/sticky_but.png"/> - </imageobject> - </inlinemediaobject> ). In the issue query executions results will be shown in one tab (no - more will be opened). </para> - <para> Moreover you are able to rename tab in <property>Hibernate Query Result</property>. - Click the tab, and type a new name in <menuchoice><guimenuitem>Property View</guimenuitem> - <guimenuitem>Tab name field</guimenuitem> - </menuchoice>. </para> + <para> + Also you can pin the <guilabel>HQL editor</guilabel> and <guilabel>Criteria editor</guilabel> as a tab in the <property>Hibernate Query Result</property> view. For that you need click on <guibutton>Stick result to one tab</guibutton> button (<inlinemediaobject><imageobject><imagedata fileref="images/plugins/sticky_but.png"/></imageobject></inlinemediaobject>). In this state query executions results will be shown in one tab (no more will be opened). + </para> + <para> + Moreover you are able to rename tab in <guilabel>Hibernate Query Result</guilabel>. 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> @@ -2067,26 +2019,24 @@ </section> <section> <title>Error Handling</title> - <para>Errors during creation of the <property>Session Factory</property> or running the - queries (e.g. if your configuration or query is incorrect) will be shown in a message - dialog or inclined in the view that detected the error, you may get more information about - the error in the <property>Error Log View</property> on the right pane.</para> - <para>Results of a query will be shown in the <property>Hibernate Query Result - View</property> and details of possible errors (syntax errors, database errors, etc.) - can be seen in the <property>Error Log View</property>.</para> + <para> + Errors raised during the creation of the <guilabel>Session Factory</guilabel> 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 <guilabel>Error Log View</guilabel> on the right pane. + </para> + <para> + Results of a query will be shown in the <guilabel>Hibernate Query Result View</guilabel> and details of possible errors (syntax errors, database errors, etc.) can be seen in the <guilabel>Error Log View</guilabel>. + </para> <note> <title>Note:</title> - <para>HQL queries are executed by default using <literal>list()</literal> thus without any - limit of the size of the output the query could return a large result set. You might run - out of memory. To avoid this you can put a value in the Max results field to reduce the - number of elements returned.</para> + <para> + HQL queries are executed by default using the <code>list()</code> function thus without any row limit could return a large result set. You might run out of memory. To avoid this you can put a value in the <guilabel>Max</guilabel> results field to reduce the number of elements returned. + </para> </note> </section> <section> <title>Dynamic Query Translator</title> - <para>If the <property>Hibernate Dynamic Query Translator View</property> is visible while - writing in the <property>HQL Editor</property> it will show the generated SQL for a HQL - query.</para> + <para> + If the <guilabel>Hibernate Dynamic Query Translator View</guilabel> is visible while writing in the <guilabel>HQL Editor</guilabel> it will show the generated SQL for a HQL query. + </para> <figure> <title>Hibernate Dynamic Query Translator View</title> <mediaobject> @@ -2098,14 +2048,16 @@ </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> + <para> + The translation is performed each time you stop typing into the editor. If there are errors in the HQL the parse exception will be shown embedded in the view. + </para> </section> </section> <section> <title>Properties View</title> - <para>As you can see on the figure,when clicking on class/entity <property>Properties - view</property> shows the number of query results as well as the time of executing.</para> + <para> + As you can see in the figure below, when clicking on class/entity the <guilabel>Properties view</guilabel> shows the number of query results as well as the execution time. + </para> <figure> <title>Properties View</title> <mediaobject> @@ -2117,7 +2069,9 @@ </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> + <para> + It also displays the structure of any persistent object selected in the <guilabel>Hibernate Query Results View</guilabel>. Editing is not yet supported. + </para> <figure> <title>Properties View for Selected Object</title> <mediaobject> @@ -2129,91 +2083,51 @@ </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> + <para> + You can also use <guilabel>Properties view</guilabel> when clicking on the configuration itself in Hibernate Configuration View (see <xref linkend="modif_console_conf"/>). + </para> </section> </section> <section id="jpa_annotations"> <title>Hibernate:add JPA annotations refactoring </title> - <para>Using this wizard you can add the next Hibernate annotations to the class: <emphasis> - <property>@Column</property> - </emphasis>,<emphasis> - <property>@Entity</property> - </emphasis>,<emphasis> - <property>@ManyToOne</property> - </emphasis>,<emphasis> - <property>@OneToMany</property> - </emphasis>,<emphasis> - <property>@OneToOne</property> - </emphasis>,<emphasis> - <property>@ManyToMany</property> - </emphasis>,<emphasis> - <property>@MappedSuperclass</property> - </emphasis>,<emphasis> - <property>@Id</property> - </emphasis>,<emphasis> - <property>@GeneratedValue</property> - </emphasis> ,<emphasis> - <property>@Version </property> - </emphasis> + <para>Using this wizard you can add the next Hibernate annotations to the class: <code>@Column</code>, <code>@Entity</code>, <code>@ManyToOne</code>, <code>@OneToMany</code>, <code>@OneToOne</code>, <code>@ManyToMany</code>, <code>@MappedSuperclass</code>, <code>@Id</code>, <code>@GeneratedValue</code>, <code>@Version </code> </para> <itemizedlist> <listitem> <para> - <emphasis> - <property>@Column</property> - </emphasis> is added to all String properties.</para> + <code>@Column<code> 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> + <code>@Entity</code> is always declared before any class where it doesn't present.</para> </listitem> <listitem> <para> - <emphasis> - <property>@ManyToOne</property> - </emphasis>,<emphasis> - <property>@OneToMany</property> - </emphasis>,<emphasis> - <property>@OneToOne</property> - </emphasis>,<emphasis> - <property>@ManyToMany</property> - </emphasis> - this annotations are declared according to the classes hierarchy.</para> + <code>@ManyToOne</code>, <code>@OneToMany</code>, <code>@OneToOne</code>, <code>@ManyToMany</code> - this annotations are declared according to the classes hierarchy. + </para> </listitem> <listitem> <para> - <emphasis> - <property>@MappedSuperclass</property> - </emphasis> is added to abstract superclasses.</para> + <code>@MappedSuperclass</code> is added to abstract superclasses.</para> </listitem> <listitem> <para> - <emphasis> - <property>@Id</property> - </emphasis>,<emphasis> - <property>@GeneratedValue</property> - </emphasis> are added automatically only to the properties under the name "Id",where they - don't present.</para> + <code>@Id</code>, <code>@GeneratedValue</code> 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> + <code>@Version</code> 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> + <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 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> @@ -2224,7 +2138,7 @@ </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. + 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 <guilabel>Add classes and packages</guilabel> page. </para> <figure> <title>Add classes and packages page </title> @@ -2234,37 +2148,17 @@ </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 <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 - option to <emphasis> - <property>Getters</property> - </emphasis>in <emphasis> - <property> Preferred location of Annotations</property> - </emphasis> dropdownlist and then all the annotations will be added to the getter methods. If - you choose <emphasis> - <property>Auto select from class preference</property> - </emphasis> then the annotations are added according to the majority of the already existed - ones positions. </para> - <para> If it's nessecary to map your String properties to the columns that length differ from - the default value(255) ,change <emphasis> - <property>Default string length field</property> - </emphasis> and <code>@Column(length = your length)</code> will be created before every String - property. </para> - <para id="optim_lock">You can add optimistic locking capability to an entity bean by selecting - <emphasis> - <property>Enable optimistic locking</property> - </emphasis> checkbox. This operation will add version property to all the selected classes. - The property will be also annotated with @Version ,getter and setter will be created. If the - property is already exists,it won't be created ,but the getters,setters will be generated. If - there is already @MappedSuperclass with version in the base class of the current class - - <emphasis> - <property>"version"</property> - </emphasis> is not inserted into the current class. </para> + <para> + Here you can add one more classes or whole package, moreover you can limit dependencies depth by selecting <guilabel>depth control</guilabel> option (you can find more information on this option in the <xref linkend="depth_control"/> section). When finished just press the <guibutton>Next</guibutton> button and you will be returned to <guilabel>The following classes will be changed</guilabel> page.</para> + <para> + By default the tags are added to the fields of selected classes. But you can change this option to <guilabel>Getters</guilabel> in <guilabel> Preferred location of Annotations</guilabel> drop down list and then all the annotations will be added to the getter methods. If you choose <guilabel>Auto select from class preference</guilabel> then the annotations are added according to the majority of the already existed ones positions. + </para> + <para> + If it is necessary to map your String properties to the columns that length differ from the default value(255), change the <guilabel>Default string length</guilabel> field and <code>@Column(length = your length)</code> will be created for every String property. + </para> + <para id="optim_lock"> + You can add optimistic locking capability to an entity bean by selecting the <guilabel>Enable optimistic locking</guilabel> checkbox. This operation will add version property to all the selected classes. The property will be also annotated with <code>@Version</code>, and a getter and setter will be created. If the property is already exists, it won't be created, but the getters and setters will be generated. If there is already <code>@MappedSuperclass</code> annotation with version in the base class of the current class - <code>version</code> 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> @@ -2274,26 +2168,9 @@ </imageobject> </mediaobject> </figure> - <para>The view represents two windows: one with the source code and and the second with - refactored one. With the help of <inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/butt1.png"/> - </imageobject> - </inlinemediaobject> ,<inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/butt2.png"/> - </imageobject> - </inlinemediaobject> ,<inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/butt3.png"/> - </imageobject> - </inlinemediaobject> ,<inlinemediaobject> - <imageobject> - <imagedata fileref="images/plugins/butt4.png"/> - </imageobject> - </inlinemediaobject> buttons you can quickly navigate between the differences in the code. If - you don't agree with some changes you can't undo them but you can remove the class from the - list of classes that need refactoring. </para> + <para> + The view represents two windows: one with the source code and and the second with refactored one. With the help of the <inlinemediaobject><imageobject><imagedata fileref="images/plugins/butt1.png"/></imageobject></inlinemediaobject>, <inlinemediaobject><imageobject><imagedata fileref="images/plugins/butt2.png"/></imageobject></inlinemediaobject>, <inlinemediaobject><imageobject><imagedata fileref="images/plugins/butt3.png"/></imageobject></inlinemediaobject>, <inlinemediaobject><imageobject><imagedata fileref="images/plugins/butt4.png"/></imageobject></inlinemediaobject> buttons you can quickly navigate between the differences in the code. If you don't agree with some changes you can't undo them but you can remove the class from the list of classes that need refactoring. + </para> <figure> <title>List of classes that need refactoring</title> <mediaobject> @@ -2302,15 +2179,14 @@ </imageobject> </mediaobject> </figure> - <para>To apply the changes click <emphasis> - <property>Finish</property> - </emphasis>.</para> + <para>To apply the changes click the <guibutton>Finish</guibutton> button.</para> </section> <section id="debug_log"> <title>Enable debug logging in the plugins</title> - <para>It is possible to configure the eclipse plugin to route all logging made by the plugins - and hibernate code it self to the <property>Error Log View</property> in Eclipse.</para> <para> + It is possible to configure the Eclipse plugin to route all logging made by the plugins and hibernate code it self to the <guilabel>Error Log View</guilabel> 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 <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

15 years, 2 months

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-20 19:39:59 -0500 (Thu, 20 Jan 2011) New Revision: 28451 Modified: trunk/build/aggregate/site/build.xml Log: add relative path item to wget target folder Modified: trunk/build/aggregate/site/build.xml =================================================================== --- trunk/build/aggregate/site/build.xml 2011-01-21 00:28:48 UTC (rev 28450) +++ trunk/build/aggregate/site/build.xml 2011-01-21 00:39:59 UTC (rev 28451) @@ -124,7 +124,7 @@ </then> <else> <var name="wget.return" unset="true" /> - <exec executable="wget" dir="${aggregate.zips.dir}" failonerror="false" failifexecutionfails="false" resultproperty="wget.return" outputproperty="null"> + <exec executable="wget" dir="${aggregate.zips.dir}/${relativePath}" failonerror="false" failifexecutionfails="false" resultproperty="wget.return" outputproperty="null"> <arg line="${location.cleaned}/@{zipPath} -q --no-clobber" /> </exec> <if>

15 years, 2 months

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-20 19:28:48 -0500 (Thu, 20 Jan 2011) New Revision: 28450 Added: trunk/build/aggregate/site/remove-uncategorized.xsl Modified: trunk/build/aggregate/site/build.xml trunk/build/aggregate/site/pom.xml Log: merge from CR1 branch to trunk Modified: trunk/build/aggregate/site/build.xml =================================================================== --- trunk/build/aggregate/site/build.xml 2011-01-21 00:16:42 UTC (rev 28449) +++ trunk/build/aggregate/site/build.xml 2011-01-21 00:28:48 UTC (rev 28450) @@ -283,8 +283,11 @@ <echo file="${update.site.source.dir}/content.xml" append="true"> </references> </repository> </echo> + <copy file="${update.site.source.dir}/content.xml" tofile="${update.site.source.dir}/content.old.xml" overwrite="true" /> + <xslt style="remove-uncategorized.xsl" in="${update.site.source.dir}/content.old.xml" out="${update.site.source.dir}/content.xml" /> <zip destfile="${update.site.source.dir}/content.jar" basedir="${update.site.source.dir}" includes="content.xml" /> <delete file="${update.site.source.dir}/content.xml" /> + <delete file="${update.site.source.dir}/content.old.xml" /> </then> </if> </target> Modified: trunk/build/aggregate/site/pom.xml =================================================================== --- trunk/build/aggregate/site/pom.xml 2011-01-21 00:16:42 UTC (rev 28449) +++ trunk/build/aggregate/site/pom.xml 2011-01-21 00:28:48 UTC (rev 28450) @@ -1,6 +1,6 @@ -<project +<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" - xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> +xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > <modelVersion>4.0.0</modelVersion> <parent> <groupId>org.jboss.tools</groupId> @@ -25,7 +25,7 @@ <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-antrun-plugin</artifactId> - <version>1.6</version> + <version>${maven.antrun.plugin.version}</version> <executions> <execution> <id>install</id> @@ -33,11 +33,11 @@ <configuration> <quiet>true</quiet> <tasks> - <property name="inputRepo1" value="${inputRepo1}" /> - <property name="inputRepos" value="${inputRepos}" /> + <property name="inputRepo1" value="${inputRepo1}"/> + <property name="inputRepos" value="${inputRepos}"/>  - <ant antfile="build.xml" /> + <ant antfile="build.xml"/> </tasks> </configuration> @@ -54,6 +54,16 @@ </dependency> <dependency> <groupId>org.apache.ant</groupId> + <artifactId>ant</artifactId> + <version>1.7.1</version> + </dependency> + <dependency> + <groupId>org.apache.ant</groupId> + <artifactId>ant-trax</artifactId> + <version>1.7.1</version> + </dependency> + <dependency> + <groupId>org.apache.ant</groupId> <artifactId>ant-commons-net</artifactId> <version>1.7.1</version> </dependency> @@ -95,4 +105,4 @@ </releases> </repository> </repositories> -</project> +</project> \ No newline at end of file Added: trunk/build/aggregate/site/remove-uncategorized.xsl =================================================================== --- trunk/build/aggregate/site/remove-uncategorized.xsl (rev 0) +++ trunk/build/aggregate/site/remove-uncategorized.xsl 2011-01-21 00:28:48 UTC (rev 28450) @@ -0,0 +1,20 @@ +<?xml version="1.0" encoding="UTF-8"?> +<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="2.0"> + +<xsl:template match="/"> + <xsl:apply-templates select="*"/> +</xsl:template> + + +<xsl:template match="*"> + <xsl:copy > + <xsl:for-each select="@*"> + <xsl:copy /> + </xsl:for-each> + <xsl:apply-templates /> + </xsl:copy> +</xsl:template> + +<xsl:template match="unit[contains(@id,'site.xml.Default')]" /> + +</xsl:stylesheet> \ No newline at end of file

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28449 - trunk/download.jboss.org/jbosstools/requirements/helios.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-20 19:16:42 -0500 (Thu, 20 Jan 2011) New Revision: 28449 Modified: trunk/download.jboss.org/jbosstools/requirements/helios/README.txt Log: add details on how Denis generated the metadata Modified: trunk/download.jboss.org/jbosstools/requirements/helios/README.txt =================================================================== --- trunk/download.jboss.org/jbosstools/requirements/helios/README.txt 2011-01-21 00:02:16 UTC (rev 28448) +++ trunk/download.jboss.org/jbosstools/requirements/helios/README.txt 2011-01-21 00:16:42 UTC (rev 28449) @@ -100,12 +100,14 @@ # zip -r9 ~/tru/download.jboss.org/jbosstools/requirements/helios/spring-ide-2.5.1.201011101000-RELEASE.zip \ # $(find . -mindepth 3 -maxdepth 3 -name "???.spring*") -# Denis created an update site version, which is spring-ide-Update-2.5.1.201011101000-RELEASE.zip -# Not sure how, exactly. +# Denis created an update site version, which is spring-ide-Update-2.5.1.201011101000-RELEASE.zip. +# Used Eclipse: +# <p2.publish.featuresAndBundles source="/home/eskimo/Projects/jbds-build/jbds-build/requirements/springide/spring-ide-2.5.1.201011101000-RELEASE" repository="file:///home/eskimo/Projects/jbds-build/jbds-build/requirements/springide/spring-ide-2.5.1.201011101000-RELEASE" compress="true"/> + TestNG # Built from ~/tru/product/extras/site/pom.xml, then repackaged to include only the testng plugin + feature (exclude all else): testng-eclipse-5.14.6.20110119.zip # Denis created an update site version, which is testng-eclipse-Update-5.14.6.20110119_1050.zip -# Not sure how, exactly. +# (see SpringIDE approach above using Eclipse and p2 publisher).

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28448 - trunk/download.jboss.org/jbosstools/requirements/helios.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-20 19:02:16 -0500 (Thu, 20 Jan 2011) New Revision: 28448 Modified: trunk/download.jboss.org/jbosstools/requirements/helios/.gitignore Log: add .directory to .gitignore Modified: trunk/download.jboss.org/jbosstools/requirements/helios/.gitignore =================================================================== --- trunk/download.jboss.org/jbosstools/requirements/helios/.gitignore 2011-01-20 23:55:18 UTC (rev 28447) +++ trunk/download.jboss.org/jbosstools/requirements/helios/.gitignore 2011-01-21 00:02:16 UTC (rev 28448) @@ -2,3 +2,4 @@ *.jar *.tar.gz *~ +.directory

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28447 - trunk/download.jboss.org/jbosstools/requirements/helios.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-20 18:55:18 -0500 (Thu, 20 Jan 2011) New Revision: 28447 Modified: trunk/download.jboss.org/jbosstools/requirements/helios/.gitignore trunk/download.jboss.org/jbosstools/requirements/helios/README.txt trunk/download.jboss.org/jbosstools/requirements/helios/index.html Log: add testng-eclipse-Update-5.14.6.20110119_1050.zip + other testng zips, spring-ide-Update-2.5.1.201011101000-RELEASE.zip Modified: trunk/download.jboss.org/jbosstools/requirements/helios/.gitignore =================================================================== --- trunk/download.jboss.org/jbosstools/requirements/helios/.gitignore 2011-01-20 23:22:47 UTC (rev 28446) +++ trunk/download.jboss.org/jbosstools/requirements/helios/.gitignore 2011-01-20 23:55:18 UTC (rev 28447) @@ -1,3 +1,4 @@ *.zip *.jar *.tar.gz +*~ Modified: trunk/download.jboss.org/jbosstools/requirements/helios/README.txt =================================================================== --- trunk/download.jboss.org/jbosstools/requirements/helios/README.txt 2011-01-20 23:22:47 UTC (rev 28446) +++ trunk/download.jboss.org/jbosstools/requirements/helios/README.txt 2011-01-20 23:55:18 UTC (rev 28447) @@ -1,4 +1,4 @@ -Total of 24 req'd tgzs/zips/jars. +Total of 25 req'd tgzs/zips/jars. BIRT 2.6 -> http://www.eclipse.org/downloads/download.php?file=/birt/downloads/build_... -> @@ -100,3 +100,12 @@ # zip -r9 ~/tru/download.jboss.org/jbosstools/requirements/helios/spring-ide-2.5.1.201011101000-RELEASE.zip \ # $(find . -mindepth 3 -maxdepth 3 -name "???.spring*") +# Denis created an update site version, which is spring-ide-Update-2.5.1.201011101000-RELEASE.zip +# Not sure how, exactly. + +TestNG +# Built from ~/tru/product/extras/site/pom.xml, then repackaged to include only the testng plugin + feature (exclude all else): testng-eclipse-5.14.6.20110119.zip + +# Denis created an update site version, which is testng-eclipse-Update-5.14.6.20110119_1050.zip +# Not sure how, exactly. + Modified: trunk/download.jboss.org/jbosstools/requirements/helios/index.html =================================================================== --- trunk/download.jboss.org/jbosstools/requirements/helios/index.html 2011-01-20 23:22:47 UTC (rev 28446) +++ trunk/download.jboss.org/jbosstools/requirements/helios/index.html 2011-01-20 23:55:18 UTC (rev 28447) @@ -73,7 +73,11 @@ <li><a class=link href=org.eclipse.swtbot.eclipse.gef-2.0.1.20101106_1831-73ca7af-dev-e36.zip>org.eclipse.swtbot.eclipse.gef-2.0.1.20101106_1831-73ca7af-dev-e36.zip</a></li> <li><a class=link href=org.eclipse.swtbot.eclipse.test.junit4-2.0.1.20101106_1831-73ca7af-dev-e36.zip>org.eclipse.swtbot.eclipse.test.junit4-2.0.1.20101106_1831-73ca7af-dev-e36.zip</a></li> <li><a class=link href=swtbot-update-site-2.0.1.20101106_1831-73ca7af-dev-e36.zip>swtbot-update-site-2.0.1.20101106_1831-73ca7af-dev-e36.zip</a></li> +<li><a class=link href=spring-ide-Update-2.5.1.201011101000-RELEASE.zip>spring-ide-Update-2.5.1.201011101000-RELEASE.zip</a></li> <li><a class=link href=spring-ide-2.5.1.201011101000-RELEASE.zip>spring-ide-2.5.1.201011101000-RELEASE.zip</a></li> +<li><a class=link href=testng-eclipse-5.8.0.1.zip>testng-eclipse-5.8.0.1.zip</a></li> +<li><a class=link href=testng-eclipse-5.14.6.20110119.zip>testng-eclipse-5.14.6.20110119.zip</a></li> +<li><a class=link href=testng-eclipse-Update-5.14.6.20110119_1050.zip>testng-eclipse-Update-5.14.6.20110119_1050.zip</a></li> <li><a class=link href=tptp.runtime-TPTP-4.7.1.zip>tptp.runtime-TPTP-4.7.1.zip</a></li> <li><a class=link href=mdt-uml2-runtime-3.1.1.zip>mdt-uml2-runtime-3.1.1.zip</a></li> <li><a class=link href=wtp-R-3.2.2-20100915173744.zip>wtp-R-3.2.2-20100915173744.zip</a></li>

15 years, 2 months

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-20 18:22:47 -0500 (Thu, 20 Jan 2011) New Revision: 28446 Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/plugins.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-20 22:56:26 UTC (rev 28445) +++ trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-20 23:22:47 UTC (rev 28446) @@ -305,8 +305,7 @@ <para>Database dialect</para> </entry> <entry> - <para>Define a database dialect. It's possible either to write your value or - choose from list. </para> + <para>Define a database dialect. It is possible either to write your value or choose from list. </para> </entry> <entry> <para>No default value</para> @@ -317,8 +316,7 @@ <para>Naming strategy</para> </entry> <entry> - <para>Fully qualified classname of a custom NamingStrategy. Only required if you use - a special naming strategy.</para> + <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> @@ -329,8 +327,7 @@ <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> + <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> @@ -384,11 +381,9 @@ <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> + <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> @@ -399,8 +394,7 @@ <para>Include default classpath from project</para> </entry> <entry> - <para>When enabled the project classpath will be appended to the classpath specified - above</para> + <para>When enabled the project classpath will be appended to the classpath specified above</para> </entry> <entry> <para>Enabled</para> @@ -428,8 +422,7 @@ </imageobject> </mediaobject> </figure> - <para>Parameters of the Mappings tab of the <property>Hibernate Console Configuration - wizard</property> are explained below:</para> + <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"> @@ -455,10 +448,9 @@ <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> + <para> + List of additional mapping files that should be loaded. Note: A <filename>hibernate.cfg.xml</filename> or <filename>persistence.xml</filename> can also contain mappings. Thus if these are duplications here, you will get "Duplicate mapping" errors when using the console configuration. + </para> </entry> <entry> <para>empty</para> @@ -501,14 +493,11 @@ </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> + <para>When you created a hibernate console configuration you can modify it in two ways: </para> <itemizedlist> <listitem> <para> - Right-click on the configuration in <menuchoice><guimenuitem>Hibernate Configurations View</guimenuitem> - <guimenuitem>Edit Configuration</guimenuitem> - </menuchoice> or just double-click on <property>Console Configuration</property> - item. + Right-click on the configuration in <menuchoice><guimenuitem>Hibernate Configurations View</guimenuitem><guimenuitem>Edit Configuration</guimenuitem></menuchoice> or just double-click on the <guilabel>Console Configuration</guilabel> item. </para> <figure> <title>Opening Edit Configuration Wizard</title> @@ -519,8 +508,7 @@ </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 <guilabel>Edit Configuration Wizard</guilabel> which is similar to <guilabel>Create Console Configuration</guilabel>, described in <xref linkend="creat_console_conf"/>. </para> </listitem> <listitem> @@ -533,8 +521,9 @@ </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> + <para> + The following table describes the available settings in the <guilabel>Properties</guilabel> view. Most properties can be changed by left clicking on them but some are not. + <table> <title>Properties</title> <tgroup cols="3"> <colspec colnum="1" align="left" colwidth="1*"/> @@ -582,7 +571,7 @@ </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. + DTP provided connection that you can use instead of what is in <filename>cfg.xml</filename> and jpa <filename>persistence.xml</filename>. It is possible to use either an already configured hibernate or JPA connection, or specify a new one here. </para> </entry> <entry> @@ -616,7 +605,7 @@ <para>Properties 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>False</para> @@ -645,8 +634,9 @@ </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> + <para> + To close <guilabel>Hibernate Console Configuration</guilabel> you need to right-click your configuration and choose the <guimenuitem>Close Configuration</guimenuitem> option + </para> <figure> <title>Close Hibernate Console Configuration</title> <mediaobject> @@ -655,25 +645,24 @@ </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> + <para> + Whe closing the configuration the connection with database will be closed, jar libs will be unlock (for Windows) and other resources will set as free. + </para> </section> </section> <section id="refeng_codegen" role="updated"> <title>Reverse Engineering and Code Generation</title> - <para>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 <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. + 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 <filename>.hbm.xml</filename>, <filename>hibernate.cfg.xml</filename> generation and schema documentation. </para> + <para> + To start working with this process, start the <guilabel>Hibernate Code Generation</guilabel> which is available from the toolbar via the <property>Hibernate</property> icon or via the <menuchoice><guimenuitem>Run</guimenuitem><guimenuitem>Hibernate Code Generation</guimenuitem></menuchoice> menu item. + </para> <section id="code_gen"> <title>Code Generation Launcher</title> - <para>When you click on <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> + <para> + When you click on the <guimenuitem>Open Hibernate Code Generation Dialog...</guimenuitem> option the standard Eclipse launcher dialog will appear. In this dialog you can create, edit and delete named Hibernate code generation "launchers". + </para> <figure id="hib_code_gen"> <title>Getting Hibernate Code Generation Wizard</title> <mediaobject> @@ -697,18 +686,17 @@ </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> + <para> + The first time you create a code generation launcher you should give it a meaningful name, otherwise the default prefix <guilabel>New_Generation</guilabel> will be used. + </para> <note> <title>Tip:</title> - <para>The "At least one exporter option must be selected" 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> + <para> + The "At least one exporter option must be selected" warning is just stating that for this launch to work you need to select an exporter on the <guilabel>Exporter</guilabel> tab. When an exporter has been selected the warning will disappear. + </para> </note> <para> - The dialog also 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. + The dialog also has 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> @@ -735,8 +723,7 @@ <para>Console Configuration</para> </entry> <entry> - <para>The name of the console configuration which should be used when code - generating</para> + <para>The name of the console configuration which should be used when code generating</para> </entry> </row> <row> @@ -744,9 +731,9 @@ <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> + <para> + The default location where all output will be written to. It's possible to enter absolute directory path, for example - <filename>d:/temp</filename>. Be aware that existing files will be overwritten, so be sure to specify the correct directory. + </para> </entry> </row> <row> @@ -754,11 +741,9 @@ <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> + <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> @@ -766,8 +751,7 @@ <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> + <para>The package name here is used as the default package name for any entities found when reverse engineering</para> </entry> </row> <row> @@ -775,11 +759,9 @@ <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 <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> + <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 the <guiButton>setup</guiButton> button allows you to select an existing <filename>reveng.xml</filename> file or create a new one. See more details about the <filename>reveng.xml</filename> file in <xref linkend="reverseengineering"/>. + </para> </entry> </row> <row> @@ -787,11 +769,9 @@ <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> + <para> + If the <filename>reveng.xml</filename> file 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> @@ -799,13 +779,9 @@ <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> + <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> @@ -813,8 +789,9 @@ <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> + <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> @@ -822,8 +799,7 @@ <para>Detect many-to-many tables</para> </entry> <entry> - <para>Automatically detect many-to-many tables. Controllable via reveng. - strategy.</para> + <para>Automatically detect many-to-many tables. Controllable via reveng. strategy.</para> </entry> </row> <row> @@ -831,11 +807,12 @@ <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> + <para> + Reverse engineering detects one-to-one associations via primary key and both the <filename>hbm.xml</filename> file and annotation generation generates the proper code for it. + </para> + <para> + The detection is enabled by default (except for Seam 1.2 and Seam 2.0) reverse engineering. For Hibernate Tools generation there is a checkbox to disable if not wanted. + </para> </entry> </row> <row> @@ -843,9 +820,9 @@ <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> + <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> @@ -862,11 +839,9 @@ </section> <section id="exportes"> <title>Exporters</title> - <para>The <emphasis> - <property>Exporters</property> - </emphasis> tab is used to specify which type of code that should be generated. Each - selection represents an Exporter that is responsible for generating the code, hence the - name.</para> + <para> + The <guilabel>Exporters</guilabel> tab is used to specify the type of code that should be generated. Each selection represents an Exporter that is responsible for generating the code, hence the name. + </para> <figure> <title>Selecting Exporters</title> <mediaobject> @@ -878,8 +853,9 @@ </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> + <para> + The following table provides a short description of the various exporters. Remember you can add and remove any Exporters depending on your needs. + </para> <table> <title>Code generation "Exporter" tab fields</title> <tgroup cols="2"> @@ -901,8 +877,7 @@ <para>Domain code</para> </entry> <entry> - <para>Generates POJO's for all the persistent classes and components found in the - given Hibernate configuration.</para> + <para>Generates POJO's for all the persistent classes and components found in the given Hibernate configuration.</para> </entry> </row> <row> @@ -926,8 +901,9 @@ <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> + <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> @@ -935,8 +911,7 @@ <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> + <para>Generates a set of html pages that documents the database schema and some of the mappings.</para> </entry> </row> <row> @@ -944,8 +919,7 @@ <para>Generic Exporter (hbmtemplate)</para> </entry> <entry> - <para>Fully customizable exporter which can be used to perform custom - generation.</para> + <para>Fully customizable exporter that can be used to perform custom generation.</para> </entry> </row> <row> @@ -953,18 +927,16 @@ <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> + <para>Generates the appropriate SQL DDL and allows you to store the result in a file or export it directly to the database.</para> </entry> </row> </tbody> </tgroup> </table> - <para>Each Exporter listens to certain properties and these can be setup in the <emphasis> - <property>Properties</property> - </emphasis> section where you can add/remove predefined or customer properties for each of - the exporters. The following table lists the time of writing predefined properties:</para> <para> + Each Exporter listens to certain properties and these can be setup in the <guilabel>Properties</guilabel> section where you can add and remove predefined or customer properties for each of the exporters. The following table lists the time of writing predefined properties: + </para> + <para> <table> <title>Exporter Properties</title> <tgroup cols="2"> @@ -1002,9 +974,9 @@ <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> + <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> @@ -1012,8 +984,7 @@ <para>template_path</para> </entry> <entry> - <para>Custom template directory for this specific exporter. You can use Eclipse - variables.</para> + <para>Custom template directory for this specific exporter. You can use Eclipse variables.</para> </entry> </row> <row> @@ -1029,8 +1000,7 @@ <para>outputdir</para> </entry> <entry> - <para>Custom output directory for this specific exporter. You can use Eclipse - variables.</para> + <para>Custom output directory for this specific exporter. You can use Eclipse variables.</para> </entry> </row> <row> @@ -1038,8 +1008,9 @@ <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> + <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> @@ -1047,8 +1018,7 @@ <para>dot.executable</para> </entry> <entry> - <para>Executable to run GraphViz (only relevant, but optional for Schema - documentation)</para> + <para>Executable to run GraphViz (only relevant, but optional for Schema documentation)</para> </entry> </row> <row> @@ -1056,8 +1026,7 @@ <para>drop</para> </entry> <entry> - <para>Output will contain drop statements for the tables, indices and - constraints</para> + <para>Output will contain drop statements for the tables, indices and constraints</para> </entry> </row> <row> @@ -1073,8 +1042,7 @@ <para>create</para> </entry> <entry> - <para>Output will contain create statements for the tables, indices and - constraints</para> + <para>Output will contain create statements for the tables, indices and constraints</para> </entry> </row> <row> @@ -1130,7 +1098,7 @@ </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. + To add a property to the chosen Exporter click the <guibutton>Add</guibutton> button in the <guilabel>Properties</guilabel> 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> @@ -1142,8 +1110,7 @@ </figure> <note> <title>Tip:</title> - <para>If the property is a directory, it is possible to browse directories in the Value - field.</para> + <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> @@ -1157,9 +1124,9 @@ </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> + <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> @@ -1173,11 +1140,9 @@ </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 <filename>hbm.xml</filename> files to the relevant class/field in java code.</para> + <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 <filename>hbm.xml</filename> files to the relevant class/field in java code. + </para> <figure> <title>Navigation Functionality</title> <mediaobject> @@ -1189,10 +1154,10 @@ </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> + <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> @@ -1214,24 +1179,23 @@ </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> + <para> + Table/Column completion requires a properly configured hibernate console configuration and this configuration should be the default for the project where the <filename>hbm.xml</filename> resides. + </para> </important> - <para>You can check which console configuration is selected under the Properties of a project - and look under the <emphasis> - <property>Hibernate Settings</property> - </emphasis> page. When a proper configuration is selected it will be used to fetch the - table/column names in the background.</para> + <para> + You can check which console configuration is selected under the Properties of a project and look under the <guilabel>Hibernate Settings</guilabel> page. When a proper configuration is selected it will be used to fetch the table/column names in the background. + </para> <note> <title>Note:</title> - <para>Currently it is not recommended to use this feature on large databases since it does - not fetch the information iteratively. It will be improved in future versions.</para> + <para> + Currently it is not recommended to use this feature on large databases since it does not fetch the information iteratively. This will be improved in future versions. + </para> </note> </section> <section> <title>Configuration property completion</title> - <para>In <filename>cfg.xml</filename> code completion for the value of <code><property> name</code> attributes - is available.</para> + <para>In <filename>cfg.xml</filename> code completion for the value of <code><property> name</code> attributes are available.</para> <figure> <title>Property Completion</title> <mediaobject> @@ -1247,13 +1211,11 @@ </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 <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: + The structured editor represents the file in a tree form. It also provides a way to modify the structure of the file and its elements with the help of tables provided on the right-hand area. + </para> + <para> + To open any mapping file in the editor, select <menuchoice><guimenuitem>Open With</guimenuitem><guimenuitem>Hibernate 3.0 XML Editor</guimenuitem></menuchoice> option from the context menu of the file. The editor is shown in the following image: </para> <figure> <title>Structured hbm.xml Editor</title> @@ -1263,9 +1225,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> @@ -1277,14 +1239,13 @@ </section> <section id="properties_editor"> <title>JBoss Tools Properties Editor</title> - <para>The editor is meant for editing <literal>.properties</literal> files. It contains two - tabs: the <property>Properties</property> (UI) tab and the <property>Source</property> tab for - manual editing.</para> - <para>For <literal>hibernate.properties</literal> file <property>JBoss Tools Properties - Editor</property> provides content assist which is available both for hibernate properties - and property values. You can make use of the content assist while editing the file in the - Source view and in the Properties view of the editor.</para> - <para>To add the property in the <property>Properties</property> view, click the <guibutton>Add</guibutton> button.</para> + <para> + The editor is meant for editing <filename>.properties</filename> files. It contains two tabs: the <guilabel>Properties</guilabel> (UI) tab and the <guilabel>Source</guilabel> tab for manual editing. + </para> + <para> + For <filename>hibernate.properties</filename> file <guilabel>JBoss Tools Properties Editor</guilabel> provides content assist for both hibernate properties and property values. You can make use of the content assist while editing the file in the <guilabel>Source</guilabel> view and in the <guilabel>Properties</guilabel> view of the editor. + </para> + <para>To add the property in the <guilabel>Properties</guilabel> view, click the <guibutton>Add</guibutton> button.</para> <figure> <title>Adding the Property</title> <mediaobject> @@ -1293,16 +1254,9 @@ </imageobject> </mediaobject> </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> - <property>'hibernate.'</property> - </emphasis> which is the prefix for all hibernate properties. After selecting <emphasis> - <property>'hibernate.'</property> - </emphasis> and invoking the content assist again, other prefixes and properties are displayed - as the proposals with a description of each one.</para> + <para> + In the <guilabel>Name</guilabel> field press <keycombo><keycap>Ctrl</keycap><keycap>Space</keycap></keycombo> to invoke the content assist. It will suggest <code>'hibernate.'</code> which is the prefix for all hibernate properties. After selecting <code>'hibernate.'</code> and invoking the content assist again, other prefixes and properties are displayed as the proposals with a description of each one. + </para> <figure> <title>Content Assist for Properties Names</title> <mediaobject> @@ -1311,9 +1265,7 @@ </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> + <para>When invoking the content assist in the <guilabel>Value</guilabel> field, it also provides a list of proposals.</para> <figure> <title>Content Assist for Properties Values</title> <mediaobject> @@ -1322,8 +1274,7 @@ </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> + <para>In the <guilabel>Source</guilabel> view of the editor, content assist can also be invoked both for properties names and values:</para> <figure> <title>Content Assist in the Source view</title> <mediaobject> @@ -1343,23 +1294,21 @@ </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 - and specific override settings for columns, e.g. define an explicit name for a column when the - default naming rules are not applicable.</para> + <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 and specific override settings for columns, e.g. define an explicit name for a column when the default naming rules are not applicable. + </para> <note> <title>Note:</title> - <para> Not all the features of the <filename>.reveng.xml </filename> file are exposed or fully implemented in the editor, but the main functionality - is there. To understand the full flexibility of the <filename>reveng.xml</filename>, please see <xref linkend="hibernaterevengxmlfile"/> + <para> + Not all the features of the <filename>.reveng.xml</filename> file are exposed or fully implemented in the editor, but the main functionality is there. To understand the full flexibility of the <filename>reveng.xml</filename> file, please see <xref linkend="hibernaterevengxmlfile"/> </para> </note> - <para>The editor is activated as soon as 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 a <filename>.reveng.xml </filename> file is opened. To get an initial <filename>reveng.xml </filename> file the <guilabel>Reverse Engineering File Wizard</guilabel> can be started via <keycombo><keycap>Ctrl</keycap><keycap>N</keycap></keycombo> and then selecting <menuchoice><guimenuitem>Hibernate</guimenuitem><guimenuitem>Hibernate Reverse Engineering File (reveng.xml)</guimenuitem></menuchoice>. + </para> <figure> <title>ChooseReverse Engineering File Wizard </title> <mediaobject> @@ -1371,14 +1320,12 @@ </imageobject> </mediaobject> </figure> - <para>Or you can get it via the <property>Code Generation Launcher</property> by checking the - proper section in the <emphasis> - <property>Main</property> - </emphasis> tab of the <xref linkend="hib_code_gen"/>.</para> - <para>The following screenshot shows the <emphasis> - <property>Overview</property> - </emphasis> page where the wanted console configuration is selected (auto-detected if - Hibernate 3 support is enabled for the project)</para> + <para> + Or you can get it via the <guilabel>Code Generation Launcher</guilabel> by checking the proper section in the <guilabel>Main</guilabel> tab of the <guilabel>Getting Hibernate Code Generation Wizard</guilabel> (see <xref linkend="hib_code_gen"/>). + </para> + <para> + The following screenshot shows the <guilabel>Overview</guilabel> page where the wanted console configuration is selected (auto-detected if Hibernate 3 support is enabled for the project) + </para> <figure> <title>Overview Page</title> <mediaobject>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28445 - in trunk/download.jboss.org/jbosstools/updates/requirements: helios_orbit and 1 other directory.

by jbosstools-commits＠lists.jboss.org

Author: nickboldt Date: 2011-01-20 17:56:26 -0500 (Thu, 20 Jan 2011) New Revision: 28445 Added: trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/ trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/.gi... trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/com... trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/com... Log: add composite repo for helios + orbit Added: trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/.gi... =================================================================== --- trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/.gi... (rev 0) +++ trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/.gi... 2011-01-20 22:56:26 UTC (rev 28445) @@ -0,0 +1 @@ +*~ Added: trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/com... =================================================================== --- trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/com... (rev 0) +++ trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/com... 2011-01-20 22:56:26 UTC (rev 28445) @@ -0,0 +1,16 @@ +<?xml version='1.0' encoding='UTF-8'?> +<?compositeArtifactRepository version='1.0.0'?> +<repository name='JBoss Tools Staging Repository' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'> +<properties size='2'> +<property name='p2.compressed' value='true'/> + +<property name='p2.timestamp' value='1295563511000'/> +</properties> +<children size='2'> +<child location='http://download.jboss.org/jbosstools/updates/requirements/helios/20100623...'/> +<child location='http://download.jboss.org/jbosstools/updates/requirements/orbit/R20100519...'/> +</children> +</repository> Added: trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/com... =================================================================== --- trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/com... (rev 0) +++ trunk/download.jboss.org/jbosstools/updates/requirements/helios_orbit/com... 2011-01-20 22:56:26 UTC (rev 28445) @@ -0,0 +1,16 @@ +<?xml version='1.0' encoding='UTF-8'?> +<?compositeMetadataRepository version='1.0.0'?> +<repository name='JBoss Tools Staging Repository' type='org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository' version='1.0.0'> +<properties size='2'> +<property name='p2.compressed' value='true'/> + +<property name='p2.timestamp' value='1295563511000'/> +</properties> +<children size='2'> +<child location='http://download.jboss.org/jbosstools/updates/requirements/helios/20100623...'/> +<child location='http://download.jboss.org/jbosstools/updates/requirements/orbit/R20100519...'/> +</children> +</repository>

15 years, 2 months

1
0
0 / 0

JBoss Tools SVN: r28444 - trunk/documentation/whatsnew/bpel.

by jbosstools-commits＠lists.jboss.org

Author: bbrodt Date: 2011-01-20 16:05:16 -0500 (Thu, 20 Jan 2011) New Revision: 28444 Added: trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.CR1.html Log: https://issues.jboss.org/browse/JBIDE-8170 What's new for CR1 Added: trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.CR1.html =================================================================== --- trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.CR1.html (rev 0) +++ trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.CR1.html 2011-01-20 21:05:16 UTC (rev 28444) @@ -0,0 +1,42 @@ +<?xml version="1.0" encoding="iso-8859-1"?> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" + "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml"> +<head> +<meta http-equiv="Content-Language" content="en-us" /> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> +<link rel="stylesheet" href="../whatsnew.css" /> +<title>BPEL Tools 1.1.0.beta1 What's New</title> +</head> +<body> +<h1>JBoss Eclipse BPEL Editor 1.1.0.CR1 What's New</h1> + +<p align="right"><a href="../index.html">< Main Index</a> <a href="../esb/esb-news-1.4.0.M2.html">ESB Tools ></a></p> +<table border="0" cellpadding="10" cellspacing="0" width="80%"> + <tr> + <td colspan="2"> + <hr /> + <h3>General</h3> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="right"><a name="itemname3" id="itemname3"></a><b>BPEL + Editor</b></td> + <td valign="top">The following issues were fixed. + <ol> +<a href="https://jira.jboss.org/jira/browse/JBIDE-6879">JBIDE-6879</a> BPEL deployer should not be using PublishCopyUtili.java in JBoss as.core package <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7334">JBIDE-7334</a> Change the bpeldeploy.xml to deploy.xml <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7786">JBIDE-7786</a> Unable to associate BPEL project with SOA 5.1 runtime. <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-7861">JBIDE-7861</a> Unable to define invoke, receive, reply atributes by entering data without the use of "Quick Pick" or "Content Assist". <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-8042">JBIDE-8042</a> BPEL validator does not recognize counter variable inside forEach. <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-8044">JBIDE-8044</a> ArrayIndexOutOfBoundsException when adding compensateScope activity. <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-8048">JBIDE-8048</a> OnEvent Handler throws NPE when selecting PartnerLink and Operation in Properties tab <br></br> +<a href="https://jira.jboss.org/jira/browse/JBIDE-8087">JBIDE-8087</a> Incorrect imports in artifacts WSDL. <br></br> + </tr> + +</table> + +</body> + +</html>

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