January 2011 - jbosstools-commits

JBoss Tools SVN: r28543 - trunk/documentation/whatsnew/cdi.

by jbosstools-commits＠lists.jboss.org

Author: max.andersen(a)jboss.com Date: 2011-01-24 07:28:27 -0500 (Mon, 24 Jan 2011) New Revision: 28543 Modified: trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.Beta1.html trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.CR1.html Log: revert bad commit for JBIDE-8156 and do a few cleanups Modified: trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.Beta1.html =================================================================== --- trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.Beta1.html 2011-01-24 11:44:39 UTC (rev 28542) +++ trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.Beta1.html 2011-01-24 12:28:27 UTC (rev 28543) @@ -12,102 +12,87 @@ <h1>CDI tools 3.2.0.Beta1 What's New</h1> <p align="right"><a href="../index.html">< Main Index</a> <a - href="../hibernate/hibernate-news-3.4.0.CR1.html">Hibernate Tools News ></a></p> + href="../seam/seam-news-3.2.0.Beta1.html">Seam Tools News ></a></p> <table border="0" cellpadding="10" cellspacing="0" width="80%"> - <tr> - <td colspan="2"> - <hr /> - <h3>Beans.xml Source Editor</h3> - <hr /> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>Code Completion</b></p> - </td> - <td align="top"> - <p>Now CDI Tools provide code completion for the relevant types/annotations in beans.xml</p> - <img src="images/3.2.0.Beta1/beansXmlCA.gif"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-2704">Related Jira</a></small></p> - </td> - </tr> - <tr> - <td colspan="2"> - <hr /> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>Hyperlinks (OpenOns)</b></p> - </td> - <td valign="top"> - <p>Class/Annotation names can now be navigated to via OpenOn.</p> - <img src="images/3.2.0.Beta1/beansXmlOpenOn.gif"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-7025">Related Jira</a></small></p> - </td> - </tr> - <tr> - <td colspan="2"> - <hr /> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>Validation</b></p> - </td> - <td valign="top"> - <p>All the classes/annotation names are now validated.</p> - <img src="images/3.2.0.Beta1/beansXmlValidation.gif"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-6523">Related Jira</a></small></p> - </td> - </tr> - <tr> - <td colspan="2"> - <hr /> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>Weld extension (beans_1_1.xsd)</b></p> - </td> - <td valign="top"> - <p>Weld extension (beans_1_1.xsd) is now supported by beans.xml editor.</p> - <img src="images/3.2.0.Beta1/beansXmlWeld.gif"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-6998">Related Jira</a></small></p> - </td> - </tr> - <tr> - <td colspan="2"> - <hr /> - <h3>OpenOn for Injected Class</h3> - <hr /> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>OpenOn for Injected Class.</b></p> - </td> - <td valign="top"> - <p>OpenOn menu for injection points now gives more information about eligible beans. - </p> - <img src="images/3.2.0.Beta1/openOns1.png"/><br/><br/> - <img src="images/3.2.0.Beta1/openOns2.png"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-6640">Related Jira</a></small></p> - </td> - </tr> - - <tr> - <td colspan="2"> - <hr /> - </td> - </tr> - +<tr> + <td colspan="2"> + <hr /> + <h3>Beans.xml Source Editor</h3> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>Code Completion</b></p> + </td> + <td align="top"> + <p>Now CDI Tools provide code completion for the relevant types/annotations in beans.xml</p> + <img src="images/3.2.0.Beta1/beansXmlCA.gif"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-2704">Related Jira</a></small></p> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>Hyperlinks (OpenOns)</b></p> + </td> + <td valign="top"> + <p>Class/Annotation names can now be navigated to via OpenOn.</p> + <img src="images/3.2.0.Beta1/beansXmlOpenOn.gif"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-7025">Related Jira</a></small></p> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>Validation</b></p> + </td> + <td valign="top"> + <p>All the classes/annotation names are now validated.</p> + <img src="images/3.2.0.Beta1/beansXmlValidation.gif"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-6523">Related Jira</a></small></p> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>Weld extension (beans_1_1.xsd)</b></p> + </td> + <td valign="top"> + <p>Weld extension (beans_1_1.xsd) is now supported by beans.xml editor.</p> + <img src="images/3.2.0.Beta1/beansXmlWeld.gif"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-6998">Related Jira</a></small></p> + </td> + </tr> +<tr> + <td colspan="2"> + <hr /> + <h3>OpenOn for Injected Class</h3> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>OpenOn for Injected Class.</b></p> + </td> + <td valign="top"> + <p>OpenOn menu for injection points now gives more information about eligible beans. + </p> + <img src="images/3.2.0.Beta1/openOns1.png"/><br/><br/> + <img src="images/3.2.0.Beta1/openOns2.png"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-6640">Related Jira</a></small></p> + </td> + </tr> + + <tr> + <td colspan="2"> + <hr /> + </td> + </tr> + </table> </body> Modified: trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.CR1.html =================================================================== --- trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.CR1.html 2011-01-24 11:44:39 UTC (rev 28542) +++ trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.CR1.html 2011-01-24 12:28:27 UTC (rev 28543) @@ -11,9 +11,8 @@ <body> <h1>CDI tools 3.2.0.CR1 What's New</h1> -<p align="right"><a href="../index.html">< Main Index</a> <a - href="../bpel/bpel-news-1.1.0.CR1.html">BPEL Tools News ></a></p> +<p align="right"><a href="../index.html">< Main Index</a> <a + href="../hibernate/hibernate-news-3.4.0.CR1.html">Hibernate Tools News ></a></p> <table border="0" cellpadding="10" cellspacing="0" width="80%"> <tr>

13 years, 5 months

1
0
0 / 0

JBoss Tools SVN: r28542 - in trunk/documentation/whatsnew: bpel and 2 other directories.

by jbosstools-commits＠lists.jboss.org

Author: max.andersen(a)jboss.com Date: 2011-01-24 06:44:39 -0500 (Mon, 24 Jan 2011) New Revision: 28542 Modified: trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.CR1.html trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.Beta1.html trunk/documentation/whatsnew/index.html trunk/documentation/whatsnew/vpe/vpe-news-3.2.0.CR1.html Log: JBIDE-8156 initial N&N fixes Modified: trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.CR1.html =================================================================== --- trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.CR1.html 2011-01-24 11:25:27 UTC (rev 28541) +++ trunk/documentation/whatsnew/bpel/bpel-news-1.1.0.CR1.html 2011-01-24 11:44:39 UTC (rev 28542) @@ -11,7 +11,7 @@ <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> +<p align="right"><a href="../index.html">< Main Index</a></p> <table border="0" cellpadding="10" cellspacing="0" width="80%"> <tr> <td colspan="2"> Modified: trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.Beta1.html =================================================================== --- trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.Beta1.html 2011-01-24 11:25:27 UTC (rev 28541) +++ trunk/documentation/whatsnew/cdi/cdi-news-3.2.0.Beta1.html 2011-01-24 11:44:39 UTC (rev 28542) @@ -12,87 +12,102 @@ <h1>CDI tools 3.2.0.Beta1 What's New</h1> <p align="right"><a href="../index.html">< Main Index</a> <a - href="../seam/seam-news-3.2.0.Beta1.html">Seam Tools News ></a></p> + href="../hibernate/hibernate-news-3.4.0.CR1.html">Hibernate Tools News ></a></p> <table border="0" cellpadding="10" cellspacing="0" width="80%"> -<tr> - <td colspan="2"> - <hr /> - <h3>Beans.xml Source Editor</h3> - <hr /> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>Code Completion</b></p> - </td> - <td align="top"> - <p>Now CDI Tools provide code completion for the relevant types/annotations in beans.xml</p> - <img src="images/3.2.0.Beta1/beansXmlCA.gif"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-2704">Related Jira</a></small></p> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>Hyperlinks (OpenOns)</b></p> - </td> - <td valign="top"> - <p>Class/Annotation names can now be navigated to via OpenOn.</p> - <img src="images/3.2.0.Beta1/beansXmlOpenOn.gif"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-7025">Related Jira</a></small></p> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>Validation</b></p> - </td> - <td valign="top"> - <p>All the classes/annotation names are now validated.</p> - <img src="images/3.2.0.Beta1/beansXmlValidation.gif"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-6523">Related Jira</a></small></p> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>Weld extension (beans_1_1.xsd)</b></p> - </td> - <td valign="top"> - <p>Weld extension (beans_1_1.xsd) is now supported by beans.xml editor.</p> - <img src="images/3.2.0.Beta1/beansXmlWeld.gif"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-6998">Related Jira</a></small></p> - </td> - </tr> -<tr> - <td colspan="2"> - <hr /> - <h3>OpenOn for Injected Class</h3> - <hr /> - </td> - </tr> - <tr> - <td valign="top" align="left"> - <p><b>OpenOn for Injected Class.</b></p> - </td> - <td valign="top"> - <p>OpenOn menu for injection points now gives more information about eligible beans. - </p> - <img src="images/3.2.0.Beta1/openOns1.png"/><br/><br/> - <img src="images/3.2.0.Beta1/openOns2.png"/> - <p><small><a - href="https://jira.jboss.org/browse/JBIDE-6640">Related Jira</a></small></p> - </td> - </tr> - - <tr> - <td colspan="2"> - <hr /> - </td> - </tr> - + <tr> + <td colspan="2"> + <hr /> + <h3>Beans.xml Source Editor</h3> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>Code Completion</b></p> + </td> + <td align="top"> + <p>Now CDI Tools provide code completion for the relevant types/annotations in beans.xml</p> + <img src="images/3.2.0.Beta1/beansXmlCA.gif"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-2704">Related Jira</a></small></p> + </td> + </tr> + <tr> + <td colspan="2"> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>Hyperlinks (OpenOns)</b></p> + </td> + <td valign="top"> + <p>Class/Annotation names can now be navigated to via OpenOn.</p> + <img src="images/3.2.0.Beta1/beansXmlOpenOn.gif"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-7025">Related Jira</a></small></p> + </td> + </tr> + <tr> + <td colspan="2"> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>Validation</b></p> + </td> + <td valign="top"> + <p>All the classes/annotation names are now validated.</p> + <img src="images/3.2.0.Beta1/beansXmlValidation.gif"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-6523">Related Jira</a></small></p> + </td> + </tr> + <tr> + <td colspan="2"> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>Weld extension (beans_1_1.xsd)</b></p> + </td> + <td valign="top"> + <p>Weld extension (beans_1_1.xsd) is now supported by beans.xml editor.</p> + <img src="images/3.2.0.Beta1/beansXmlWeld.gif"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-6998">Related Jira</a></small></p> + </td> + </tr> + <tr> + <td colspan="2"> + <hr /> + <h3>OpenOn for Injected Class</h3> + <hr /> + </td> + </tr> + <tr> + <td valign="top" align="left"> + <p><b>OpenOn for Injected Class.</b></p> + </td> + <td valign="top"> + <p>OpenOn menu for injection points now gives more information about eligible beans. + </p> + <img src="images/3.2.0.Beta1/openOns1.png"/><br/><br/> + <img src="images/3.2.0.Beta1/openOns2.png"/> + <p><small><a + href="https://jira.jboss.org/browse/JBIDE-6640">Related Jira</a></small></p> + </td> + </tr> + + <tr> + <td colspan="2"> + <hr /> + </td> + </tr> + </table> </body> Modified: trunk/documentation/whatsnew/index.html =================================================================== --- trunk/documentation/whatsnew/index.html 2011-01-24 11:25:27 UTC (rev 28541) +++ trunk/documentation/whatsnew/index.html 2011-01-24 11:44:39 UTC (rev 28542) @@ -20,6 +20,18 @@ </td> </tr> + <tr> + <td valign="top" align="left"> + <p align="right"><b>3.2.0.CR1</b> + <td valign="top"> + <p><a href="cdi/cdi-news-3.2.0.Beta1.html">CDI (JSR-299) Tools</a></p> + <p><a href="hibernate/hibernate-news-3.4.0.CR1.html">Hibernate Tools</a></p> + <p><a href="jst/jst-news-3.2.0.CR1.html">JST/JSF Tools</a></p> + <p><a href="vpe/vpe-news-3.2.0.CR1.html">Visual Page Editor</a></p> + <p><a href="bpel/bpel-news-1.1.0.CR1.html">BPEL Tools</a></p> + </td> + </tr> + <tr> <td valign="top" align="left"> Modified: trunk/documentation/whatsnew/vpe/vpe-news-3.2.0.CR1.html =================================================================== --- trunk/documentation/whatsnew/vpe/vpe-news-3.2.0.CR1.html 2011-01-24 11:25:27 UTC (rev 28541) +++ trunk/documentation/whatsnew/vpe/vpe-news-3.2.0.CR1.html 2011-01-24 11:44:39 UTC (rev 28542) @@ -12,7 +12,7 @@ <h1>What's New Visual Page Editor</h1> <p align="right"><a href="../index.html">< Main Index</a> <a - href="../portlet/portlet-news-1.0.0.CR1.html">Portal Tools ></a></p> + href="../bpel/bpel-news-1.1.0.CR1.htm">BPEL Tools ></a></p> <table border="0" cellpadding="10" cellspacing="0" width="80%"> <tr> <td colspan="2">

13 years, 5 months

1
0
0 / 0

JBoss Tools SVN: r28541 - trunk/jsf/tests/org.jboss.tools.jsf.ui.bot.test/src/org/jboss/tools/jsf/ui/bot/test/jsf2/refactor.

by jbosstools-commits＠lists.jboss.org

Author: vpakan(a)redhat.com Date: 2011-01-24 06:25:27 -0500 (Mon, 24 Jan 2011) New Revision: 28541 Modified: trunk/jsf/tests/org.jboss.tools.jsf.ui.bot.test/src/org/jboss/tools/jsf/ui/bot/test/jsf2/refactor/JSF2AttributeRenameTest.java Log: Remove debug message. Modified: trunk/jsf/tests/org.jboss.tools.jsf.ui.bot.test/src/org/jboss/tools/jsf/ui/bot/test/jsf2/refactor/JSF2AttributeRenameTest.java =================================================================== --- trunk/jsf/tests/org.jboss.tools.jsf.ui.bot.test/src/org/jboss/tools/jsf/ui/bot/test/jsf2/refactor/JSF2AttributeRenameTest.java 2011-01-24 08:56:29 UTC (rev 28540) +++ trunk/jsf/tests/org.jboss.tools.jsf.ui.bot.test/src/org/jboss/tools/jsf/ui/bot/test/jsf2/refactor/JSF2AttributeRenameTest.java 2011-01-24 11:25:27 UTC (rev 28541) @@ -91,7 +91,6 @@ SWTBotStyledText styledText = bot.styledText(0); assertEquals( loadFileContent("refactor/compositeComponent.html"), styledText.getText()); //$NON-NLS-1$ - System.out.println(styledText.getText()); } }

13 years, 5 months

1
0
0 / 0

JBoss Tools SVN: r28540 - trunk/documentation/whatsnew/drools.

by jbosstools-commits＠lists.jboss.org

Author: max.andersen(a)jboss.com Date: 2011-01-24 03:56:29 -0500 (Mon, 24 Jan 2011) New Revision: 28540 Modified: trunk/documentation/whatsnew/drools/guvnor-tools-news-5.1.0.Beta2.html Log: left over old n&n fix. Modified: trunk/documentation/whatsnew/drools/guvnor-tools-news-5.1.0.Beta2.html =================================================================== --- trunk/documentation/whatsnew/drools/guvnor-tools-news-5.1.0.Beta2.html 2011-01-24 06:18:05 UTC (rev 28539) +++ trunk/documentation/whatsnew/drools/guvnor-tools-news-5.1.0.Beta2.html 2011-01-24 08:56:29 UTC (rev 28540) @@ -11,7 +11,7 @@ <body> <h1>Drools Guvnor 5.1.0.Beta2 What's New</h1> -<p align="right"><a href="../index.html">< Main Index</a> <a href="../bpel/bpel-news-1.1.0.beta1.html">BPEL Tools ></a></p> +<p align="right"><a href="../index.html">< Main Index</a> <a href="../bpel/bpel-news-1.1.0.beta2.html">BPEL Tools ></a></p> <table border="0" cellpadding="10" cellspacing="0" width="80%">

13 years, 5 months

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-24 01:18:05 -0500 (Mon, 24 Jan 2011) New Revision: 28539 Modified: trunk/hibernatetools/docs/reference/en-US/codegen.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/codegen.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/codegen.xml 2011-01-24 05:53:28 UTC (rev 28538) +++ trunk/hibernatetools/docs/reference/en-US/codegen.xml 2011-01-24 06:18:05 UTC (rev 28539) @@ -3,18 +3,18 @@ <title>Controlling POJO code generation</title> <para> - When using <code><hbm2java></code> or the Eclipse plugin to generate POJO Java code you have the ability to control certain aspects of the code generation. This is primarily done with the <code><meta></code> tag in the mapping files. The following section describes the possible <code><meta></code> tags and their use. + When using the <code><hbm2java></code> tag or the Eclipse plugin to generate POJO Java code you have the ability to control certain aspects of the code generation process. This is primarily done with the <code><meta></code> tag in the mapping files. The following section describes the possible <code><meta></code> tags and their use. </para> <section> <title>The <meta> attribute</title> <para> - The <code><meta></code> tag is a simple way of annotating the <filename>hbm.xml</filename> with information, so tools have a natural place to store and read information that is not directly related to the Hibernate core. + The <code><meta></code> tag is a simple way of annotating the <filename>hbm.xml</filename> file with information, so tools have a natural place to store and read information that is not directly related to the Hibernate core. </para> <para> - As an example, you can use the <code><meta></code> tag to tell <code><hbm2java></code> to only generate <code>"protected"</code> setters, have classes always implement a certain set of interfaces or even have them extend a certain base class and even more. + As an example, you can use the <code><meta></code> tag to tell the <code><hbm2java></code> tag to only generate <code>"protected"</code> setters, have classes always implement a certain set of interfaces, have them extend a certain base class and more. </para> <para>The following example shows how to use various <code><meta></code> attributes and the resulting Java code.</para> @@ -35,7 +35,7 @@ </class>]]></programlisting> <para> - The above <filename>hbm.xml</filename> file will produce something like the following (the code abbreviated for clarity). Notice the Javadoc comment and the protected set methods: + The above <filename>hbm.xml</filename> file will produce something like the following (the code has been abbreviated for clarity). Notice the Javadoc comment and the protected set methods: </para> <programlisting role="JAVA"><![CDATA[// default package @@ -242,22 +242,22 @@ </table> <para> - Attributes declared via the <code><meta></code> tag are per default <code>"inherited"</code> inside an <code>hbm.xml</code> file. + Attributes declared via the <code><meta></code> tag <code>"inherited"</code> inside an <code>hbm.xml</code> file by default. </para> <para> - What does that mean? As an example if you want to have all your classes implement <code>IAuditable</code> then you just add an <code> <meta attribute="implements">IAuditable</meta></code> in the top of the <filename>hbm.xml</filename> file, just after <code><hibernate-mapping></code>. Now all classes defined in that <filename>hbm.xml</filename> file will implement <property>IAuditable</property>. + What does that mean? As an example if you want to have all your classes implement <code>IAuditable</code> then you just add <code> <meta attribute="implements">IAuditable</meta></code> in the top of the <filename>hbm.xml</filename> file, just after <code><hibernate-mapping></code>. Now all classes defined in that <filename>hbm.xml</filename> file will implement <code>IAuditable</code>. </para> <note> <title>Note:</title> <para> - This applies to <emphasis>all</emphasis> <code><meta></code>-tags. Thus it can also be used to specify that all fields should be declare protected, instead of the default private. This is done by adding <code><meta attribute="scope-field">protected</meta></code> just under the <code><class></code> tag and all fields of that class will be protected. + This applies to <emphasis>all</emphasis> <code><meta></code>-tags. Thus it can also be used to specify that all fields should be declare <code>protected</code>, instead of the default <code>private</code>. This is done by adding <code><meta attribute="scope-field">protected</meta></code> just under the <code><class></code> tag, and all fields of that class will be <code>protected</code>. </para> </note> <para> - To avoid having a <code><meta></code> tag inherited then you can simply specify <code> inherit = "false"</code> for the attribute. For example <code> <meta attribute = "scope-class" inherit = "false">public abstract</meta></code> will restrict the <code>"class-scope"</code> to the current class, not the subclasses. + To avoid having a <code><meta></code> tag inherited then you can specify <code> inherit = "false"</code> for the attribute. For example <code> <meta attribute = "scope-class" inherit = "false">public abstract</meta></code> will restrict the <code>"class-scope"</code> to the current class, not the subclasses. </para> <section> @@ -266,10 +266,10 @@ <para>The following are some good practices to employ when using <code><meta></code> attributes.</para> <section> - <title>Dangers of a class level <property>use-in-string and use-in-equals</property> meta attributes when having bi-directional associations</title> + <title>Dangers of a class level <property>use-in-string and use-in-equals</property> meta attributes when using bi-directional associations</title> <para> - If we have two entities with a bi-directional association between them and define at class scope level the meta attributes: <code>use-in-string</code>, <code>use-in-equals</code>: + In the following example we have two entities with a bi-directional association between them and define the <code>use-in-string</code> and <code>use-in-equals</code> meta attributes at the class scope level the meta attributes: </para> <programlisting role="XML"><![CDATA[<hibernate-mapping> @@ -280,7 +280,7 @@ </class> </hibernate-mapping>]]></programlisting> - <para>And for <filename>Event.hbm</filename> file:</para> + <para>Here is the <filename>Event.hbm</filename> file:</para> <programlisting role="XML"><![CDATA[<hibernate-mapping> <class name="events.Event" table="EVENTS"> @@ -299,14 +299,14 @@ </hibernate-mapping>]]></programlisting> <para> - Then <code><hbm2java></code> will assume you want to include all properties and collections in the <code>toString()</code> and <code>equals()</code> methods and this can result in infinite recursive calls. + In this situation the <code><hbm2java></code> tag will assume you want to include all properties and collections in the <code>toString()</code> and <code>equals()</code> methods. This can result in infinite recursive calls. </para> <para> - To remedy this you have to decide which side of the association will include the other part (if at all) in the <code>toString()</code> and <code>equals()</code> methods. Therefore it is not a good practice to put at class scope such <code>meta</code> attributes, unless you are defining a class without bi-directional associations. + To remedy this you have to decide which side of the association will include the other part (if at all) in the <code>toString()</code> and <code>equals()</code> methods. Therefore it is not a good practice to define these <code>meta</code> attributes at the class scope, unless you are defining a class without bi-directional associations. </para> - <para>We recommend instead to add the <code>meta</code> attributes at the property level:</para> + <para>Instead it is recommended that the <code>meta</code> attributes are defined at the property level, like so:</para> <programlisting role="XML"><![CDATA[<hibernate-mapping> <class name="events.Event" table="EVENTS"> @@ -326,7 +326,7 @@ </class> </hibernate-mapping>]]></programlisting> - <para>and now for <code>Person</code>:</para> + <para>and for <code>Person</code>:</para> <programlisting role="XML"><![CDATA[<hibernate-mapping> <class name="Person"> @@ -352,7 +352,7 @@ <title>Be aware of putting at class scope level <meta> attributeuse-in-equals</title> <para> - For <code>equal()</code> and <code>hashCode()</code> method generation, you have to take into account that the attributes that participate on such method definition, should take into account only attributes with business meaning (the name, social security number, etc, but no generated id's, for example). + Only attributes with business meaning (e.g. the name, social security number, etc, but no generated id's) should be referenced when calculating the return value for the <code>equal()</code> and <code>hashCode()</code> methods. </para> <para> @@ -364,7 +364,7 @@ </para> <para> - On <ulink url="http://www.hibernate.org/109.html">www.hibernate.org </ulink> you can get a more in-depth explanation on the subject of <code>equals()</code> and <code>hashcode()</code> methods. + On <ulink url="http://www.hibernate.org/109.html">www.hibernate.org </ulink> you can find more in-depth explanation on the subject of <code>equals()</code> and <code>hashcode()</code> methods. </para> </section> </section> @@ -373,29 +373,29 @@ <title>Advanced <meta> attribute examples</title> <para> - This section shows an example for using meta attributes (including userspecific attributes) together with the code generation features in <productname>Hibernate Tools</productname>. + This section shows an example for using meta attributes (including user specific attributes) together with the code generation features in <productname>Hibernate Tools</productname>. </para> - <para>The example shown below automatically inserts some pre and post conditions into the getter and setters of the generated POJO. </para> + <para>The example shown below automatically inserts some pre and post conditions into the getter and setter methods of the generated POJO. </para> <section> <title>Generate pre/post-conditions for methods</title> <para> - With the <code> <meta attribute="class-code"></code>, you can add additional methods on a given class, nevertheless such <code><meta></code> attribute can not be used at a property scope level and <property>Hibernate Tools</property> does not provide such <code><meta></code> attributes. + With <code> <meta attribute="class-code"></code> you can add additional methods on a given class. However, such <code><meta></code> attributes can not be used at a property scope level and <property>Hibernate Tools</property> does not provide such <code><meta></code> attributes. </para> <para> - A possible solution for this is to modify the freemarker templates responsible for generating the POJO's. If you look inside <filename>hibernate-tools.jar</filename>, you can find the template <filename>pojo/PojoPropertyAccessor.ftl</filename>. + A possible solution for this is to modify the Freemarker templates responsible for generating the POJOs. If you look inside the <filename>hibernate-tools.jar</filename> archive, you can find the template <filename>pojo/PojoPropertyAccessor.ftl</filename>. </para> - <para>As its name indicates, this file is used to generate property accessors for POJO's.</para> + <para>As its name indicates, this file is used to generate property accessors for POJOs.</para> <para> - Extract the <filename>PojoPropertyAccessor.ftl</filename> into a local folder i.e. <filename>${hbm.template.path}</filename>, respecting the whole path, for example: <filename>${hbm.template.path}/pojo/PojoPropertyAccessor.ftl</filename>. + Extract the <filename>PojoPropertyAccessor.ftl</filename> file into a local folder e.g. <filename>${hbm.template.path}</filename>, respecting the whole path, for example: <filename>${hbm.template.path}/pojo/PojoPropertyAccessor.ftl</filename>. </para> - <para>The contents of the file is something like this:</para> + <para>The contents of the file will be something like this:</para> <programlisting role="XML"><![CDATA[<#foreach property in pojo.getAllPropertiesIterator()> ${pojo.getPropertyGetModifiers(property)} @@ -412,7 +412,7 @@ </#foreach>]]></programlisting> <para> - We can add conditionally pre and post conditions on our <code>set</code> method generation just adding a little Freemarker syntax to the above source code: + We can add pre and post conditions on our <code>set</code> method generation just by adding a little Freemarker syntax to the above source code: </para> <programlisting role="XML"><![CDATA[<#foreach property in pojo.getAllPropertiesIterator()> @@ -442,7 +442,7 @@ </para> <para> - As an example let us add a pre-condition for property <code>name</code> which will prevent the <code>Person</code> class from having an empty name. To achieve this we have to modify the <filename>Person.hbm.xml</filename> file like so: + As an example let us add a pre-condition for the <code>name</code> property which will prevent the <code>Person</code> class from having an empty name. To achieve this we have to modify the <filename>Person.hbm.xml</filename> file like so: </para> <programlisting role="XML"><![CDATA[<hibernate-mapping> @@ -462,14 +462,14 @@ <note> <title>Note:</title> - <para>I) To escape the & symbol we put &amp;. You can use <code> <![CDATA[]]></code> instead.</para> + <para>I) To escape the & symbol we put &amp;. You could use <code> <![CDATA[]]></code> instead.</para> <para> II) Note that we are referring to <code>firstName</code> directly and this is the parameter name not the actual field name. If you want to refer the field you have to use <code>this.firstName</code> instead. </para> </note> <para> - Finally we have to generate the <filename>Person.java</filename> class. For this we can use both Eclipse and Ant, as long as you remember to set or fill in the templatepath setting. For Ant we configure <code><hibernatetool></code> task via <literal>the templatepath</literal> attribute as in: + Finally we have to generate the <filename>Person.java</filename> class. For this we can use either Eclipse or Ant, as long as you remember to set or fill in the <code>templatepath</code> setting. For Ant we configure the <code><hibernatetool></code> task via the <code>templatepath</code> attribute as in: </para> <programlisting role="XML"><![CDATA[ @@ -492,7 +492,7 @@ </target>]]></programlisting> <para> - Invoking the target <code><hbm2java></code> will generate on the <filename>${hbm2java.dest.dir}</filename> the file <filename>Person.java</filename>: + Invoking the target <code><hbm2java></code> will generate file <filename>Person.java</filename> in <filename>${hbm2java.dest.dir}</filename>: </para> <programlisting role="JAVA"><![CDATA[// default package @@ -531,11 +531,11 @@ }]]></programlisting> <para> - In conclusion, this document is intended to introduce you to Hibernate plugin specific features related to tools bath for the Eclipse and Ant tasks. + In conclusion, this document is intended to introduce you to Hibernate plugin specific features related to tools both for the Eclipse and Ant tasks. </para> <para> - In the <xref linkend="plugins"/> chapter you've learned about a set of wizards for creating Mapping files, Configuration file, Console Configuration, become familiar with Mapping and Configuration files editors, tooling for organizing and controlling Reverse Engineering, Hibernate Console and Mapping diagram as well. + In <xref linkend="plugins"/> you've learned about a set of wizards for creating Mapping files, Configuration files, Console Configurations, become familiar with Mapping and Configuration files editors, tooling for organizing and controlling Reverse Engineering, Hibernate Console and Mapping diagrams. </para> <para>The rest chapters have explored the use of the <productname>Hibernate Tools</productname> via Ant tasks.</para>

13 years, 5 months

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-24 00:53:28 -0500 (Mon, 24 Jan 2011) New Revision: 28538 Modified: trunk/hibernatetools/docs/reference/en-US/reverseengineering.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/reverseengineering.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/reverseengineering.xml 2011-01-24 05:36:46 UTC (rev 28537) +++ trunk/hibernatetools/docs/reference/en-US/reverseengineering.xml 2011-01-24 05:53:28 UTC (rev 28538) @@ -3,22 +3,25 @@ <title>Controlling reverse engineering</title> <para> - When using the <code><jdbcconfiguration></code>, the Ant task will read the database metadata and then perform a reverse engineering of the database schema into a normal Hibernate Configuration. It is from this object e.g. <code><hbm2java></code>can generate other artifacts such as <filename>.java</filename>, <filename>.hbm.xml</filename> etc. + When using the <code><jdbcconfiguration></code> tag, the Ant task will read the database metadata and then reverse engineer the database schema into a normal Hibernate Configuration. It is from this object (e.g. <code><hbm2java></code>) that other artifacts, such as <filename>.java</filename> and <filename>.hbm.xml</filename>, can be generated. </para> <para> - To govern this process <productname>Hibernate</productname> uses a reverse engineering strategy. A reverse engineering strategy is mainly called to provide more Java like names for tables, column and foreign keys into classes, properties and associations. It also used to provide mappings from SQL types to <productname>Hibernate</productname> types. The strategy can be customized by a user. The user can even provide its own custom reverse engineering strategy if the provided strategy does not provide the required functionality, or simply define a small component of the strategy and delegate the rest to the default strategy. + To govern this process <productname>Hibernate</productname> uses a reverse engineering strategy. A reverse engineering strategy is mainly called to provide more Java like names for tables, column and foreign keys into classes, properties and associations. It is also used to provide mappings from SQL types to <productname>Hibernate</productname> types. </para> + <para> + The strategy can be customized by the user. This can be done by providing a custom reverse engineering strategy should the default strategy does not include the required functionality, or simply define a small component of the strategy and delegate the rest to the default strategy. + </para> <para> - Thus, further in this chapter we will discuss how you can configure the process of reverse engineering, what the default reverse engineering strategy includes as well as some custom concepts. + Further in this chapter we will discuss how you can configure the process of reverse engineering, what the default reverse engineering strategy includes, as well as some custom concepts. </para> <section> <title>Default reverse engineering strategy</title> <para> - The default strategy uses some rules for mapping JDBC artifact names to java artifact names. It also provide basic typemappings from JDBC types to <productname>Hibernate</productname> types. It is the default strategy that uses the packagename attribute to convert a table name to a fully qualified classname. + The default strategy uses a collection of rules for mapping JDBC artifact names to Java artifact names. It also provide basic type mappings from JDBC types to <productname>Hibernate</productname> types. It is the default strategy that uses the <code>packagename</code> attribute to convert a table name into a fully qualified class name. </para> </section> @@ -26,17 +29,17 @@ <title>hibernate.reveng.xml file</title> <para> - A <filename>hibernate.reveng.xml</filename> file can provide a finer degree of control of the process. In this file you can specify type mappings and table filtering. This file can be created by hand (it's just basic XML) or you can use the <ulink url="http://www.hibernate.org/30.html">Hibernate plugins</ulink> which has a specialized editor. + A <filename>hibernate.reveng.xml</filename> file can provide a finer degree of control of the reverse engineering process. In this file you can specify type mappings and table filtering. This file can be created by hand (it's just basic XML) or you can use the <ulink url="http://www.hibernate.org/30.html">Hibernate plugins</ulink>, which provides a specialized editor. </para> <note> <title>Note:</title> <para> - Many databases have case-sensitive names and thus if a table does not match, and you are sure it is not excluded by a <code><table-filter></code>, check if the case matches. Most databases stores table names in uppercase. + Many databases have case-sensitive names, so if a table does not match, and you are sure it is not excluded by a <code><table-filter></code>, check that the case matches. Most databases stores table names in uppercase. </para> </note> - <para>Below you can see an example of a <filename>reveng.xml</filename> file. Following the example gives you more details about the format.</para> + <para>Below you can see an example of a <filename>reveng.xml</filename> file.</para> <programlisting role="XML"><![CDATA[<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE hibernate-reverse-engineering @@ -93,20 +96,20 @@ <section> <title>Schema Selection (<schema-selection>)</title> - <para><code><schema-selection></code> is used to determine which schemas the reverse engineering will try and process.</para> + <para>The <code><schema-selection></code> tag is used to determine which schemas the reverse engineering will try and process.</para> <para> - By default the reverse engineering will read all schemas and then use <code><table-filter></code> to decide which tables get reverse engineered and which do not; this makes it easy to get started but can be inefficient on databases with many schemas. + By default the reverse engineering will read all schemas and then use the <code><table-filter></code> tag to decide which tables are reverse engineered and which are not. This makes it easy to get started but can be inefficient on databases with many schemas. </para> <para> - With <code><schema-selection></code> it is thus possible to limit which schemas are processed, thus significantly speed-up the reverse engineering. <code><table-filter></code> is still used to then decide which tables will be included and excluded. + With the <code><schema-selection></code> tag it is thus possible to limit which schemas are processed, which in turn can significantly speed-up the reverse engineering. The <code><table-filter></code> tag is still used to then decide which tables will be included and excluded. </para> <note> <title>Note:</title> <para> - If no <code><schema-selection></code> is specified, the reverse engineering works as if all schemas should be processed. This is equal to: <![CDATA[<schema-selection/>]]>, which in turn is equal to: <![CDATA[<schema-selection match-catalog=".*" match-schema=".*" match-table=".*"/>]]> + If no <code><schema-selection></code> tag is specified, the reverse engineering works as if all schemas should be processed. This is equal to: <![CDATA[<schema-selection/>]]>, which in turn is equal to: <![CDATA[<schema-selection match-catalog=".*" match-schema=".*" match-table=".*"/>]]> </para> </note> @@ -118,7 +121,7 @@ <programlisting role="XML"><![CDATA[<schema-selection match-schema="MY_SCHEMA"/>]]></programlisting> <para> - It is possible to have multiple <code>schema-selection</code>'s to support multi-schema reading, or simply to limit the processing to very specific tables. The following example processes all tables in <code>"MY_SCHEMA"</code>, a specific <code>"CITY"</code> table plus all tables that start with <code>"CODES_"</code> in <code>"COMMON_SCHEMA"</code>. + It is possible to have multiple <code>schema-selection</code>'s to support multi-schema reading, or to limit the processing to very specific tables. The following example processes all tables in <code>"MY_SCHEMA"</code>, a specific <code>"CITY"</code> table plus all tables that start with <code>"CODES_"</code> in <code>"COMMON_SCHEMA"</code>. </para> <programlisting role="XML"><![CDATA[<schema-selection match-schema="MY_SCHEMA"/> @@ -146,13 +149,13 @@ </type-mapping>]]></programlisting> <para> - The number of attributes specified and the sequence of the <code>sql-type</code>'s is important. Meaning that <productname>Hibernate</productname> will search for the most specific first, and if no specific match is found it will seek from top to bottom when trying to resolve a type mapping. + The number of attributes specified and the sequence of the <code>sql-type</code> tags are important. This is because <productname>Hibernate</productname> will search for the most specific first, and if no specific match is found it will seek from top to bottom when trying to resolve a type mapping. </para> <section> <title>Example</title> - <para>The following is an example of a type-mapping which shows the flexibility and the importance of the ordering of the type mappings.</para> + <para>The following is an example of a type-mapping which shows the flexibility and importance of the ordering of the type mappings.</para> <programlisting role="XML"><![CDATA[<type-mapping> <sql-type jdbc-type="NUMERIC" precision="15" hibernate-type="big_decimal"/> @@ -314,7 +317,7 @@ <title>Table filters (<table-filter>)</title> <para> - The <code><table-filter></code> lets you specify matching rules for performing general filtering and setup for tables, e.g. let you include or exclude specific tables based on the schema or even a specific prefix. + The <code><table-filter></code> tag lets you specify matching rules for performing general filtering and setup of tables, e.g. let you include or exclude specific tables based on the schema or even a specific prefix. </para> <programlisting role="XML"><![CDATA[<table-filter @@ -400,7 +403,7 @@ <title>Specific table configuration (<table>)</title> <para> - <code><table></code> allows you to provide explicit configuration on how a table should be reverse engineered. Amongst other things it allows control over the naming of a class for the table, provides a way to specify which identifier generator should be used for the primary key etc. + The <code><table></code> tag allows you to explicitly define how a table should be reverse engineered. It allows control over the naming of a class for the table, provides a way to specify which identifier generator should be used for the primary key and more. </para> <programlisting role="XML"><![CDATA[<table @@ -485,7 +488,7 @@ <title><primary-key></title> <para> - A <code><primary-key></code> allows you to define a primary-key for tables that do not have one defined in the database, and probably more importantly it allows you to define which identifier strategy should be used (even for already existing primary-key's). + A <code><primary-key></code> tag allows you to define a primary-key for tables that do not have one defined in the database, and more importantly it allows you to define which identifier strategy should be used (even for preexisting primary-key's). </para> <programlisting role="XML"><![CDATA[<primary-key @@ -561,7 +564,7 @@ <title><column></title> <para> - With a <code><column></code> it is possible to explicitly name the resulting property for a column. It is also possible to redefine what JDBC and/or Hibernate type a column should be processed as and finally it is possible to completely exclude a column from processing. + With a <code><column></code> tag it is possible to explicitly name the resulting property for a column, to redefine what JDBC and/or Hibernate type a column should be processed as, and to completely exclude a column from processing. </para> <programlisting role="XML"><![CDATA[<column @@ -651,7 +654,7 @@ <title><foreign-key></title> <para> - The <code><foreign-key></code> has two purposes. The first is to define foreign-keys in databases that does not support them or do not have them defined in their schema. The second is to define the name of the resulting properties (many-to-one, one-to-one and one-to-many's). + The <code><foreign-key></code> tag has two purposes. The first is to define foreign-keys in databases that does not support them or do not have them defined in their schema. The second is to define the name of the resulting properties (many-to-one, one-to-one and one-to-many's). </para> <programlisting role="XML"><![CDATA[<foreign-key @@ -807,7 +810,7 @@ <title>Custom strategy</title> <para> - It is possible to implement a user strategy. Such a strategy must implement <code>org.hibernate.cfg.reveng.ReverseEngineeringStrategy</code>. It is recommended that you use the <code>DelegatingReverseEngineeringStrategy</code> and provide a public constructor which takes another <code>ReverseEngineeringStrategy</code> as an argument. This will allow you to only implement the relevant methods and provide a fall back strategy. Below is an example of a custom delegating strategy which converts all column names that ends with <code>"PK"</code> into a property named <code>"id"</code>. + It is possible to implement a user strategy. Such a strategy must implement <code>org.hibernate.cfg.reveng.ReverseEngineeringStrategy</code>. It is recommended that you use the <code>DelegatingReverseEngineeringStrategy</code> and provide a public constructor which takes another <code>ReverseEngineeringStrategy</code> as an argument. This will allow you to only implement the relevant methods and provide a fall back strategy. An example is shown below of a custom delegating strategy that converts all column names ending with <code>"PK"</code> into a property named <code>"id"</code>. </para> <programlisting role="JAVA"><![CDATA[public class ExampleStrategy extends DelegatingReverseEngineeringStrategy { @@ -830,11 +833,11 @@ <title>Custom Database Metadata</title> <para> - By default the reverse engineering is performed using the JDBC database metadata API. This is done via the class <code>org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect</code> which is an implementation of <code>org.hibernate.cfg.reveng.dialect.MetaDataDialect</code>. + By default the reverse engineering is performed using the JDBC database metadata API. This is done via the class <code>org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect</code>, which is an implementation of <code>org.hibernate.cfg.reveng.dialect.MetaDataDialect</code>. </para> <para> - The default implementation can be replaced with an alternative implementation by setting the property <code>hibernatetool.metadatadialect</code> to a fully qualified classname for a class that implements <code>JDBCMetaDataDialect</code>. + The default implementation can be replaced with an alternative implementation by setting the <code>hibernatetool.metadatadialect</code> property to a fully qualified class name for a class that implements <code>JDBCMetaDataDialect</code>. </para> <para>

13 years, 5 months

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-24 00:36:46 -0500 (Mon, 24 Jan 2011) New Revision: 28537 Modified: trunk/hibernatetools/docs/reference/en-US/ant.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/ant.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/ant.xml 2011-01-24 05:28:50 UTC (rev 28536) +++ trunk/hibernatetools/docs/reference/en-US/ant.xml 2011-01-24 05:36:46 UTC (rev 28537) @@ -8,14 +8,14 @@ <title>Introduction</title> <para> - The <filename>hibernate-tools.jar</filename> contains the core for the <productname>Hibernate Tools</productname>. It is used as the basis for both the Ant tasks described in this document and the eclipse plugins both available from tools.hibernate.org. The <filename>hibernate-tools.jar</filename> file is located in your eclipse plugins directory at <filename>/plugins/org.hibernate.eclipse.x.x.x/lib/tools/hibernate-tools.jar</filename>. + The <filename>hibernate-tools.jar</filename> file contains the core code for <productname>Hibernate Tools</productname>. It is used as the basis for both the Ant tasks described in this document and the Eclipse plugins both available from <ulink url="http://www.hibernate.org/subprojects/tools.html">tools.hibernate.org</ulink>. The <filename>hibernate-tools.jar</filename> file is located in your Eclipse plugins directory at <filename>/plugins/org.hibernate.eclipse.x.x.x/lib/tools/hibernate-tools.jar</filename>. </para> <para>This jar is 100% independent from the Eclipse platform and can thus be used independently of Eclipse.</para> <note> <title>Note:</title> <para> - There might be incompatibilities with respect to the <filename>Hibernate3.jar</filename> bundled with the tools and your own jar. Thus to avoid any confusion it is recommended that you use the <filename>hibernate3.jar</filename> and <filename>hibernate-annotations.jar</filename> files bundled with the tools when you want to use the Ant tasks. Do not worry about using the jar's from a later version of Hibernate (e.g. Hibernate 3.2) with a project using an earlier version of Hibernate (e.g. a Hibernate 3.1) since the output generated will work with previous Hibernate 3 versions. + There may be incompatibilities with respect to the <filename>hibernate3.jar</filename> bundled with the tools and your own JAR. To avoid any confusion it is recommended that you use the <filename>hibernate3.jar</filename> and <filename>hibernate-annotations.jar</filename> files bundled with the tools when you want to use the Ant tasks. Do not worry about using the JAR's from a later version of Hibernate (e.g. Hibernate 3.2) with a project using an earlier version of Hibernate (e.g. a Hibernate 3.1) since the generated output will work with previous Hibernate 3 versions. </para> </note> </section> @@ -24,7 +24,7 @@ <title>The <hibernatetool> Ant Task</title> <para> - To use the ant tasks you need to have the <emphasis><property>hibernatetool</property></emphasis> task defined. That is done in your <filename>build.xml</filename> by inserting the following xml (assuming the jars are in the <filename>lib</filename> directory): + To use the Ant tasks you need to have the <code>hibernatetool</code> task defined. That is done in your <filename>build.xml</filename> file by inserting the following XML (assuming the JARs are located in the <filename>lib</filename> directory): </para> <programlisting role="XML"><![CDATA[<path id="toolslib"> @@ -40,7 +40,7 @@ ]]></programlisting> <para> - This <code><taskdef></code> defines an Ant task called <emphasis><property> hibernatetool </property></emphasis> which now can be used anywhere in your Ant <filename>build.xml</filename> files. It is important to include all the <productname>Hibernate Tools</productname> dependencies as well as the JDBC driver. + This <code><taskdef></code> defines an Ant task called <code> hibernatetool </code> which now can be used anywhere in your Ant <filename>build.xml</filename> files. It is important to include all the <productname>Hibernate Tools</productname> dependencies as well as the JDBC driver. </para> <para> @@ -49,7 +49,7 @@ <para/> - <para>When using the <emphasis><property> hibernatetool </property></emphasis> task you have to specify one or more of the following:</para> + <para>When using the <code>hibernatetool</code> task you have to specify one or more of the following:</para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="defaultDestinationDirectory" @@ -92,7 +92,7 @@ </entry> <entry> - <para>Destination directory for files generated with exporters</para> + <para>Destination directory for files generated with the exporters</para> </entry> <entry> @@ -135,7 +135,7 @@ </entry> <entry> - <para>Used to set properties to control the exporters. Mostly relevant for providing custom properties to user defined templates</para> + <para>Used to set properties that control the exporters. Mostly relevant for providing custom properties to user defined templates</para> </entry> <entry> @@ -180,7 +180,7 @@ <title>Basic examples</title> <para> - The following example shows the most basic setup for generating pojo's via <code><hbm2java></code> from a normal <filename>hibernate.cfg.xml</filename>. The output will be put in the <filename>${build.dir}/generated</filename> directory. + The following example shows the most basic setup for generating POJOs via <code><hbm2java></code> from a normal <filename>hibernate.cfg.xml</filename>. The output will be placed in the <filename>${build.dir}/generated</filename> directory. </para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> @@ -194,7 +194,11 @@ <para> - The following example is similar, but now we are performing multiple exports from the same configuration. We are exporting the schema via <code><hbm2dll></code>, generating some DAO code via <code><hbm2dao></code> and finally running a custom code generation via <code><hbmtemplate></code>. This is again from a normal <filename>hibernate.cfg.xml</filename> file and the output is still placed in the <filename>${build.dir}/generated</filename> directory. Furthermore the example also shows how a classpath is specified, which is useful when you have custom usertypes or some mappings that is needed to be looked up as a classpath resource. + The following example is similar, but now we are performing multiple exports from the same configuration. We are exporting the schema via <code><hbm2dll></code>, generating some DAO code via <code><hbm2dao></code> and finally running some custom code generation via <code><hbmtemplate></code>. This is again from a normal <filename>hibernate.cfg.xml</filename> file, and the output is still placed in the <filename>${build.dir}/generated</filename> directory. + </para> + + <para> + The example also shows how a classpath is specified, which is useful when you have custom user types or some mappings that is needed to be looked up as a classpath resource. </para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> @@ -219,27 +223,27 @@ <title>Hibernate Configurations</title> <para> - <emphasis>Hibernatetool</emphasis> supports four different Hibernate configurations: A standard Hibernate configuration (<code><configuration></code>), Annotation based configuration (<code><annotationconfiguration></code>), JPA persistence based configuration (<code><jpaconfiguration></code>) and a JDBC based configuration (<code><jdbcconfiguration></code>) for use when reverse engineering. + <emphasis>Hibernatetool</emphasis> supports four different Hibernate configurations: A standard Hibernate configuration (<code><configuration></code>), Annotation based configuration (<code><annotationconfiguration></code>), JPA persistence based configuration (<code><jpaconfiguration></code>) and a JDBC based configuration (<code><jdbcconfiguration></code>) used when reverse engineering. </para> <para> - Each have in common the fact that they are able to build up a Hibernate Configuration object, from which a set of exporters can be run in order to generate various output. + Each can be used to build a Hibernate Configuration object, from which a set of exporters can be run in order to generate various output formats. </para> <note> <title>Note:</title> <para> - Output can be anything, e.g. specific files, statements execution against a database, error reporting or anything else that can be done in java code. + Output can be anything, e.g. specific files, statements execution against a database, error reporting or anything else that can be done in Java code. </para> </note> - <para>The following sections describe what the various configurations can do, plus lists the individual settings they have.</para> + <para>The following sections describe what the various configurations can do, as well as listing their individual settings.</para> <section> <title>Standard Hibernate Configuration (<configuration>)</title> <para> - A <code><configuration></code> is used to define a standard Hibernate configuration. A standard Hibernate configuration reads the mappings from a <filename>cfg.xml</filename> and/or a fileset. + A <code><configuration></code> tag is used to define a standard Hibernate configuration. A standard Hibernate configuration reads the mappings from a <filename>cfg.xml</filename> file and/or a fileset. </para> <programlisting role="XML"><![CDATA[<configuration @@ -359,13 +363,13 @@ <title>Example</title> <para> - This example shows an example where no <filename>hibernate.cfg.xml</filename> exists, and a <filename> hibernate.properties</filename> file and fileset is used instead. + This example shows an example where no <filename>hibernate.cfg.xml</filename> file exists, and a <filename>hibernate.properties</filename> file and fileset is used instead. </para> <note> <title>Note:</title> <para> - Hibernate will still read any global <filename>hibernate.properties</filename> available in the classpath, but the specified properties file here will override those values for any non-global property. + Hibernate will still read any global <filename>hibernate.properties</filename> files available in the classpath, but the specified properties file here will override those values for any non-global property. </para> </note> @@ -387,17 +391,17 @@ <section> <title>Annotation based Configuration (<annotationconfiguration>)</title> - <para>An <code><annotationconfiguration></code> is used when you want to read the metamodel from EJB3/Hibernate Annotations based POJO's.</para> + <para>An <code><annotationconfiguration></code> tag is used when you want to read the metamodel from EJB3 or Hibernate Annotations based POJO's.</para> <important> <title>Important:</title> <para> - To use it remember to put the jar files needed for using hibernate annotations in the classpath of the <code><taskdef></code>, i.e. <filename>hibernate-annotations.jar</filename> and <filename>hibernate-commons-annotations.jar</filename>. + To use it remember to put the JAR files needed for using Hibernate annotations in the classpath of the <code><taskdef></code>, i.e. <filename>hibernate-annotations.jar</filename> and <filename>hibernate-commons-annotations.jar</filename>. </para> </important> <para> - The <code><annotationconfiguration></code> supports the same attributes as a <code><configuration></code> except that the configurationfile attribute is now required as that is from where an <emphasis>AnnotationConfiguration</emphasis> gets the list of classes/packages it should load. + The <code><annotationconfiguration></code> tag supports the same attributes as the <code><configuration></code> tag except that the <code>configurationfile</code> attribute is now required as that is where an <emphasis>AnnotationConfiguration</emphasis> gets the list of classes and packages it should load. </para> <para>Thus the minimal usage is:</para> @@ -417,19 +421,19 @@ <title>JPA based configuration (<jpaconfiguration>)</title> <para> - A <code><jpaconfiguration></code> is used when you want to read the metamodel from JPA/Hibernate Annotation where you want to use the auto-scan configuration as defined in the JPA spec (part of EJB3). In other words, when you do not have a <filename>hibernate.cfg.xml</filename>, but instead have a setup where you use a <filename>persistence.xml</filename> file packaged in a JPA compliant manner. + A <code><jpaconfiguration></code> tag is used when you want to read the metamodel from JPA or Hibernate Annotation where you want to use the auto-scan configuration as defined in the JPA spec (part of EJB3). In other words, when you do not have a <filename>hibernate.cfg.xml</filename>, but instead have a setup where you use a <filename>persistence.xml</filename> file packaged in a JPA compliant manner. </para> <para> - The <code><jpaconfiguration></code> will simply try and auto-configure it self based on the available classpath, e.g. look for the <filename>META-INF/persistence.xml</filename> file. + The <code><jpaconfiguration></code> tag will try and auto-configure it self based on the available classpath, e.g. look for the <filename>META-INF/persistence.xml</filename> file. </para> <para> - The <code>persistenceunit</code> attribute can be used to select a specific persistence unit. If no <code>persistenceunit</code> is specified it will automatically search for one and if a unique one is found, use it, but having multiple persistence units will result in an error. + The <code>persistenceunit</code> attribute can be used to select a specific persistence unit. If no <code>persistenceunit</code> attribute is specified it will automatically search for one and if a unique one is found, use it. However, having multiple persistence units will result in an error. </para> <para> - To use a <code><jpaconfiguration></code> you will need to specify some additional jars from Hibernate EntityManager in the <code><taskdef></code> of the hibernatetool. The following shows a full setup: + To use a <code><jpaconfiguration></code> tag you will need to specify some additional JARs from Hibernate EntityManager in the <code><taskdef></code> section of the hibernatetool. The following demonstrates a full setup: </para> <programlisting role="XML"><![CDATA[<path id="ejb3toolslib"> @@ -462,7 +466,7 @@ <note> <title>Note:</title> <para> - ejb3configuration was the name used in previous versions. It still works but will emit a warning telling you to use <literal>jpaconfiguration</literal> instead. + ejb3configuration was the name used in previous versions. It still works but will display a warning telling you to use <literal>jpaconfiguration</literal> instead. </para> </note> @@ -471,14 +475,14 @@ <section> <title>JDBC Configuration for reverse engineering (<jdbcconfiguration>)</title> - <para>A <code><jdbcconfiguration></code> is used to perform reverse engineering of the database from a JDBC connection.</para> + <para>A <code><jdbcconfiguration></code> tag is used to perform reverse engineering of a database from a JDBC connection.</para> <para> This configuration works by reading the connection properties either from a <filename>hibernate.cfg.xml</filename> file or a <filename>hibernate.properties</filename> file with a fileset. </para> <para> - The <code><jdbcconfiguration></code> has the same attributes as a <code><configuration></code> plus the following additional attributes: + The <code><jdbcconfiguration></code> tag has the same attributes as a <code><configuration></code> tag, plus the following additional attributes: </para> <programlisting role="XML"><![CDATA[<jdbcconfiguration @@ -602,7 +606,7 @@ <title>Example</title> <para> - Here is an example of using <code><jdbcconfiguration></code> to generate Hibernate xml mappings via <code><hbm2hbmxml></code>. The connection settings here is read from a <filename> hibernate.properties </filename> file but could just as well have been read from a <filename>hibernate.cfg.xml</filename> file. + Here is an example using a <code><jdbcconfiguration></code> tag to generate Hibernate XML mappings via <code><hbm2hbmxml></code>. The connection settings used here are read from a <filename>hibernate.properties</filename> file, but they could also have been defined in a <filename>hibernate.cfg.xml</filename> file. </para> <programlisting role="XML"><![CDATA[<hibernatetool> @@ -618,7 +622,7 @@ <title>Exporters</title> <para> - Exporters do the actual job of converting the hibernate metamodel into various artifacts, mainly code. The following section describes the current supported set of exporters in the <productname>Hibernate Tool</productname> distribution. It is also possible to implement user defined exporters, which is done through the <code><hbmtemplate></code> exporter. + Exporters do the actual job of converting the Hibernate metamodel into various artifacts, mainly code. The following section describes the current supported set of exporters in the <productname>Hibernate Tool</productname> distribution. It is also possible to implement user defined exporters, which is done through the <code><hbmtemplate></code> exporter. </para> <section> @@ -683,7 +687,7 @@ <entry> <para> - Try and create an update script representing the "delta" that is, between what is in the database and what the mappings specify. Ignores create and update attributes. (<emphasis>Do *not* use against production databases, as there are no guarantees that the proper delta can be generated nor that the underlying database can actually execute the required operations</emphasis>). + Try and create an update script representing the "delta" that is, between what is in the database and what the mappings specify. Ignores create and update attributes. (<emphasis>Do *not* use against production databases, as there are no guarantees that the proper delta can be generated, nor that the underlying database can actually execute the required operations</emphasis>). </para> </entry> @@ -785,7 +789,7 @@ <title>Example</title> <para> - Basic example of using <code><hbm2ddl></code>, which does not export to the database but simply dumps the SQL to a file named <filename>sql.ddl</filename>. + Below is a basic example of using <code><hbm2ddl></code>, which does not export to the database but simply dumps the SQL to a file named <filename>sql.ddl</filename>. </para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> @@ -868,7 +872,7 @@ <section> <title>Example</title> - <para>Basic example of using <code><hbm2java></code> to generate POJO's that utilize JDK5 constructs.</para> + <para>Here is a basic example using <code><hbm2java></code> to generate POJO's that utilize JDK5 constructs.</para> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated"> <configuration configurationfile="hibernate.cfg.xml"/> @@ -881,7 +885,7 @@ <title>Hibernate Mapping files exporter (<hbm2hbmxml>)</title> <para> - <code><hbm2hbmxml></code> generates a set of <filename>.hbm</filename> files. Intended to be used together with a <code><jdbcconfiguration></code> when performing reverse engineering, but can be used with any kind of configuration. e.g. to convert from annotation based POJO's to a <filename>hbm.xml</filename> file. + <code><hbm2hbmxml></code> generates a set of <filename>.hbm</filename> files. It is intended to be used together with a <code><jdbcconfiguration></code> when performing reverse engineering, but can be used with any kind of configuration e.g. to convert from annotation based POJO's to a <filename>hbm.xml</filename> file. </para> <note> @@ -923,7 +927,7 @@ <title>Hibernate Configuration file exporter (<hbm2cfgxml>)</title> <para> - <code><hbm2cfgxml></code> generates a <filename>hibernate.cfg.xml</filename> file. Intended to be used together with a <code><jdbcconfiguration></code> when performing reverse engineering, but it can be used with any kind of configuration. The <code><hbm2cfgxml></code> will contain the properties used and adds mapping entries for each mapped class. + <code><hbm2cfgxml></code> generates a <filename>hibernate.cfg.xml</filename> file. It is intended to be used together with a <code><jdbcconfiguration></code> when performing reverse engineering, but it can be used with any kind of configuration. The <code><hbm2cfgxml></code> will contain the properties that are used and adds mapping entries for each mapped class. </para> <programlisting role="XML"><![CDATA[<hbm2cfgxml @@ -1000,7 +1004,7 @@ ]]></programlisting> <para> - Currently one session is opened and used for all queries and the query is executed via the <code>list()</code> method. In the future more options might become available, like performing <code>executeUpdate()</code>, use named queries and etc. + Currently one session is opened and used for all queries, which are executed via the <code>list()</code> method. In the future more options might become available, like executing <code>executeUpdate()</code>, use named queries and etc. </para> <para/> @@ -1009,7 +1013,7 @@ <title>Examples</title> <para> - The simplest usage of <code><query></code> will just execute the query without dumping to a file. This can be used to verify that queries can actually be performed. + The simplest usage of <code><query></code> will execute the query without dumping to a file. This can be used to verify that queries can be performed successfully. </para> <programlisting role="XML"><![CDATA[<hibernatetool> @@ -1023,7 +1027,7 @@ <note> <title>Note:</title> - <para> Currently the dump is simply a call to <code>toString()</code> on each element.</para> + <para> Currently the dump is performed by calling the <code>toString()</code> function on each element.</para> </note> <programlisting role="XML"><![CDATA[<hibernatetool> @@ -1039,7 +1043,7 @@ <section id="hbmtemplate"> <title>Generic Hibernate metamodel exporter (<hbmtemplate>)</title> - <para>Generic exporter that can be controlled by a user provides a template or class.</para> + <para>Below is an example of a generic exporter that can be controlled by a user provided template or class.</para> <programlisting role="XML"><![CDATA[<hbmtemplate filepattern="{package-name}/{class-name}.ftl" @@ -1049,7 +1053,7 @@ <note> <title>Note:</title> - <para>Previous versions of the tools used <productname>Velocity</productname>. We are now using <productname>Freemarker</productname> which provides us much better exception and error handling. + <para>Previous versions of the tools used <productname>Velocity</productname>. We are now using <productname>Freemarker</productname>, which provides much better exception and error handling. </para> </note> @@ -1057,7 +1061,7 @@ <title>Exporter via <hbmtemplate></title> <para> - The following is an example of reverse engineering via <code><jdbcconfiguration></code> and usage of a custom Exporter via the <code><hbmtemplate></code>. + The following is an example of reverse engineering via a <code><jdbcconfiguration></code> tag and the use of a custom Exporter via the <code><hbmtemplate></code> tag. </para> <programlisting role="XML"><![CDATA[ <hibernatetool destdir="${destdir}"> @@ -1081,7 +1085,7 @@ <title>Relevant Resources Links</title> <para> - Read more about <ulink url="http://velocity.apache.org/">Velocity</ulink> and <ulink url="http://freemarker.org/">Freemarker</ulink> to find out why using the last is better or refer to Max Andersen discussion on the topic in <ulink url="http://in.relation.to/2110.lace;jsessionid=3462F47B17556604C15DF1B96572E940">"A story about FreeMarker and Velocity"</ulink>. + You can read more about <ulink url="http://velocity.apache.org/">Velocity</ulink> and <ulink url="http://freemarker.org/">Freemarker</ulink> to find out why using the latter is better or refer to Max Andersens discussion on the topic in <ulink url="http://in.relation.to/2110.lace;jsessionid=3462F47B17556604C15DF1B96572E940">"A story about FreeMarker and Velocity"</ulink>. </para> </section> </section> @@ -1093,20 +1097,20 @@ <title>Using properties to configure Exporters</title> <para> - Exporters can be controlled by user properties. The user properties are specified via <code><property></code> or <code><propertyset></code> and each exporter will have access to them directly in the templates and via <code>Exporter.setProperties()</code>. + Exporters can be controlled by user properties. These user properties are specified via a <code><property></code> or <code><propertyset></code> tag, and each exporter will have access to them directly in the templates and via <code>Exporter.setProperties()</code>. </para> <section> <title><property> and <propertyset></title> <para> - The <code><property></code> allows you bind a string value to a key. The value will be available in the templates via <code>$<key></code>. The following example will assign the string value <code>"true"</code> to the variable <code>$descriptors</code>. + The <code><property></code> tag allows you bind a string value to a key. The value will be available in the templates via the <code>$<key></code> tag. The following example will assign the string value <code>"true"</code> to the variable <code>$descriptors</code>. </para> <programlisting role="XML"><![CDATA[<property key="descriptors" value="true"/>]]></programlisting> <para> - Most times using <code><property></code> is enough for specifying the properties needed for the exporters. Still the Ant tools supports the notion of a <code><propertyset></code> which is used for grouping a set of properties. More about the functionality of <code><propertyset></code> is explained in detail in the <ulink url="http://ant.apache.org/manual/">Ant manual</ulink>. + Usually using the <code><property></code> tag is enough when specifying the properties required by the exporters. Still, the Ant tools supports the notion of a <code><propertyset></code> which is used for grouping a set of properties. More about the functionality of <code><propertyset></code> is can be found in the <ulink url="http://ant.apache.org/manual/">Ant manual</ulink>. </para> </section> @@ -1118,18 +1122,18 @@ <programlisting role="XML"><![CDATA[<property key="hibernatetool.sometool.toolclass" value="x.y.z.NameOfToolClass"/>]]></programlisting> <para> - Placing the above <code><property></code> tag in <code><hibernatetool></code> or inside any exporter will automatically create an instance of <code>x.y.z.NameOfToolClass</code> and it will be available in the templates as <code>$sometool</code>. This is useful to delegate logic and code generation to Java code instead of placing such logic in the templates. + Placing the above <code><property></code> tag in the <code><hibernatetool></code> tag or inside any exporter will automatically create an instance of <code>x.y.z.NameOfToolClass</code> which will be available in the templates as <code>$sometool</code>. This is useful to delegate logic and code generation to Java code instead of placing such logic in the templates. </para> <section> <title>Example</title> <para> - Here is an example that uses <code><hbmtemplate></code> together with <code><property></code>, which will be available to the templates/exporter. + Here is an example that uses the <code><hbmtemplate></code> tag together with the <code><property></code> tag, which will be available to the templates and exporter. </para> <note> <title>Note:</title> - <para> This example actually simulates what <code><hbm2java></code> does.</para> + <para> This example actually simulates what the <code><hbm2java></code> tag does.</para> </note> <programlisting role="XML"><![CDATA[<hibernatetool destdir="${build.dir}/generated">

13 years, 5 months

1
0
0 / 0

JBoss Tools SVN: r28536 - trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command.

by jbosstools-commits＠lists.jboss.org

Author: Grid.Qian Date: 2011-01-24 00:28:50 -0500 (Mon, 24 Jan 2011) New Revision: 28536 Modified: trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/AbstractJBossWSGenerationTest.java trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/JBossWSJavaFirstCommandTest.java trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/JBossWSTopDownCommandTest.java Log: JBIDE-8046: try to fix the test failed issue Modified: trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/AbstractJBossWSGenerationTest.java =================================================================== --- trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/AbstractJBossWSGenerationTest.java 2011-01-24 04:41:06 UTC (rev 28535) +++ trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/AbstractJBossWSGenerationTest.java 2011-01-24 05:28:50 UTC (rev 28536) @@ -92,17 +92,11 @@ return model; } - public void publishWebProject() throws CoreException { - IModule[] modules = ServerUtil.getModules(currentServer.getServerType() - .getRuntimeType().getModuleTypes()); - IServerWorkingCopy serverWC = currentServer.createWorkingCopy(); - serverWC.modifyModules(modules, null, null); - serverWC.save(true, null).publish(0, null); - IStatus status = currentServer.publish(IServer.PUBLISH_FULL, null); - int i = 0; - while(!status.isOK() && i++ <30){ - JobUtils.delay(500); - } + public IStatus publishWebProject(IProject project) throws CoreException { + IModule mod = ServerUtil.getModule(project); + currentServer = ServerRuntimeUtils.addModule(currentServer, mod); + IStatus status = ServerRuntimeUtils.publish(currentServer); + return status; } private boolean isServerSupplied() { Modified: trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/JBossWSJavaFirstCommandTest.java =================================================================== --- trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/JBossWSJavaFirstCommandTest.java 2011-01-24 04:41:06 UTC (rev 28535) +++ trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/JBossWSJavaFirstCommandTest.java 2011-01-24 05:28:50 UTC (rev 28536) @@ -73,13 +73,12 @@ doValidateWSImplCommand(); doJava2WSCommand(); - IProject project = fproject.getProject(); - project.refreshLocal(IResource.DEPTH_INFINITE, null); - project.build(IncrementalProjectBuilder.FULL_BUILD, null); + fproject.getProject().refreshLocal(IResource.DEPTH_INFINITE, null); + fproject.getProject().build(IncrementalProjectBuilder.FULL_BUILD, null); startup(currentServer); - publishWebProject(); - JobUtils.delay(18000); + publishWebProject(fproject.getProject()); + JobUtils.delay(30000); String webServiceUrl = "http://localhost:8080/JavaFirstTestProject/HelloWorld?wsdl"; URL url = new URL(webServiceUrl); URLConnection conn = url.openConnection(); Modified: trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/JBossWSTopDownCommandTest.java =================================================================== --- trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/JBossWSTopDownCommandTest.java 2011-01-24 04:41:06 UTC (rev 28535) +++ trunk/ws/tests/org.jboss.tools.ws.creation.core.test/src/org/jboss/tools/ws/creation/core/test/command/JBossWSTopDownCommandTest.java 2011-01-24 05:28:50 UTC (rev 28536) @@ -64,8 +64,8 @@ fproject.getProject().refreshLocal(IResource.DEPTH_INFINITE, null); fproject.getProject().build(IncrementalProjectBuilder.FULL_BUILD, null); startup(currentServer); - publishWebProject(); - JobUtils.delay(12000); + publishWebProject(fproject.getProject()); + JobUtils.delay(15000); assertTrue(currentServer.getModules().length > 0); String webServiceUrl = "http://127.0.0.1:8080/JBossWSTestProject/Greeter?wsdl"; URL url = new URL(webServiceUrl);

13 years, 5 months

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-23 23:41:06 -0500 (Sun, 23 Jan 2011) New Revision: 28535 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-24 04:34:06 UTC (rev 28534) +++ trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-24 04:41:06 UTC (rev 28535) @@ -337,7 +337,7 @@ </table> <itemizedlist> <listitem> - <para>Classpath</guilabel> for classpath</para> + <para><guilabel>Classpath</guilabel> for classpath</para> </listitem> </itemizedlist> <figure> @@ -2199,7 +2199,7 @@ <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 the <guilabel>JPA Perspective</guilabel>), the first wizard page is shwn in the image below. + When starting a new JPA project by selecting <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>Other</guimenuitem><guimenuitem>JPA</guimenuitem><guimenuitem>JPA Project</guimenuitem></menuchoice> (or simply <menuchoice><guimenuitem>New</guimenuitem><guimenuitem>JPA Project</guimenuitem></menuchoice> in the <guilabel>JPA Perspective</guilabel>), the first wizard page is shown in the image below. </para> <figure> <title>Starting JPA Project</title> @@ -2225,7 +2225,7 @@ <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 <guilabel>Hibernate Tools</guilabel> features without additional setup. + If you choose Hibernate as a platform while creating a JPA/Dali project, a Hibernate Console Configuration for the project is created automatically when the wizard is finished. It allows all the <guilabel>Hibernate Tools</guilabel> features to be used without any additional setup. </para> </note> </section> @@ -2244,7 +2244,7 @@ </figure> <note> <title>Note:</title> - <para>Please, remember to put the proper database driver to the classpath of your project.</para> + <para>Remember to put the proper database driver to the classpath of your project.</para> </note> <para>The <guilabel>Generate Entities wizard</guilabel> will first ask you to choose the directory where all output will be written.</para> <figure> @@ -2258,9 +2258,9 @@ <para>To generate entities you can use:</para> <itemizedlist> <listitem> - <para>a Hibernate Console Configuration (proposed by default)</para> + <para>A Hibernate Console Configuration (proposed by default)</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. + To select this option make sure that the <guilabel>Use Console Configuration</guilabel> checkbox is selected and select a configuration from the <guilabel>Console configurations</guilabel> list box. </para> <figure> <title>Generate Entities Wizard</title> @@ -2274,8 +2274,8 @@ </itemizedlist> <itemizedlist> <listitem> - <para>or a DTP connection directly</para> - <para>Just uncheck the <guilabel>Use Console Configuration</guilabel> option and adjust the database settings.</para> + <para>Or a DTP connection directly</para> + <para>To select this option uncheck the <guilabel>Use Console Configuration</guilabel> option and adjust the database settings.</para> </listitem> </itemizedlist> <para> @@ -2289,12 +2289,12 @@ </imageobject> </mediaobject> </figure> - <para>Thus, you can now have the Hibernate runtime support in Eclipse JPA projects.</para> + <para>In this way you can enable Hibernate runtime support in Eclipse JPA projects.</para> </section> <section id="hibernate_annotations_support"> <title>Hibernate Annotations Support</title> <para> - Hibernate Annotations are also supported in <guilabel>Dali Java Persistence Tools</guilabel>. The next annotations are integrated with <guilabel>JPA Details</guilabel> view: + Hibernate Annotations are also supported in <guilabel>Dali Java Persistence Tools</guilabel>. The following annotations are integrated with the <guilabel>JPA Details</guilabel> view: </para> <itemizedlist> <listitem> @@ -2318,7 +2318,7 @@ </figure> </listitem> <listitem> - <para>Property annotations- <code>@DiscriminatorFormula</code>, <code>@Generated Annotation</code>, <code>@Index annotation</code> + <para>Property annotations - <code>@DiscriminatorFormula</code>, <code>@Generated</code>, <code>@Index</code> </para> <figure> <title>@Index support in Dali</title> @@ -2364,13 +2364,13 @@ </listitem> </itemizedlist> <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>. + More information about Hibernate Annotations can be found in the <ulink url="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html/">Hibernate Annotations Reference Guide</ulink>. </para> </section> <section> <title>Relevant Resources Links</title> <para> - More information about native Dali plugin features on <ulink url="http://help.eclipse.org/galileo/index.jsp?nav=/8">Eclipse Documentation page</ulink>. + Find more information about native Dali plugin features on the <ulink url="http://help.eclipse.org/galileo/index.jsp?nav=/8">Eclipse Documentation page</ulink>. </para> </section> </section>

13 years, 5 months

1
0
0 / 0

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

by jbosstools-commits＠lists.jboss.org

Author: mcaspers Date: 2011-01-23 23:34:06 -0500 (Sun, 23 Jan 2011) New Revision: 28534 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-24 04:04:16 UTC (rev 28533) +++ trunk/hibernatetools/docs/reference/en-US/plugins.xml 2011-01-24 04:34:06 UTC (rev 28534) @@ -1411,7 +1411,7 @@ <section id="map_diagram"> <title>Mapping Diagram</title> <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>. + In order to visualize how entities are related, as well as view their structures, a <guilabel>Mapping Diagram</guilabel> is provided. It is available by right clicking on the entity you want view a mapping diagram for and then selecting <guilabel>Mapping Diagram</guilabel>. </para> <figure> <title>Mapping Diagram</title> @@ -1425,7 +1425,7 @@ </mediaobject> </figure> <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. + To make <guilabel>Mapping Diagram</guilabel> usage easier you can use the <guilabel>Rules</guilabel>, <guilabel>Grid</guilabel>, <guilabel>Snap to Geometry</guilabel> checkboxes in the <guimenu>View</guimenu> menu. </para> <figure> <title>View menu</title> @@ -1436,7 +1436,7 @@ </mediaobject> </figure> <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. + If you select the <guilabel>Rules</guilabel> checkbox, the view print page scale will be added to the page. The numbers on the scale displays its size in inches. If you click on the scale a <guilabel>Ruler Guide</guilabel> will appear on the diagram. You can connect any diagram item to it. To connect the items you should move their tops to the Ruler Guide. And while moving the ruler guide, the items will be moved together with it as a whole. </para> <figure> <title>Moving the Ruler guide</title> @@ -1446,7 +1446,7 @@ </imageobject> </mediaobject> </figure> - <para>If you select the <guilabel>Grid</guilabel> checkbox, the grid will appear on the diagram.</para> + <para>If you select the <guilabel>Grid</guilabel> checkbox, a grid will appear on the diagram.</para> <figure> <title>Grid on Mapping diagram</title> <mediaobject> @@ -1455,7 +1455,7 @@ </imageobject> </mediaobject> </figure> - <para>The checkbox <guilabel>Snap to Geometry</guilabel> helps to put the items of the diagram into alignment with the grid.</para> + <para>The <guilabel>Snap to Geometry</guilabel> checkbox 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> @@ -1566,14 +1566,15 @@ <para>Export as Image</para> </entry> <entry> - <para>Allows the diagram to be exported as a <filename>.png</filename>,<filename>.jpeg</filename> or <filename>.bmp </filename> + <para> + Allows the diagram to be exported as a <filename>.png</filename>,<filename>.jpeg</filename> or <filename>.bmp </filename> file </para> </entry> </row> </tbody> </tgroup> </table> - <para>When you open the context menu while clicking an item on the diagram, it quite differs from the one described before.</para> + <para>When you open the context menu for an item in the diagram, it differs quite significantly from the one described before.</para> <figure> <title>Context Menu in Mapping Item</title> <mediaobject> @@ -1682,7 +1683,7 @@ <title>Tip:</title> <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 following table lists the actions that can be performed using the keyboard keys (or keys combinations).</para> <table> <title>Hibernate Mapping Diagram Shortcut Keys</title> <tgroup cols="2"> @@ -1757,7 +1758,7 @@ </tgroup> </table> <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. + It is possible to save the diagram in the Eclipse workspace. Select <menuchoice><guimenuitem>File</guimenuitem><guimenuitem>Save As</guimenuitem></menuchoice>, and the wizard will ask you to set the location within you project where you wish to save the file and give the name for the diagram. The default name is the item's names concatenated with the ampersand symbols. The file is saved with the <filename>.hibernate</filename> extension. </para> <figure> <title>The Diagram saved in the Workspace</title> @@ -1770,7 +1771,7 @@ <note> <title>Note:</title> <para> - If you restart Eclipse with the mapping diagram opened, the mapping diagram will be restored with the message like on the figure below. To view the diagram content, you should perform the refreshing. + If you restart Eclipse with the mapping diagram opened, the mapping diagram will be restored with the message like on the figure below. To view the diagram content, you should refresh the view. </para> </note> <figure> @@ -1851,7 +1852,7 @@ </entry> <entry> <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>. + Used to define scale of the diagram. It is also used for printing <guilabel>Mapping Diagrams</guilabel>. If you want to print the whole <guilabel>diagram</guilabel> to one print page, you need select the <guilabel>Page</guilabel> option in the <guilabel>Zoom Box</guilabel> drop down list. </para> </entry> </row> @@ -1887,7 +1888,7 @@ </entry> <entry> <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>). + Used to show or hide a connection on the diagram. You can also choose what type of connections must be present on the diagram (<guilabel>Property Mappings</guilabel>, <guilabel>Class Mappings</guilabel>, <guilabel>Associations</guilabel> or <guilabel>Foreign key constraints</guilabel>). </para> </entry> </row> @@ -1905,7 +1906,7 @@ <para>Expand|Collapse</para> </entry> <entry> - <para>Used for expanding/collapsing fields of the item.</para> + <para>Used for expanding or collapsing fields of the item.</para> </entry> </row> <row> @@ -1933,7 +1934,7 @@ <section> <title>Prototyping Queries</title> <para> - Queries can be prototyped by entering them into the <guilabel>HQL</guilabel> or <guilabel>Criteria Editor</guilabel>. To execute a query you should click the green run button in the editor toolbar or press <keycombo><keycap>Ctrl</keycap><keycap>Enter</keycap></keycombo>. + Queries can be prototyped by entering them into the <guilabel>HQL</guilabel> or <guilabel>Criteria Editor</guilabel>. To execute a query click the green run button in the editor toolbar or press <keycombo><keycap>Ctrl</keycap><keycap>Enter</keycap></keycombo>. </para> <section id="hql_and_criteria_editors"> <title>HQL Editor and Hibernate Criteria Editor</title> @@ -1951,15 +1952,15 @@ <note> <title>Tip:</title> <para> - If the context menu items are disabled then you need at first to create a <guilabel>Session Factory</guilabel>. That is done by simply expanding the <guilabel>Session Factory</guilabel> node. + If the context menu items are disabled then you need at first to create a <guilabel>Session Factory</guilabel>. That is done by expanding the <guilabel>Session Factory</guilabel> node. </para> </note> - <para>When open the editors they should automatically detect the chosen <guilabel>Console Configuration</guilabel>.</para> + <para>When they are opened, 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. + Choosing <guimenuitem>HQL Editor</guimenuitem> in the context menu for any entity (or any entity child node) will also open the HQL Editor with the associated query. If you select <guimenuitem>Hibernate Criteria Editor</guimenuitem> in the context menu, it will open <guilabel>Hibernate Criteria Editor</guilabel> with the associated criteria. </para> <figure> <title>Generating Simple Queries</title> @@ -1984,7 +1985,7 @@ </mediaobject> </figure> <para> - You can also update the original java code with changes made in the HQL or Criteria editor. For that you should save your HQL/Criteria query and submit the replacing in appeared confirmation dialog. + You can also update the original Java code with changes made in the HQL or Criteria editor. For that you should save your HQL/Criteria query and submit the replacement code when prompted by the confirmation dialog. </para> <figure> <title>Updating Java Code</title> @@ -1995,10 +1996,10 @@ </mediaobject> </figure> <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). + 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 the <guibutton>Stick result to one tab</guibutton> button (<inlinemediaobject><imageobject><imagedata fileref="images/plugins/sticky_but.png"/></imageobject></inlinemediaobject>). In this state query executions results will be shown in one tab (no more will be opened). </para> <para> - 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>. + You are able to rename the <guilabel>Hibernate Query Result</guilabel> tab. Click the tab, and type a new name in the <menuchoice><guimenuitem>Property View</guimenuitem><guimenuitem>Tab name</guimenuitem></menuchoice> field. </para> <figure> <title>Tab Renaming</title> @@ -2012,7 +2013,7 @@ <section> <title>Error Handling</title> <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. + Errors raised during the creation of the <guilabel>Session Factory</guilabel> or when executing the queries (e.g. if your configuration or query is incorrect) will be shown in a message dialog or inclined in the view that detected the error. You may get more information about the error in the <guilabel>Error Log 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>. @@ -2020,14 +2021,14 @@ <note> <title>Note:</title> <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. + HQL queries are executed by default using the <code>list()</code> function, and without any row limit could return a large result set. You may run out of memory. To avoid this you can enter a value in the <guilabel>Max</guilabel> results field to reduce the number of elements that are returned. </para> </note> </section> <section> <title>Dynamic Query Translator</title> <para> - If the <guilabel>Hibernate Dynamic Query Translator View</guilabel> is visible while writing in the <guilabel>HQL Editor</guilabel> it will show the generated SQL for a HQL query. + If the <guilabel>Hibernate Dynamic Query Translator View</guilabel> is visible, it will show the generated SQL for a HQL query while you write in the <guilabel>HQL Editor</guilabel> . </para> <figure> <title>Hibernate Dynamic Query Translator View</title> @@ -2041,14 +2042,14 @@ </mediaobject> </figure> <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. + The translation is performed each time you stop typing in the editor. If there are errors in the HQL code the parse exception will be shown embedded in the view. </para> </section> </section> <section> <title>Properties View</title> <para> - As you can see in the figure below, when clicking on class/entity the <guilabel>Properties view</guilabel> shows the number of query results as well as the execution time. + As you can see in the figure below, when clicking on class or entity the <guilabel>Properties view</guilabel> shows the number of query results as well as the execution time. </para> <figure> <title>Properties View</title> @@ -2082,7 +2083,7 @@ </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: <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>Using this wizard you can add the following Hibernate annotations to a class: <code>@Column</code>, <code>@Entity</code>, <code>@ManyToOne</code>, <code>@OneToMany</code>, <code>@OneToOne</code>, <code>@ManyToMany</code>, <code>@MappedSuperclass</code>, <code>@Id</code>, <code>@GeneratedValue</code>, <code>@Version </code> </para> <itemizedlist> <listitem> @@ -2090,11 +2091,11 @@ </listitem> <listitem> <para> - <code>@Entity</code> is always declared before any class where it doesn't present.</para> + <code>@Entity</code> is always declared before any class where it has not yet been defined.</para> </listitem> <listitem> <para> - <code>@ManyToOne</code>, <code>@OneToMany</code>, <code>@OneToOne</code>, <code>@ManyToMany</code> - this annotations are declared according to the classes hierarchy. + <code>@ManyToOne</code>, <code>@OneToMany</code>, <code>@OneToOne</code>, <code>@ManyToMany</code> - these annotations are declared according to the classes hierarchy. </para> </listitem> <listitem> @@ -2103,22 +2104,22 @@ </listitem> <listitem> <para> - <code>@Id</code>, <code>@GeneratedValue</code> are added automatically only to the properties under the name "Id",where they don't present. + <code>@Id</code>, <code>@GeneratedValue</code> are only added automatically to the properties under the name "Id", where they have not yet been defined. </para> </listitem> <listitem> <para> - <code>@Version</code> is declared in case you select <xref linkend="optim_lock"/>.</para> + <code>@Version</code> is declared in case you select optimistic locking (see <xref linkend="optim_lock"/>).</para> </listitem> </itemizedlist> <note> <title>Note:</title> <para> - This section doesn't cover the 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>. + This section doesn't cover the definitions of the <property>Hibernate annotations</property>. For more information read the <ulink url="http://docs.jboss.org/hibernate/stable/annotations/reference/en/html/">Hibernate Annotations Documentation</ulink>. </para> </note> <para> - To open this wizard you should right click the class you want to 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 add the annotations to and select <menuchoice><guimenuitem>Source</guimenuitem><guimenuitem>Generate Hibernate/JPA annotations</guimenuitem></menuchoice>. You will see the <guilabel>Hibernate: add JPA annotations</guilabel> dialog. </para> <figure> <title>Starting Hibernate:add JPA annotations dialog</title> @@ -2129,7 +2130,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 <guilabel>Add classes and packages</guilabel> page. + In the top of this dialog you can see a list of all the classes that will be passed through refactoring. Besides the class you have selected, this list also shows its superclasses and the classes that objects present in the current class as properties. If you want to add new classes or packages to the list, you should click the <guibutton>Back</guibutton> button. In result you will see <guilabel>Add classes and packages</guilabel> page. </para> <figure> <title>Add classes and packages page </title> @@ -2140,17 +2141,17 @@ </mediaobject> </figure> <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> + Here you can add more classes or whole packages, and you can limit the dependencies depth by selecting the <guilabel>depth control</guilabel> option (you can find more information on this option in <xref linkend="depth_control"/>). When finished click the <guibutton>Next</guibutton> button and you will be returned to <guilabel>The following classes will be changed</guilabel> page.</para> <para> - By default the tags are added to the fields of selected classes. 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. + By default the tags are added to the fields of selected classes. But you can change this option to <guilabel>Getters</guilabel> in the <guilabel> Preferred location of Annotations</guilabel> drop down list, which results in the annotations being added to the getter methods. If you choose <guilabel>Auto select from class preference</guilabel> then the annotations are added according to the position of the majority of the existing annotations. </para> <para> - If it is necessary to map your 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. + If it is necessary to map your <code>String</code> properties to the columns that length differ from the default value (255), change the <guilabel>Default string length</guilabel> field and the <code>@Column(length = your length)</code> annotation will be created for every <code>String</code> property. </para> <para id="optim_lock"> - You can add optimistic locking 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. + You can add optimistic locking capability to an entity bean by selecting the <guilabel>Enable optimistic locking</guilabel> checkbox. This operation will add the version property to all the selected classes. The property will be also annotated with <code>@Version</code>, and a getter and setter will be created. If the property is already exists, it won't be created, but the getters and setters will be generated. If there is already <code>@MappedSuperclass</code> annotation with 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> + <para>After defining all the required settings click the <guibutton>Next</guibutton> button and follow the next wizard steps. </para> <figure> <title>Hibernate:add JPA annotations view</title> <mediaobject> @@ -2175,25 +2176,25 @@ <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 <guilabel>Error Log View</guilabel> in Eclipse. + It is possible to configure the Eclipse plugin to route all logging performed by the plugins and Hibernate code it self to the <guilabel>Error Log View</guilabel> in Eclipse. </para> <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>. + The <guilabel>Error Log View</guilabel> is very useful tool when solving any problems which appear in the Hibernate Tools plugins. You can use it if there are troubles setting up a <guilabel>Hibernate Console Configuration</guilabel>. </para> <para> - This is done by editing the <filename>hibernate-log4j.properties</filename> file in the <filename>org.hibernate.eclipse/</filename> directory/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. + This is done by editing the <filename>hibernate-log4j.properties</filename> file in the <filename>org.hibernate.eclipse/</filename> directory or JAR. This file includes a default configuration that only logs WARN and above to a set of custom appenders (PluginFileAppender and PluginLogAppender). You can change these settings to be as verbose or silent as you please. See <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>. + More information on how to to configure logging via a Log4j property file can be found in the <ulink url="http://supportweb.cs.bham.ac.uk/docs/tutorials/docsystem/build/tutorials/...">Log4j documentation</ulink>. </para> </section> </section> <section id="dali_integration"> <title>Hibernate support for Dali plugins in Eclipse WTP</title> <para> - Starting from 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. + Starting from version 3.0.0 Alpha1, <productname>JBoss Tools</productname> Hibernate plugins support Eclipse Dali integration, which makes it possible to use a Hibernate as a complete JPA development platform. </para> <section id="jpa_project_with_hibernate"> <title>Creating JPA project with Hibernate support</title>

13 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

jbosstools-commits January 2011