Author: mcaspers Date: 2011-01-23 21:48:09 -0500 (Sun, 23 Jan 2011) New Revision: 28531 Modified: trunk/hibernatetools/docs/reference/en-US/codegenarchitecture.xml Log: General Updates Modified: trunk/hibernatetools/docs/reference/en-US/codegenarchitecture.xml =================================================================== --- trunk/hibernatetools/docs/reference/en-US/codegenarchitecture.xml 2011-01-24 02:39:42 UTC (rev 28530) +++ trunk/hibernatetools/docs/reference/en-US/codegenarchitecture.xml 2011-01-24 02:48:09 UTC (rev 28531) @@ -3,25 +3,25 @@ <title>Code generation architecture</title> <para> - The code generation mechanism in <productname>Hibernate Tools</productname> consists of a few core concepts. This section explains their overall structure, which are the same for the Ant and Eclipse tools. + The code generation mechanism in <productname>Hibernate Tools</productname> consists of a few core concepts. This section explains their overall structure, which are the same for the <productname>Ant</productname> and <productname>Eclipse</productname> tools. </para> <section> <title>Hibernate Meta Model</title> <para> - The meta model is the model used by <productname>Hibernate Core</productname> to perform its object relational mapping. The model includes information about tables, columns, classes, properties, components, values, collections etc. The API is in <code>org.hibernate.mapping</code> and its main entry point is the <code>Configuration</code> class, the same class that is used to build a session factory. + The meta model is the model used by <productname>Hibernate Core</productname> to perform its object relational mapping. The model includes information about tables, columns, classes, properties, components, values, collections etc. The API is in the <code>org.hibernate.mapping</code> package and its main entry point is the <code>Configuration</code> class, the same class that is used to build a session factory. </para> <para> - The model represented by the <code>Configuration</code> class can be built in many ways. The following list the currently supported ones in <productname>Hibernate Tools</productname>. + The model represented by the <code>Configuration</code> class can be built in many ways, which are listed below. </para> <para> <itemizedlist> <listitem> <para> - A Core configuration uses <productname>Hibernate Core</productname> and supports reading <filename>hbm.xml</filename> files, requires a <filename>hibernate.cfg.xml</filename> file. This is referred to as <productname>core</productname> in Eclipse and <code>&lt;configuration&gt;</code> in Ant. + A Core configuration uses <productname>Hibernate Core</productname> and supports reading <filename>hbm.xml</filename> files, and requires a <filename>hibernate.cfg.xml</filename> file. This is referred to as <productname>core</productname> in Eclipse and <code>&lt;configuration&gt;</code> in Ant. </para> </listitem> @@ -70,7 +70,7 @@ </para> <para> - The code generation is done based on the Configuration model no matter which type of configuration have been used to create the meta model, and thus the code generation is independent on the source of the meta model and represented via Exporters. + The code generation is performed based on the Configuration model no matter which type of configuration has been used to create the meta model, and thus the code generation is independent on the source of the meta model and represented via Exporters. </para> </section> @@ -82,11 +82,11 @@ </para> <para> - The tools provides a default set of Exporter's which can be used in both Ant and the Eclipse UI. Documentation for these Exporters is in the <xref linkend="ant"/> and <xref linkend="plugins"/> sections. + The tools provides a default set of Exporter's which can be used in both Ant and the Eclipse UI. Documentation for these Exporters is in <xref linkend="ant"/> and <xref linkend="plugins"/>. </para> <para> - Users can provide their own customer Exporter's, either by custom classes implementing the Exporter interface or simply be providing custom templates. This is documented at in the <xref linkend="hbmtemplate"/> section. + Users can provide their own custom Exporter's, either through custom classes implementing the Exporter interface or simply be providing custom templates. This is documented at in <xref linkend="hbmtemplate"/>. </para> </section> </chapter>