Author: mcaspers
Date: 2011-03-03 22:19:54 -0500 (Thu, 03 Mar 2011)
New Revision: 29500
Modified:
trunk/hibernatetools/docs/reference/en-US/ant.xml
Log:
"General editing and screenshot updates"
Modified: trunk/hibernatetools/docs/reference/en-US/ant.xml
===================================================================
--- trunk/hibernatetools/docs/reference/en-US/ant.xml 2011-03-04 02:57:00 UTC (rev 29499)
+++ trunk/hibernatetools/docs/reference/en-US/ant.xml 2011-03-04 03:19:54 UTC (rev 29500)
@@ -180,7 +180,7 @@
<title>Basic examples</title>
<para>
- 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.
+ The following example shows the most basic setup for generating POJOs via
<code><hbm2java></code> from a normal
<filename>hibernate.cfg.xml</filename> file. The output will be placed in the
<filename>${build.dir}/generated</filename> directory.
</para>
<programlisting role="XML"><![CDATA[<hibernatetool
destdir="${build.dir}/generated">
@@ -194,11 +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 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.
+ 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.
+ The example also shows how a classpath is specified, which is useful when you
have custom user types or some mappings that are required to be looked up as a classpath
resource.
</para>
<programlisting role="XML"><![CDATA[<hibernatetool
destdir="${build.dir}/generated">
@@ -223,7 +223,7 @@
<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>) used
when reverse engineering.
+ <productname>Hibernatetool</productname> supports four different
Hibernate configurations: A standard Hibernate configuration
(<code><configuration></code>), Annotation based configuration
(<code><annotationconfiguration></code>), JPA persistence based
configuration (<code><jpaconfiguration></code>) and a JDBC
based configuration (<code><jdbcconfiguration></code>) used
when reverse engineering.
</para>
<para>
@@ -396,12 +396,12 @@
<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 an <code><annotationconfiguration></code> tag
remember to place the JAR files required to use Hibernate annotations in the classpath of
the <code><taskdef></code>, i.e.
<filename>hibernate-annotations.jar</filename> and
<filename>hibernate-commons-annotations.jar</filename>.
</para>
</important>
<para>
- The <code><annotationconfiguration></code> 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.
+ The <code><annotationconfiguration></code> tag supports
the same attributes as the <code><configuration></code> tag,
with the exception being that the <code>configurationfile</code> attribute is
now required as that is where an <emphasis>AnnotationConfiguration</emphasis>
gets the list of classes and packages it should load.
</para>
<para>Thus the minimal usage is:</para>
Show replies by date