11:36 p.m.
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....;.
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">