From jbosstools-commits at lists.jboss.org Thu Mar  3 22:19:55 2011
Content-Type: multipart/mixed; boundary="===============5750730622196604574=="
MIME-Version: 1.0
From: jbosstools-commits at lists.jboss.org
To: jbosstools-commits at lists.jboss.org
Subject: [jbosstools-commits] JBoss Tools SVN: r29500 -
 trunk/hibernatetools/docs/reference/en-US.
Date: Thu, 03 Mar 2011 22:19:55 -0500
Message-ID: <201103040319.p243JtMU018356@svn01.web.mwc.hst.phx2.redhat.com>

--===============5750730622196604574==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

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
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/hibernatetools/docs/reference/en-US/ant.xml	2011-03-04 02:57:00 U=
TC (rev 29499)
+++ trunk/hibernatetools/docs/reference/en-US/ant.xml	2011-03-04 03:19:54 U=
TC (rev 29500)
@@ -180,7 +180,7 @@
       <title>Basic examples</title>
 =

       <para>
-      	The following example shows the most basic setup for generating POJ=
Os via <code>&lt;hbm2java&gt;</code> from a normal <filename>hibernate.cfg.=
xml</filename>. The output will be placed in the <filename>${build.dir}/gen=
erated</filename> directory.
+      	The following example shows the most basic setup for generating POJ=
Os via <code>&lt;hbm2java&gt;</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=3D"XML"><![CDATA[<hibernatetool destdir=3D"${bu=
ild.dir}/generated">
@@ -194,11 +194,11 @@
 =

 =

       <para>
-      	The following example is similar, but now we are performing multipl=
e exports from the same configuration. We are exporting the schema via <cod=
e>&lt;hbm2dll&gt;</code>, generating some DAO code via <code>&lt;hbm2dao&gt=
;</code> and finally running some custom code generation via <code>&lt;hbmt=
emplate&gt;</code>. This is again from a normal <filename>hibernate.cfg.xml=
</filename> file, and the output is still placed in the <filename>${build.d=
ir}/generated</filename> directory.
+      	The following example is similar, but now we are performing multipl=
e exports from the same configuration. We are exporting the schema via <cod=
e>&lt;hbm2dll&gt;</code>, generating some DAO code via <code>&lt;hbm2dao&gt=
;</code>, and finally running some custom code generation via <code>&lt;hbm=
template&gt;</code>. This is again from a normal <filename>hibernate.cfg.xm=
l</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 usef=
ul when you have custom user types or some mappings that is needed to be lo=
oked up as a classpath resource.
+      		The example also shows how a classpath is specified, which is usef=
ul when you have custom user types or some mappings that are required to be=
 looked up as a classpath resource.
       </para>
 =

       <programlisting role=3D"XML"><![CDATA[<hibernatetool destdir=3D"${bu=
ild.dir}/generated">
@@ -223,7 +223,7 @@
     <title>Hibernate Configurations</title>
 =

     <para>
-    	<emphasis>Hibernatetool</emphasis> supports four different Hibernate =
configurations: A standard Hibernate configuration (<code>&lt;configuration=
&gt;</code>),  Annotation based configuration  (<code>&lt;annotationconfigu=
ration&gt;</code>), JPA persistence based configuration (<code>&lt;jpaconfi=
guration&gt;</code>)  and a JDBC based configuration  (<code>&lt;jdbcconfig=
uration&gt;</code>) used when reverse engineering.
+    	<productname>Hibernatetool</productname> supports four different Hibe=
rnate configurations: A standard Hibernate configuration (<code>&lt;configu=
ration&gt;</code>),  Annotation based configuration  (<code>&lt;annotationc=
onfiguration&gt;</code>), JPA persistence based configuration (<code>&lt;jp=
aconfiguration&gt;</code>)  and a JDBC based configuration  (<code>&lt;jdbc=
configuration&gt;</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 Hibernat=
e annotations in the classpath of the <code>&lt;taskdef&gt;</code>,  i.e. <=
filename>hibernate-annotations.jar</filename> and <filename>hibernate-commo=
ns-annotations.jar</filename>.
+        	To use an <code>&lt;annotationconfiguration&gt;</code> tag rememb=
er to place the JAR files required to use Hibernate annotations in the clas=
spath of the <code>&lt;taskdef&gt;</code>,  i.e. <filename>hibernate-annota=
tions.jar</filename> and <filename>hibernate-commons-annotations.jar</filen=
ame>.
         </para>
       </important>
 =

       <para>
-      	The <code>&lt;annotationconfiguration&gt;</code> tag supports the s=
ame attributes as the <code>&lt;configuration&gt;</code> tag except that th=
e <code>configurationfile</code> attribute is now required as that is where=
 an <emphasis>AnnotationConfiguration</emphasis> gets the list of classes a=
nd packages it should load.
+      	The <code>&lt;annotationconfiguration&gt;</code> tag supports the s=
ame attributes as the <code>&lt;configuration&gt;</code> tag, with the exce=
ption being that the <code>configurationfile</code> attribute is now requir=
ed as that is where an <emphasis>AnnotationConfiguration</emphasis> gets th=
e list of classes and packages it should load.
       </para>
 =

       <para>Thus the minimal usage is:</para>


--===============5750730622196604574==--