db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From henn...@apache.org
Subject svn commit: r239636 [3/4] - in /db/torque/runtime/trunk: ./ conf/ src/conf/ src/java/org/apache/torque/ src/java/org/apache/torque/adapter/ src/java/org/apache/torque/avalon/ src/java/org/apache/torque/dsfactory/ src/java/org/apache/torque/manager/ src...
Date Wed, 24 Aug 2005 12:38:54 GMT
Modified: db/torque/runtime/trunk/xdocs/changes.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/changes.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/changes.xml (original)
+++ db/torque/runtime/trunk/xdocs/changes.xml Wed Aug 24 05:38:09 2005
@@ -28,13 +28,13 @@
   <release version="3.2-rc2-dev" date="in SVN">
     <action type="add" dev="tfischer">
       Added a method getXXX(connection) to retrieve associated objects
-      in the n->1 direction, which uses the provided connection 
-      if a db hit is necessary 
+      in the n->1 direction, which uses the provided connection
+      if a db hit is necessary
     </action>
     <action type="add" dev="tfischer">
       Added a generator property torque.silentDbFetch, which is true by default.
-      If set to false, the getXXX() methods without arguments will not access 
-      the db silently, but return null if the associated objects has not been 
+      If set to false, the getXXX() methods without arguments will not access
+      the db silently, but return null if the associated objects has not been
       read yet. Also, the method does not throw a Torque exception any more.
     </action>
     <action type="add" dev="henning">
@@ -50,8 +50,8 @@
       Updated all SCM references to point to Subversion.
     </action>
     <action type="add" dev="tfischer" issue="TRQS306">
-      Added the following generator properties to allow detailed control 
-      where the target classes are generated. 
+      Added the following generator properties to allow detailed control
+      where the target classes are generated.
       <ul>
         <li>torque.subpackage.peer</li>
         <li>torque.subpackage.object</li>
@@ -67,8 +67,8 @@
 
   <release version="3.2-rc1" date="2005-07-19">
     <action type="add" dev="tfischer">
-      Added the build-torque.xml again to the generator release. 
-      In order to use the same default directory structure 
+      Added the build-torque.xml again to the generator release.
+      In order to use the same default directory structure
       for maven and ant, the default directory for the schema files
       was changed from ${torque.home}/schema to ${torque.home}/src/schema
     </action>
@@ -79,7 +79,7 @@
       change into src/generator/src/templates and run maven jar:install.
     </action>
     <action type="update" dev="tfischer" issue="TRQS308">
-      Changed runtime configuration checking. It is now required having set 
+      Changed runtime configuration checking. It is now required having set
       the following properties:
       <ul>
         <li>torque.database.default</li>
@@ -89,16 +89,16 @@
       This was done in order to detect misconfiguration more easily.
     </action>
     <action type="update" dev="tfischer">
-      The runtime does not configure the DataSourveFactory with the name "default" 
+      The runtime does not configure the DataSourveFactory with the name "default"
       any more automatically. If you need a DataSourceFactory with that name,
       you have to configure it manually from now on.
     </action>
     <action type="update" dev="tfischer">
-      If Torque is not yet initialized, it does now return null as name of the 
+      If Torque is not yet initialized, it does now return null as name of the
       default database (not "default" as it was before).
     </action>
     <action type="update" dev="tfischer" issue="TRQS252">
-      The asColumns in a Criteria are now added to the SQL select clause 
+      The asColumns in a Criteria are now added to the SQL select clause
       in the same order as they were added to a Criteria.
       To achieve this, the return type of the method Criteria.getAsColumns()
       had to be changed from Hashtable to Map.
@@ -117,11 +117,11 @@
     </action>
     <action type="add" dev="tfischer">
       The database schema.xml is now validated against the DTD. The generator stops
-      and displays an error message if the schema.xml does not satisfy the DTD.  
+      and displays an error message if the schema.xml does not satisfy the DTD.
     </action>
     <action type="fix" dev="tfischer" issue="TRQS286">
       The TorqueJDBCTransformTask now creates a name attribute for the database
-      element. The attribute value is the name of the database user used to 
+      element. The attribute value is the name of the database user used to
       connect to the database.
     </action>
     <action type="add" dev="tfischer" issue="TRQS266">
@@ -130,7 +130,7 @@
     </action>
     <action type="fix" dev="tfischer">
       Changed the length of the tablename column from 255 to 250 in the idbroker
-      schema for the runtimetest. This is necessary because the firebird database 
+      schema for the runtimetest. This is necessary because the firebird database
       cannot create an index on a varchar column which has the length 255.
     </action>
     <action type="fix" dev="tfischer">
@@ -141,15 +141,15 @@
         <li>Column names are no longer put into double quotes by the create-db task</li>
         <li>The template createdb.vm was added to be able to run the create-db task</li>
       </ul>
-      Also, a firebird profile was added for the runtimetest, and firebird was added 
+      Also, a firebird profile was added for the runtimetest, and firebird was added
       to the list of supported databases on the homepage.
     </action>
     <action type="fix" dev="tfischer" issue="TRQS287">
       Changed the name attribute of the database tag from #IMPLIED to #REQUIRED in the dtd.
-    </action> 
+    </action>
     <action type="add" dev="tfischer" issue="TRQS273">
-      Added a database-layout-Howto to the docs. 
-    </action> 
+      Added a database-layout-Howto to the docs.
+    </action>
     <action type="fix" dev="tfischer">
       In Torque 3.1.1, BIT columns were treated as Strings with the value 0 and 1.
       This caused problems in various DBs which natively support BOOLEAN columns
@@ -159,20 +159,20 @@
       However, this behavior breaks BIT support for Databases which do not have
       a native boolean datatype (like Oracle). For these Databases, use BOOLEANINT
       (or BOOLEANCHAR) column types for Booleans.
-    </action> 
+    </action>
     <action type="update" dev="tfischer" issue="TRQS221">
       Changed Postgres handling of boolean Values to use FALSE,TRUE instead of '0','1'
       while selecting from columns of Torque type BIT.
-    </action> 
+    </action>
     <action type="add" dev="tfischer" issue="TRQS251">
       Added support for using SQL functions in "order by".
     </action>
     <action type="update" dev="tfischer">
-      Unify the behaviour of primary key columns. Until now, 
+      Unify the behaviour of primary key columns. Until now,
       primary key columns were not filled automatically for
       idMethod=native and for platforms with
       default idMethod=identity (i.e. all databases exept oracle,
-      postgresql and sapdb). Now, the default is that primary key 
+      postgresql and sapdb). Now, the default is that primary key
       columns are always filled automatically by default.
     </action>
     <action type="fix" dev="tfischer">
@@ -201,19 +201,19 @@
       </ul>
     </action>
     <action type="add" dev="tfischer" issue="TRQS263">
-      Add support for oracle datatype timestamp; 
+      Add support for oracle datatype timestamp;
       limit number of digits for saving integers in oracle to 10.
     </action>
     <action type="fix" dev="tfischer" issue="TRQS267">
       Fix escaping of single quotes in datasql task.
     </action>
     <action type="add" dev="tfischer">
-      Added support for schema support at generate time. 
+      Added support for schema support at generate time.
       See <a href="schema-howto.html">Schema Support Howto</a>.
     </action>
     <action type="remove" dev="tfischer" issue="TRQS222">
-      Removed Oracle Update patch again. 
-      Creates invalid scripts and causes ant to fail. 
+      Removed Oracle Update patch again.
+      Creates invalid scripts and causes ant to fail.
       See Scarab for further details.
     </action>
     <action dev="mpoeschl" type="remove">
@@ -229,7 +229,7 @@
       Remove support for stratum lifecycle interfaces.
     </action>
     <action dev="mpoeschl" type="add" issue="TRQS163">
-      Add domain element to schema.xml. Domains are used to define 
+      Add domain element to schema.xml. Domains are used to define
       attributes for columns.
     </action>
     <action dev="mpoeschl" type="update">
@@ -243,7 +243,7 @@
       default since 3.1)
     </action>
     <action dev="mpoeschl" type="add">
-      Changed ojb-model task to generate Object + BaseObject (like for the 
+      Changed ojb-model task to generate Object + BaseObject (like for the
       torque om).
     </action>
     <action dev="mpoeschl" type="fix">
@@ -277,7 +277,7 @@
       sure that his patch goes in ok.
     </action>
     <action type="update" dev="henning">
-      Started reworking the BasePeer class, factored out some code into SQLBuilder and VillageUtils.  
+      Started reworking the BasePeer class, factored out some code into SQLBuilder and VillageUtils.
     </action>
     <action type="add" dev="henning">
       Make the getter names for the table column values configurable. Torque did generate
@@ -327,15 +327,15 @@
       Add Torque Reporting to the Maven plugin. Patch contributed by Thierry Lach.
     </action>
     <action type="update" dev="henning" issue="TRQS207">
-      Make <code>org.apache.torque.util.SqlEnum</code> public visible. The C'tor is 
+      Make <code>org.apache.torque.util.SqlEnum</code> public visible. The C'tor is
       still private, so this should be no problem.
     </action>
     <action type="update" dev="henning" issue="TRQS239">
-      Fix a typo in the reworked Limit / Offset Code for Oracle and DB2. 
+      Fix a typo in the reworked Limit / Offset Code for Oracle and DB2.
       Confused pre and post.
     </action>
     <action type="update" dev="henning" issue="TRQS240">
-      Fix offset and limit swap for DB2 and Oracle. 
+      Fix offset and limit swap for DB2 and Oracle.
     </action>
   </release>
   <release version="3.1.1-RC3" date="2004-10-16">
@@ -357,11 +357,11 @@
       file. Activated the maven-changes-report.
     </action>
     <action type="update">
-        Changed the default property value for <code>torque.output.dir</code> 
+        Changed the default property value for <code>torque.output.dir</code>
         from <code>maven.build.dest</code> to <code>maven.build.dir</code>.
-        This means many of the generated files will now appear in the 
+        This means many of the generated files will now appear in the
         <code>target</code> rather than the <code>target/classes</code>
-        directory. The properties reference was updated accordingly (a few 
+        directory. The properties reference was updated accordingly (a few
         missing properties were also documented).
     </action>
     <action type="update" dev="henning">
@@ -369,11 +369,11 @@
         method to the generated peer classes
     </action>
     <action type="add" dev="henning">
-        Patrick Carl donated an XSL style sheet to convert Torque schema 
+        Patrick Carl donated an XSL style sheet to convert Torque schema
         files into <a href="http://mogwai.sourceforge.net/erdesigner/erdesigner.html">mogwai ERDesigner</a> files.
     </action>
     <action type="update" dev="seade">
-      Restructured maven project files based on HEAD to gain improved control 
+      Restructured maven project files based on HEAD to gain improved control
       over dependencies.
     </action>
     <action type="update" dev="seade">
@@ -398,21 +398,21 @@
     <action type="fix">
       Deleting an Object containing a timestamp didn't work with PostgreSQL (the
       adapter was missing the necessary method to convert the timestamp into a value
-      that is understood by the databases).     
+      that is understood by the databases).
     </action>
   </release>
   <release version="3.1.1-RC2" date="2004-08-27">
     <action type="fix" dev="henning">
-      <code>limit</code> and <code>offset</code> handling for all databases 
-      other than DB2 was broken.  <code>limit</code> and <code>offset</code> 
-      handling for all databases has been revamped and should now work 
+      <code>limit</code> and <code>offset</code> handling for all databases
+      other than DB2 was broken.  <code>limit</code> and <code>offset</code>
+      handling for all databases has been revamped and should now work
       correctly.
     </action>
    </release>
   <release version="3.1.1-RC1" date="2004-08-26">
     <action type="update">
-      Addressed a number of issues highlighted by 
-      <a href="http://findbugs.sourceforge.net/">FindBugs</a> in generated 
+      Addressed a number of issues highlighted by
+      <a href="http://findbugs.sourceforge.net/">FindBugs</a> in generated
       source code.
     </action>
     <action type="update">
@@ -423,18 +423,18 @@
       commons-lang-2.0 and commons-logging-1.0.4.
     </action>
     <action type="fix">
-      HSQL adapter enhancements/fixes: added support for case-insensitive 
+      HSQL adapter enhancements/fixes: added support for case-insensitive
       queries, added support for cascading deletes, correction to the generated
       CREATE TABLE DDL when using IDENTITY columns.  Thanks to Patrick Carl for
       the patch.
     </action>
     <action type="update">
-      The <code>adapter</code> property is now used in preference to 
+      The <code>adapter</code> property is now used in preference to
       <code>driver</code> when building the database map.  This allows Torque
-      to work when the driver setting is not what it expects - e.g. if using 
-      <code>com.mysql</code> driver instead of the 
-      <code>org.gjt.mm.mysql</code> or when using 
-      <a http="http://www.p6spy.org/">P6Spy</a> pass through driver for 
+      to work when the driver setting is not what it expects - e.g. if using
+      <code>com.mysql</code> driver instead of the
+      <code>org.gjt.mm.mysql</code> or when using
+      <a http="http://www.p6spy.org/">P6Spy</a> pass through driver for
       performance monitoring.  Thanks to Ben Hogan for the patch.
     </action>
     <action type="add">
@@ -451,8 +451,8 @@
       solution implemented has been tested under MySLQ and PostgreSQL only.
     </action>
     <action type="fix">
-      Multiple unique constraints and indexes on a single table are now 
-      allocated sequential names (previously duplicate names were being 
+      Multiple unique constraints and indexes on a single table are now
+      allocated sequential names (previously duplicate names were being
       allocated).
     </action>
     <action type="fix">
@@ -460,30 +460,30 @@
       to HEAD some time ago.
     </action>
     <action type="fix">
-      Generate sequences correctly for PostgreSQL (i.e. leave it to 
+      Generate sequences correctly for PostgreSQL (i.e. leave it to
       PostgreSQL).  Note that schemas produced from the database using
       the <code>torque:jdbc</code> goal are not yet handling sequences
       correctly.
     </action>
     <action type="fix" issue="TRQD26">
-      Problems with Torque tutorial.  The Torque tutorial has been 
+      Problems with Torque tutorial.  The Torque tutorial has been
       updated to reflect the separated generator and runtime components and
       to use the Maven plugin.
     </action>
     <action type="fix">
-      The generator logging configuration has been changed from DEBUG to INFO 
-      - this will make the day of all those people that for some reason have 
+      The generator logging configuration has been changed from DEBUG to INFO
+      - this will make the day of all those people that for some reason have
       the torque-gen jar in their classpath at runtime.  <b>Hint: You don't
       need this jar to use the Torque generated object model classes.</b>
     </action>
     <action type="fix">
-      The maven-plugin now provides default values for 
+      The maven-plugin now provides default values for
       <code>torque.initialIDValue</code> and
-      <code>torque.initialIDStep</code> so that the id table initialization 
+      <code>torque.initialIDStep</code> so that the id table initialization
       sql is now generated correctly.
     </action>
     <action type="fix" issue="TRQS223">
-      The get${pVarName} method in the Object.vm template does not 
+      The get${pVarName} method in the Object.vm template does not
       return related objects with a negative PK.  Thanks to Nick Curry for
       the patch.
     </action>
@@ -495,15 +495,15 @@
       short or byte.
     </action>
     <action type="fix" issue="TRQS149">
-      For PostgreSQL the LONGVARCHAR datatype now maps to 
+      For PostgreSQL the LONGVARCHAR datatype now maps to
       <em>text</em> rather than <em>bytea</em>.
     </action>
     <action type="fix" issue="TRQS190">
       Error on "byte" data type generation rules.
     </action>
     <action type="fix">
-      A minor template change has been made to correctly allow 
-      Base[TableName]Peer.doDelete(criteria, connection) to be overridden in 
+      A minor template change has been made to correctly allow
+      Base[TableName]Peer.doDelete(criteria, connection) to be overridden in
       [TableName]Peer.
     </action>
   </release>
@@ -511,7 +511,7 @@
   <release version="3.1" date="2003-09-01">
     <action type="fix">
       SqlExpression: replace UniqueList with HashSet to improve performace for
-      large IN clause.      
+      large IN clause.
     </action>
   </release>
 
@@ -534,16 +534,16 @@
       ClassLoader.
     </action>
     <action type="update">
-      The generated schema-data.dtd has been changed to allow any order of 
+      The generated schema-data.dtd has been changed to allow any order of
       table data entries.
     </action>
     <action type="update">
-      The old Torque connection pool is deprecated. You should use the 
+      The old Torque connection pool is deprecated. You should use the
       commons-dbcp pool.
     </action>
     <action type="update">
-      Upgraded to latest commons-dbcp snapshot. The new 
-      SharedPoolDatasourceFactory is now used by default. Don't forget to 
+      Upgraded to latest commons-dbcp snapshot. The new
+      SharedPoolDatasourceFactory is now used by default. Don't forget to
       upgrade your property file!
     </action>
     <action type="fix" issue="TRQS51">
@@ -553,9 +553,9 @@
       Torque.initialize not reentrant
     </action>
     <action type="fix" issue="TRQS87">
-      name conflict in generated java sources when using java reserved 
+      name conflict in generated java sources when using java reserved
       words (like "class") as column names. <br/>
-      <code>Column.UncapitalisedJavaName</code> is now used as member name 
+      <code>Column.UncapitalisedJavaName</code> is now used as member name
       instead of <code>Column.Name.toLowerCase()</code> <br/>
     </action>
     <action type="fix" issue="TRQS136">
@@ -569,7 +569,7 @@
     </action>
     <action type="fix" issue="TRQS178">
       use sql autoincrement only if idMethod native.<br/>
-      So you have to set idMethod="native" (table) plus autoincrement="true" 
+      So you have to set idMethod="native" (table) plus autoincrement="true"
       (column) to generate the autoincrement code in your sql.
     </action>
   </release>
@@ -580,23 +580,23 @@
       BaseObject.log() and .getLog() now return a Log object.
     </action>
     <action type="update">
-      The DTD resolver will now use the database.dtd from the classpath if the 
+      The DTD resolver will now use the database.dtd from the classpath if the
       DTD is http://db.apache.org/torque/dtd/database_3_1.dtd.
     </action>
     <action type="update">
       LargeSelect now implements Serializable, provides better debugging
       information and further methods for maintaining search parameters.
     </action>
-    <action type="update">  
-      LargeSelect is now thread safe when calling invalidateResult 
-      (thanks to Soteri Panagou &lt;panagos@midetech.com&gt;). 
+    <action type="update">
+      LargeSelect is now thread safe when calling invalidateResult
+      (thanks to Soteri Panagou &lt;panagos@midetech.com&gt;).
     </action>
-    <action type="update">  
-      Updated ojb tasks to work for OJB 1.0(rc3). The generated modell is very 
+    <action type="update">
+      Updated ojb tasks to work for OJB 1.0(rc3). The generated modell is very
       simple. Support for advanced features will be added in the future.
     </action>
     <action type="fix" issue="TRQS20">
-      mysql: "on delete cascade" not generated 
+      mysql: "on delete cascade" not generated
     </action>
     <action type="fix" issue="TRQS101">
       Sql2Xml task should generate a dtd compliant xml
@@ -609,21 +609,21 @@
     </action>
     <action type="fix" issue="TRQS139">
       wrong invocation of populateObject in peer class
-    </action>  
+    </action>
     <action type="fix" issue="TRQS141">
       Table with no primary key results an empty ADD PRIMARY KEY ()
-    </action>  
+    </action>
     <action type="fix" issue="TRQS153">
-      BasePeer.doSelect(Criteria, Connection) calls executeQuery 
+      BasePeer.doSelect(Criteria, Connection) calls executeQuery
       without offset and limit.
     </action>
     <action type="fix" issue="TRQS159">
       Invalid syntaxes for Hypersonic when using indexes.
     </action>
     <action type="fix" issue="TRQS165">
-      columns in an external schema caused Manager imports to be 
+      columns in an external schema caused Manager imports to be
       generated
-    </action>  
+    </action>
     <action type="fix">
       Corrected deadly multi-CPU thread deadlock problem discovered by
       Ed Korthof &lt;ed@apache.org&gt; and John McNally

Modified: db/torque/runtime/trunk/xdocs/configuration-howto.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/configuration-howto.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/configuration-howto.xml (original)
+++ db/torque/runtime/trunk/xdocs/configuration-howto.xml Wed Aug 24 05:38:09 2005
@@ -39,13 +39,13 @@
 factory that uses jndi to retrieve the <code>DataSource</code>.
 The jndi factory looks up a <code>DataSource</code> bound to jndi; it
 also provides a simple property file based way to configure and deploy most
-<code>DataSource</code>'s, though in many cases a pool may already be 
+<code>DataSource</code>'s, though in many cases a pool may already be
 bound to jndi and torque only needs to use it.
 </p>
 
 <p>
 Before going over how to configure the factories, which will take up most the
-content of this document, you must first consider your database handles and 
+content of this document, you must first consider your database handles and
 adapters.
 </p>
 
@@ -54,14 +54,14 @@
 <section name="Database handles">
 
 <p>
-A database handle is the name attribute that was used in the 
-<code>&lt;database&gt;</code> tag of the schema.xml file.  If the name 
+A database handle is the name attribute that was used in the
+<code>&lt;database&gt;</code> tag of the schema.xml file.  If the name
 attribute is not used, then the handle would be 'default'.
 </p>
 
 <p>
-In all examples that follow we will use the handle 'bookstore'.  As Torque has 
-the ability to use multiple databases you can tell it which one to use by 
+In all examples that follow we will use the handle 'bookstore'.  As Torque has
+the ability to use multiple databases you can tell it which one to use by
 default thus:</p>
 
 <source><![CDATA[
@@ -126,10 +126,10 @@
 <section name="SharedPoolDataSourceFactory">
 
 <p>
-This factory uses the more full featured DataSource available in the 
-commons-dbcp package. SharedPoolDataSourceFactory provides an easy way 
-to configure this pool and it assumes you will have a jdbc Driver class 
-providing the physical database connections.  Again, you must let torque know 
+This factory uses the more full featured DataSource available in the
+commons-dbcp package. SharedPoolDataSourceFactory provides an easy way
+to configure this pool and it assumes you will have a jdbc Driver class
+providing the physical database connections.  Again, you must let torque know
 you are using this factory.
 </p>
 
@@ -139,7 +139,7 @@
 ]]></source>
 
 <p>
-Then there are two sets of properties related to the pool configuration and 
+Then there are two sets of properties related to the pool configuration and
 settings for making the connection to the database.
 </p>
 
@@ -159,9 +159,9 @@
 <p>
 Comparing this with the torque's old pool, you can see that this pool does not
 rely on expirying connections periodically to maintain their validity.  The
-pool can be setup to test each connection before returning it to the 
+pool can be setup to test each connection before returning it to the
 application, so the likelihood of the application receiving a bad connection
-is much smaller than using <code>TorqueClassicDataSource</code>. 
+is much smaller than using <code>TorqueClassicDataSource</code>.
 Torque also includes a factory for the <code>PerUserPoolDataSource</code>.
 Please see the commons-dbcp javadoc for more info.
 </p>
@@ -194,9 +194,9 @@
 ]]></source>
 
 <p>
-This line defines the string that will be used to lookup the 
+This line defines the string that will be used to lookup the
 <code>DataSource</code> within the default jndi <code>InitialContext</code>.
-If everything is configured and the default <code>InitialContext</code> 
+If everything is configured and the default <code>InitialContext</code>
 contains the <code>DataSource</code>, this is all that is
 needed.  The default <code>InitialContext</code> is chosen according to the
 rules given in the class's javadoc.  If the default has not been configured,
@@ -219,10 +219,10 @@
 <p>
 One of the advantages of jndi is that it supports changing
 the <code>DataSource</code> on the fly. On the other hand this means that the
-actual <code>DataSource</code> object must be looked up in the context with 
+actual <code>DataSource</code> object must be looked up in the context with
 every database operation. To avoid this, the factory provides a simple
 caching mechanism, which stores the <code>DataSource</code> object for a
-configurable amount of time (im ms). The <b>t</b>ime between <b>t</b>wo 
+configurable amount of time (im ms). The <b>t</b>ime between <b>t</b>wo
 <b>l</b>ookups is specified as follows:
 </p>
 
@@ -240,7 +240,7 @@
 
 <p>
 Generally a J2EE environment such as a servlet engine or application server is
-expected to provide a jdbc2 compatible connection pool.  If your application 
+expected to provide a jdbc2 compatible connection pool.  If your application
 is not running within such an environment, or even if it is and torque is your
 only use of a connection pool, torque provides a simple properties file
 method of configuring a <code>DataSource</code> and deploying it via jndi.
@@ -265,7 +265,7 @@
 ]]></source>
 
 <p>
-In the above example two objects are being configured.  One is a 
+In the above example two objects are being configured.  One is a
 <code>DataSource</code> that is used by the application (torque).  The other is
 a <code>ConnectionPoolDataSource</code> that is provided as part of a jdbc2
 driver.  If the jdbc driver implementation you are using does not fully
@@ -274,11 +274,11 @@
 provided in commons-dbcp where <code>BasicDataSource</code> provides a
 <code>DataSource</code> frontend, and has properties to directly configure
 a jdbc1 <code>Driver</code>.  But regardless of the implementation torque
-uses commons-beanutils package to call the setters on the object using 
+uses commons-beanutils package to call the setters on the object using
 reflection.
 </p>
 
-<p>Torque uses the jndi path properties to know where to deploy the 
+<p>Torque uses the jndi path properties to know where to deploy the
 configured objects.  So you would have the two following properties in
 addition to the datasource props:
 </p>
@@ -289,8 +289,8 @@
 ]]></source>
 
 <p>
-The second handle, DBbookstore, has no relevance to torque, other than 
-to uniquely identify this group of properties as belonging together.  Any 
+The second handle, DBbookstore, has no relevance to torque, other than
+to uniquely identify this group of properties as belonging together.  Any
 unique handle may be used.
 </p>
 
@@ -299,11 +299,11 @@
 <subsection name="Tomcat example of external configuration/binding">
 
 <p>
-If you have other parts of your application that need to use the same 
+If you have other parts of your application that need to use the same
 connection pool and torque cannot be guaranteed to be initialized in time for
 these other uses, or if you just want to follow your j2ee environment's
 standard jndi deployment pattern, torque can just make use of these externally
-deployed pools.  Here is an example using catalina of deploying the pool that 
+deployed pools.  Here is an example using catalina of deploying the pool that
 used to come with torque, but is now part of commons-jdbc2pool.
 </p>
 
@@ -338,7 +338,7 @@
   </ResourceParams>
 ]]></source>
 
-<p>In web.xml.  Elements must be given in the order of the dtd described in 
+<p>In web.xml.  Elements must be given in the order of the dtd described in
 the servlet specification:
 </p>
 
@@ -372,7 +372,7 @@
 ]]></source>
 
 <p>
-Remember that jdbc2 pools expect a 
+Remember that jdbc2 pools expect a
 <code>ConnectionPoolDataSource</code>
 available via jndi under the name given in the dataSourceName, so you will
 need entries in server.xml and web.xml for this object as well.
@@ -381,8 +381,8 @@
 <p>
 Catalina provides a default <code>DataSource</code> that can be used as well
 and it is configured similarly, but detailed information on that
-implementation is <a href="http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html">here</a>.  Note that the 
-"type attribute/ref-type element" value of "javax.sql.DataSource" appears to 
+implementation is <a href="http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jndi-resources-howto.html">here</a>.  Note that the
+"type attribute/ref-type element" value of "javax.sql.DataSource" appears to
 be reserved for catalina's default implementation, which is why the
 implementation classname is used in our configuration example.
 </p>
@@ -393,9 +393,9 @@
 <subsection name="An example configuration from scarab">
 
 <p>
-The following example shows a complete torque configuration from 
+The following example shows a complete torque configuration from
 scarab, an issue tracking application, running under catalina, but using torque
-to deploy the <code>DataSource</code>.  It is here to 
+to deploy the <code>DataSource</code>.  It is here to
 put together some of the details shown above.
 </p>
 

Modified: db/torque/runtime/trunk/xdocs/criteria-howto.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/criteria-howto.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/criteria-howto.xml (original)
+++ db/torque/runtime/trunk/xdocs/criteria-howto.xml Wed Aug 24 05:38:09 2005
@@ -39,15 +39,15 @@
   <section name="Ordering the Results">
 
    <p>
-     One of the common clauses in an SQL Query is the ORDER BY clause. 
-     With the criteria object, the results can be ordered via the 
-     addAscendingOrderByColumn(String columnname) and 
-     addDescendingOrderByColumn(String columnname) methods. 
+     One of the common clauses in an SQL Query is the ORDER BY clause.
+     With the criteria object, the results can be ordered via the
+     addAscendingOrderByColumn(String columnname) and
+     addDescendingOrderByColumn(String columnname) methods.
      As an example, consider the book table from the tutorial. To get all books ordered by their
      title and ISBN (where the ISBN should only be taken into accout for equal titles),
      use the following code:
    </p>
-   
+
    <source>
 Criteria criteria = new Criteria();
 criteria.addAscendingOrderByColumn(BookPeer.TITLE);
@@ -62,59 +62,59 @@
   <section name="Using Criteria to create Joins ">
 
    <p>
-    In a relational database, there are two different join types: 
+    In a relational database, there are two different join types:
     inner joins and outer joins. Both types can be generated using Torque
     and will be discussed seperately in the following:
    </p>
-  
+
     <subsection name="Inner joins">
       <p>
         Imagine we want to know all authors which have published at least one book.
         This can be achieved using the following code:
       </p>
-      
+
       <source>
 Criteria criteria = new Criteria();
 criteria.addJoin(AuthorPeer.AUTHOR_ID, BookPeer.AUTHOR_ID, Criteria.INNER_JOIN);
-  
+
 List bookAuthors = AuthorPeer.doSelect(criteria);</source>
-      
+
       <p>
         This method creates a so called "inner join", i.e. only author entries
         which have a corresponding book entry are selected.
       </p>
-    
+
       <table>
         <tr>
           <th>Details</th>
         </tr>
         <tr>
           <td>
-    		    All joins which are created using Criteria are only used for data selection, 
+    		    All joins which are created using Criteria are only used for data selection,
     		    not for reading the related objects.
     		    For example, in the above code, only author objects are read in from the database.
     		    The book objects which are related to the authors are not read,
-    		    meaning that 
+    		    meaning that
     	    	<source>
 Author author = (Author) bookAuthors.get(0);
 List books = author.getBooks();</source>
     		    performs a background read in the database to get all the books for one author.
-    		    
+
     		    If you do not like this behaviour, there are also methods which do read the
-    		    related objects, see for example BaseBookPeer.doSelectJoinAuthor(). 
+    		    related objects, see for example BaseBookPeer.doSelectJoinAuthor().
     		    These methods are protected to keep the public API reasonable.
     		    If you need public access to such a method, simply overwrite the method in
     		    the Peer class and declare the method public. Note that these methods perform
-    		    inner joins (this behavour will hopefully be changed in the near future). 
+    		    inner joins (this behavour will hopefully be changed in the near future).
           </td>
         </tr>
         <tr>
           <td>
-    		    Also, in SQL, there are two different ways to state an inner join. 
+    		    Also, in SQL, there are two different ways to state an inner join.
     		    The first way is a statement like
     	    	<source>
-SELECT BOOK.* FROM BOOK INNER JOIN AUTHOR ON BOOK.AUTHOR_ID=AUTHOR.AUTHOR_ID</source> 
-            SQL like this is produced if the join type is stated explicitly 
+SELECT BOOK.* FROM BOOK INNER JOIN AUTHOR ON BOOK.AUTHOR_ID=AUTHOR.AUTHOR_ID</source>
+            SQL like this is produced if the join type is stated explicitly
             (as above).<br />
             The second way to create an inner join is
     	    	<source>
@@ -124,7 +124,7 @@
             <source>
 criteria.addJoin(AuthorPeer.AUTHOR_ID, BookPeer.AUTHOR_ID);</source>
             Note that both SQL statements return the same result set. <br/>
-            It is not possible to combine both ways of creating a join 
+            It is not possible to combine both ways of creating a join
             in most databases, i.e. code like
             <source>
 criteria.addJoin(AuthorPeer.AUTHOR_ID, BookPeer.AUTHOR_ID);
@@ -132,69 +132,69 @@
             produces an SQL error in most databases.
             In most circumstances, it is recommended to state t
             the join type explicitly.
-            However, if the "INNER JOIN" syntax is not supported by your database, 
+            However, if the "INNER JOIN" syntax is not supported by your database,
             try not to state the join type explicitly.
-          </td>        
-  
+          </td>
+
         </tr>
       </table>
     </subsection>
-    
+
     <subsection name="Outer joins">
       <p>
         To discuss the difference between inner joins and outer joins, consider the
         following code fragments. Joins will be used there just for discussing the effects
         of the different join types, but for no other reason.
       </p>
-  
+
       <p>
         First, let us reconsider the inner join code:
       </p>
-  
+
       <source>
 Criteria criteria = new Criteria();
 criteria.addJoin(AuthorPeer.AUTHOR_ID, BookPeer.AUTHOR_ID, Criteria.INNER_JOIN);
-  
+
 List bookAuthors = AuthorPeer.doSelect(criteria);</source>
-  
+
   	  <p>
-  	    For an inner join, the database only returns an entry 
+  	    For an inner join, the database only returns an entry
   	    in one table if there is a corresponding entry in the other table.
-  	    In the example above, this means that only authors 
+  	    In the example above, this means that only authors
   	    with a book are read.
   	    In contrast, with an outer join, an entry in one table is also returned
   	    even if there is no corresponding entry in the other table:
   	  </p>
-  
+
       <source>
 Criteria criteria = new Criteria();
 criteria.addJoin(AuthorPeer.AUTHOR_ID, BookPeer.AUTHOR_ID, Criteria.LEFT_JOIN);
 List authors = AuthorPeer.doSelect(criteria);</source>
-      
+
       <p>
-        The above code uses a left (outer) join. There, authors 
-        which have no books also appear in the list of authors. 
-        There are two kinds of outer joins: left joins and right joins. 
+        The above code uses a left (outer) join. There, authors
+        which have no books also appear in the list of authors.
+        There are two kinds of outer joins: left joins and right joins.
         In a left join, entries in the first table are returned even if
         no entry in the second table is found, whereas in a right join,
         entries in the second table are returned even if there are no
-        entries in the first table. Both kinds are supported in Torque 
+        entries in the first table. Both kinds are supported in Torque
         via the constants Criteria.LEFT_JOIN and Criteria.RIGHT_JOIN.
       </p>
-      
+
       <p>
-        Usually, outer joins are used for reading in several tables at once 
-        (not ?yet? supported in Torque), or for ordering the contents 
+        Usually, outer joins are used for reading in several tables at once
+        (not ?yet? supported in Torque), or for ordering the contents
         of one table by the contents of another table.
       </p>
     </subsection>
-  
+
   </section>
 
   <section name="Using DISTINCT with Criteria">
 
    <p>
-     All of the examples in the section "joins" return multiples 
+     All of the examples in the section "joins" return multiples
      of the desired table columns.
      In the first example, the author will appear for every book that is
      attached to it. If an author has published 10 books,
@@ -227,9 +227,9 @@
 criteria.addJoin(AuthorPeer.AUTHOR_ID, BookPeer.AUTHOR_ID, Criteria.INNER_JOIN);
 criteria.setDistinct();
 criteria.addAscendingOrderByColumn(AuthorPeer.NAME);
-      
+
 List bookAuthors = AuthorPeer.doSelect(criteria);</source>
-    
+
   </section>
 
   <section name="Using the Comparators in Criteria">
@@ -287,15 +287,15 @@
   <section name="Case insensitive LIKE Comparator">
 
    <p>
-     A LIKE comparison is usually case sensitive (unless the underlying 
+     A LIKE comparison is usually case sensitive (unless the underlying
      database only provides case sensitive LIKE clauses - e.g. MySQL).  To get
-     a case insensitive LIKE you need to tell the criteria that it should 
+     a case insensitive LIKE you need to tell the criteria that it should
      ignore the case thus:
    </p>
 
 <source>
 Criteria criteria = new Criteria();
-criteria.add(InvoicePeer.TABLE_NAME, searchField, 
+criteria.add(InvoicePeer.TABLE_NAME, searchField,
         (Object) ("%" + searchCriteria + "%"), Criteria.LIKE);
 criteria.getCriterion(InvoicePeer.TABLE_NAME, searchField).setIgnoreCase(true);
 
@@ -303,7 +303,7 @@
 </source>
 
    <p>
-     For PostgreSQL this will use ILIKE, for other databases it will use the 
+     For PostgreSQL this will use ILIKE, for other databases it will use the
      SQL upper() function on the column and search string (for Oracle you may
      want to define a function index to make this efficient).
    </p>

Modified: db/torque/runtime/trunk/xdocs/database-layout-howto.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/database-layout-howto.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/database-layout-howto.xml (original)
+++ db/torque/runtime/trunk/xdocs/database-layout-howto.xml Wed Aug 24 05:38:09 2005
@@ -22,67 +22,67 @@
  </properties>
 
  <body>
- 
+
   <p>
-   This Howto is NOT meant as a complete guide of how to design a database. 
+   This Howto is NOT meant as a complete guide of how to design a database.
    On the contrary, it is meant as a kind of addon, in the sense of
    &quot;If I know in general how to design a databasein general, what do I have to
-   keep in mind if I use Torque to access that database&quot; 
+   keep in mind if I use Torque to access that database&quot;
   </p>
 
   <section name="Things not supported by Torque">
-   
+
    <subsection name="Column names">
-   
+
     <p>
      There are some column names which you can not use in Torque although
-     your database would support them. The reason is that they would 
+     your database would support them. The reason is that they would
      produce constants twice in the generated code. The column names which
      cannot be used are (case is ignored)
      <ul>
       <li>TABLE_NAME</li>
       <li>DATABASE_NAME</li>
-     </ul>     
+     </ul>
     </p>
-   
+
     <p>
-     Furthermore, it is recommended that you do not use words which have 
+     Furthermore, it is recommended that you do not use words which have
      a defined meaning in SQL as column names. Even if you can trick your
      database into using them, it is not sure whether Torque can do the same.
      And besides, even if it works for one database, if you ever decide
-     to use another database, you may run into trouble then. 
+     to use another database, you may run into trouble then.
     </p>
-     
+
    </subsection>
-   
+
   </section>
 
-  
+
   <section name="Design considerations">
-  
+
    <p>
-    These design considerations apply to the most common uses of a database. 
+    These design considerations apply to the most common uses of a database.
     In some cases where you have to meet very special challanges, there will
     be reasons not to follow the advice given here. But in general,
     you will be fine if you follow these guidelines.
    </p>
-   
+
    <subsection name="Primary keys">
-    
+
     <p>
-     For every table, you should create a primary key which has no meaning 
+     For every table, you should create a primary key which has no meaning
      in real life. The reasons for this are:
     </p>
-    
+
     <p>
-     You should use a primary key at all because it creates a well-defined 
-     link between the objects in the database and the objects in memory. 
+     You should use a primary key at all because it creates a well-defined
+     link between the objects in the database and the objects in memory.
      Often, one has to decide whether a java object in memory describes
      &quot;the same&quot; object as a certain row in the database. For example,
-     if you read an object from a database, change a field value and 
-     write it again to the database, you would usually want to update the 
+     if you read an object from a database, change a field value and
+     write it again to the database, you would usually want to update the
      row you read from. This is only possible if Torque can find the row
-     in the database from which the object originated. For this, the 
+     in the database from which the object originated. For this, the
      primary key is used in relational databases. If two java objects have
      the same primary key, they describe &quot;the same thing&quot; and refer
      to the same row in the database. If you do not have
@@ -90,30 +90,30 @@
      objects describe &quot;the same thing&quot;. You might run into not
      being able to update an object.
     </p>
-    
+
     <p>
-     Now that we know why we want to have a primary key at all, why should 
-     it have no meaning in real life ? This can be explained best by an 
-     example. Consider a table which holds manufactured parts. Each part 
+     Now that we know why we want to have a primary key at all, why should
+     it have no meaning in real life ? This can be explained best by an
+     example. Consider a table which holds manufactured parts. Each part
      has an unique serial number. So it is tempting to use the serial number
-     as a primary key. But now imagine that we have registered the wrong 
-     serial number for a certain part in the database. Remember that 
-     the primary key is used to decide &quot;is it the same object?&quot; 
+     as a primary key. But now imagine that we have registered the wrong
+     serial number for a certain part in the database. Remember that
+     the primary key is used to decide &quot;is it the same object?&quot;
      So we cannot change the serial number of a specified object without
-     making it another object. 
-    </p>  
-   
+     making it another object.
+    </p>
+
     <p>
      In Torque, this problem manifests itself in that there is no easy way
      to change the primary key of an object; you must trick Torque into it
      by using Torque's internals. This should be avoided if possible.
      If you use an additional primary key which
      has no meaning in real life, you do not run into that trouble.
-    </p>   
-   
+    </p>
+
    </subsection>
-   
-  </section> 
- 
+
+  </section>
+
  </body>
 </document>

Modified: db/torque/runtime/trunk/xdocs/developer-guide.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/developer-guide.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/developer-guide.xml (original)
+++ db/torque/runtime/trunk/xdocs/developer-guide.xml Wed Aug 24 05:38:09 2005
@@ -59,30 +59,30 @@
     <section name="Building from SVN">
       <p>
         The Torque build process uses
-        <a href="http://maven.apache.org">Maven</a>.  Before you begin, you'll 
-        need to check out the <code>db-torque</code> SVN repository (if you are 
+        <a href="http://maven.apache.org">Maven</a>.  Before you begin, you'll
+        need to check out the <code>db-torque</code> SVN repository (if you are
         not familiar with the Apache SVN repositories, please refer to the
         <a href="http://www.apache.org/dev/version-control.html">documentation</a>).
-        Specific information for Torque is available on the 
+        Specific information for Torque is available on the
         <a href="cvs-usage.html">Source Repository</a> page.
       </p>
       <p>
-        To build the Torque generator jar, first execute 
-        <code>maven jar:install</code> in the 
-        <code>src/generator/src/templates</code> directory to install a copy 
+        To build the Torque generator jar, first execute
+        <code>maven jar:install</code> in the
+        <code>src/generator/src/templates</code> directory to install a copy
         of the templates jar in your local Maven repository. Note that
-        <code>maven jar:jar</code> does not suffice here because the 
+        <code>maven jar:jar</code> does not suffice here because the
         main generator jar depends upon the template jar.
         Afterwards, execute <code>maven jar:jar</code> in the src/generator
-        directory to build the generator jar (<code>maven jar:install</code> 
+        directory to build the generator jar (<code>maven jar:install</code>
         to install a copy of the jar in your local Maven repository).
       </p>
       <p>
-        To build and install the Torque maven-plugin execute <code>maven 
+        To build and install the Torque maven-plugin execute <code>maven
         plugin:install</code> in the <code>src/maven-plugin</code> directory.
       </p>
       <p>
-        To build the Torque runtime jar execute <code>maven jar:jar</code> in 
+        To build the Torque runtime jar execute <code>maven jar:jar</code> in
         the root directory of the project (<code>maven jar:install</code> to
         install a copy of the jar in your local Maven repository).
       </p>
@@ -108,7 +108,7 @@
       ]]></source>
 
       <p>
-        Please report any problems to the 
+        Please report any problems to the
         <a href="mailto:torque-dev@db.apache.org">torque-dev</a> mailing list.
       </p>
 
@@ -119,27 +119,27 @@
         This section is meant to to provide some insight into the initialisation procedure
         of Torque.
         On initialisation, Torque needs to provide the following resources to work properly
-        <ul> 
+        <ul>
           <li>
             The name of the default database, configured by the key
             torque.database.default
-          </li> 
+          </li>
           <li>
-            The adapters, configured by the keys 
+            The adapters, configured by the keys
             torque.database.&lt;databaseName&gt;.adapter
-          </li> 
+          </li>
           <li>
             The DataSourceFactories, configured by the keys
-            torque.dsfactory.&lt;databaseName&gt;.&lt;property&gt;. 
+            torque.dsfactory.&lt;databaseName&gt;.&lt;property&gt;.
             For some DataSourceFactories, default values can be defined under
             torque.defaults.&lt;property&gt;.
           </li>
           <li>
             The Database maps. Each peer class registers its Map builder with the Torque
-            runtime when the Base Peer Class is loaded (Usually, a peer class is loaded 
+            runtime when the Base Peer Class is loaded (Usually, a peer class is loaded
             if one of the constants for a column name is accessed, or a method
             is called). If Torque is already initialized when the Peer class is loaded
-            (this is usually the case) the Map Builder builds the database map instantly 
+            (this is usually the case) the Map Builder builds the database map instantly
             and makes it avaliable to Torque. If Torque is not yet initialized,
             the Peer class stores the Map Builder with Torque, which builds the database
             Map when Torque is initialized.
@@ -149,39 +149,39 @@
           </li>
         </ul>
       </p>
-      
+
     </section>
-    
+
     <section name="Internal resources used by the Torque Runtime">
-    
+
       <subsection name="Default database name">
         <p>
           Torque can be used with several databases at once. The resources for each
           database are usually kept in Maps where the key is the name of the database.
           To make things easier for people who use only one database, Torque supports
-          the notion of a default database. This allows it to provide convenience 
-          methods like Torque.getConnection() where no database name must be specified. 
+          the notion of a default database. This allows it to provide convenience
+          methods like Torque.getConnection() where no database name must be specified.
           These methods refer to the default database, in contrast to e.g.
           Torque.getConnection(String) where the name of the database must be supplied
           explicitly.
         </p>
       </subsection>
-    
+
       <subsection name="Adapters">
         <p>
-          Although all databases supported by Torque understand SQL, there are 
+          Although all databases supported by Torque understand SQL, there are
           differences in the behaviour of the databases which the Torque runtime
           needs to know about. For example, the standard (String) format of a date
           object in an oracle9i database is different from a postgresql database.
           The adapter for a database provides the necessary methods to hide such
-          differences from the user. 
-          For example, the adapter provides a method to create a String in the 
+          differences from the user.
+          For example, the adapter provides a method to create a String in the
           database's preferred format from a Date object.
         </p>
-        
+
         <p>
           Adapters are subclasses of the org.apache.torque.adapter.DB class.
-          The adapters are stored in the private map TorqueInstance.apdapterMap; 
+          The adapters are stored in the private map TorqueInstance.apdapterMap;
           the key of the map is the name of the database (e.g. "bookstore"), and the
           value of the map is the adapter. The adapter for a given key
           can be retrieved via the method Torque.getDB(key).
@@ -194,37 +194,37 @@
           A DataSource is an object which can provide Connections to the database.
           A DataSourceFactory is used to configure and provide one DataSource.
         </p>
-        
+
         <p>
           DataSourceFactories must implement the interface
           org.apache.torque.dsfactory.DataSourceFactory.
-          The DataSourceFactories are stored in the private map 
-          TorqueInstance.dsFactoryMap; the key of the map is the 
+          The DataSourceFactories are stored in the private map
+          TorqueInstance.dsFactoryMap; the key of the map is the
           name of the database (e.g. "bookstore"), and the
-          value of the map is the DataSourceFactory. 
+          value of the map is the DataSourceFactory.
           The DataSourceFactory for a given key
-          can not be retrieved by a public method; however, a connection 
+          can not be retrieved by a public method; however, a connection
           from the DataSource for the DataSourceFactory for a given key
           can be obtained by Torque.getConnection(key);
         </p>
       </subsection>
-      
+
       <subsection name="Database maps">
         <p>
           Torque sometimes needs to know internals about the structure of the
           database, e.g. which table contains which columns etc.
-          This knowledge is kept in the database maps. 
+          This knowledge is kept in the database maps.
         </p>
-        
+
         <p>
           Database Maps are instances of the class org.apache.torque.map.DatabaseMap.
           They are kept in the instance variable TorqueInstance.dbMaps. The Map
-          for the database with the name key can be retrieved by the method 
+          for the database with the name key can be retrieved by the method
           Torque.getDatabaseMap(key).
         </p>
       </subsection>
-      
+
     </section>
-    
+
   </body>
 </document>

Modified: db/torque/runtime/trunk/xdocs/download.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/download.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/download.xml (original)
+++ db/torque/runtime/trunk/xdocs/download.xml Wed Aug 24 05:38:09 2005
@@ -19,7 +19,7 @@
  See the License for the specific language governing permissions and
  limitations under the License.
 -->
-	
+
 <document>
 
   <properties>
@@ -161,7 +161,7 @@
           <a href="http://www.apache.org/dist/db/torque/torque-3.2-rc1/source/maven-torque-plugin-3.2-rc1-src.tar.gz.asc">Signature</a>&nbsp;
           <a href="http://www.apache.org/dist/db/torque/torque-3.2-rc1/source/maven-torque-plugin-3.2-rc1-src.tar.gz.md5">MD5</a></td>
     </tr>
-    
+
     <tr>
       <td><a href="http://www.apache.org/dyn/closer.cgi/db/torque/torque-3.2-rc1/source/torque-3.2-rc1-src.zip">ZIP</a>&nbsp;
           <a href="http://www.apache.org/dist/db/torque/torque-3.2-rc1/source/torque-3.2-rc1-src.zip.asc">Signature</a>&nbsp;
@@ -237,7 +237,7 @@
   <p>
     We generate daily snapshots of the DB torque project. These
     are built on a daily base but are only source snapshots. There are no
-    warranties that these build or run. You can get them from 
+    warranties that these build or run. You can get them from
     <a href="http://cvs.apache.org/dist/db/torque/nightly/">nightly snapshot site</a>.
   </p>
 </section>
@@ -252,7 +252,7 @@
 
 <section name="Building The Source">
   <p>
-    Torque uses <a href="http://maven.apache.org">Maven</a> as its 
+    Torque uses <a href="http://maven.apache.org">Maven</a> as its
     build system. Run <code>maven</code> or <code>maven jar:jar</code>
     at the top of the source directory to build the runtime.
   </p>

Modified: db/torque/runtime/trunk/xdocs/index.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/index.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/index.xml (original)
+++ db/torque/runtime/trunk/xdocs/index.xml Wed Aug 24 05:38:09 2005
@@ -167,8 +167,8 @@
       <p>
         If there is no tester for your RDBMS and you want to help, please read
         the <a href="developer-guide.html">developer-guide</a>, run the tests
-        and send your results (and bugfixes ;) to the 
-        <a href="mailto:torque-dev@db.apache.org">torque-dev@db.apache.org</a> 
+        and send your results (and bugfixes ;) to the
+        <a href="mailto:torque-dev@db.apache.org">torque-dev@db.apache.org</a>
         list.
       </p>
     </section>

Modified: db/torque/runtime/trunk/xdocs/jar-guide.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/jar-guide.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/jar-guide.xml (original)
+++ db/torque/runtime/trunk/xdocs/jar-guide.xml Wed Aug 24 05:38:09 2005
@@ -29,22 +29,22 @@
 <p>
   The standard practice for using Torque has been to download the jar, unjar it
   to get the directory structure given in the <a href="user-guide.html">user
-  guide</a>, and  somehow either integrate your source tree and Torque's 
-  un-jared directory  structure. While doable, this was less than desirable, 
+  guide</a>, and  somehow either integrate your source tree and Torque's
+  un-jared directory  structure. While doable, this was less than desirable,
   especially when working with prespecified directory structures, such as that
   used by Maven.
 </p>
 
 <p>
-  Complex build scripts, such as <a href="http://scarab.tigris.org">Scarab's</a>, 
-  which dynamically unjar Torque during the build process and copy over all the 
-  correct files, can get around this, but having to re-develop or even copy such 
+  Complex build scripts, such as <a href="http://scarab.tigris.org">Scarab's</a>,
+  which dynamically unjar Torque during the build process and copy over all the
+  correct files, can get around this, but having to re-develop or even copy such
   capabilities on a project-by-project basis is undesirable do to the relative
   complexity.
 </p>
 
 <p>
-  Instead, it is possible to run Torque without un-jaring it. All that is needed 
+  Instead, it is possible to run Torque without un-jaring it. All that is needed
   is the venerable <code>build-torque.xml</code> and <code>build.properties</code>.
   Everything else can be read  from the classpath and outputted directly to the
   directories that are desired instead of the previous rigid structure.
@@ -56,8 +56,8 @@
 
 <p>
   Along with the <code>build-torque.xml</code> and <code>build.properties</code>,
-  you must ensure that Torque and all of it's dependencies are in the classpath. 
-  For a list of dependencies, please refer to 
+  you must ensure that Torque and all of it's dependencies are in the classpath.
+  For a list of dependencies, please refer to
   <a href="dependencies.html">dependencies.html</a>.
 </p>
 
@@ -69,9 +69,9 @@
 
 
 <p>
-  <strong>Note</strong>, if you set only the above properties, Torque will default 
+  <strong>Note</strong>, if you set only the above properties, Torque will default
   to using the old directory structure to read and output files from. This
-  maintains backwards compatibility, but is not always what is wanted. The next 
+  maintains backwards compatibility, but is not always what is wanted. The next
   section addresses telling Torque where to read and output files.
 </p>
 
@@ -81,7 +81,7 @@
 
 <p>
   The following directory properties allow you to control with a good deal of
-  granularity where Torque will read and output files. The table contains each 
+  granularity where Torque will read and output files. The table contains each
   of the properties, along with it's default value and description.
 </p>
 

Modified: db/torque/runtime/trunk/xdocs/managers-cache.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/managers-cache.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/managers-cache.xml (original)
+++ db/torque/runtime/trunk/xdocs/managers-cache.xml Wed Aug 24 05:38:09 2005
@@ -43,7 +43,7 @@
   </p>
   <p>
     A manager is responsible for instantiating new objects, retrieving stored
-    objects, and possibly caching these objects.  Managers provide static 
+    objects, and possibly caching these objects.  Managers provide static
     accessors for much of its functionality, so usage examples are:
   </p>
 
@@ -52,7 +52,7 @@
     // id is an ObjectKey that identifies the object in the db
     foo = FooManager.getInstance(id);
     // ids is a List of ObjectKey's that identifies objects in the db
-    List foos = FooManager.getInstances(ids); 
+    List foos = FooManager.getInstances(ids);
   ]]></source>
 
 </section>
@@ -60,12 +60,12 @@
 <section name="Business Object Cache">
 
   <p>
-    If no-arg constructor of FooManager, 
+    If no-arg constructor of FooManager,
     calls setRegion(region) where the String region is the key used to
     determine the cache, the manager will cache instances of Foo retrieved
     via the getInstance(ObjectKey id) and getInstances(List ids) methods.
-    One possibility for the region key is the 
-    fully qualified classname with dots replaced by underscores. 
+    One possibility for the region key is the
+    fully qualified classname with dots replaced by underscores.
   </p>
 
   <source><![CDATA[
@@ -79,9 +79,9 @@
   <p>
     The key given for the region is used in a JCS
     configuration file, cache.ccf, to set up a cache that the manager uses
-    to store objects for which it is responsible. See the JCS 
+    to store objects for which it is responsible. See the JCS
     <a href="http://jakarta.apache.org/turbine/jcs/">
-    documentation</a> for details on configuring JCS.  But here is a 
+    documentation</a> for details on configuring JCS.  But here is a
     simple section that creates an in-memory only LRU cache for FooManager.
   </p>
 
@@ -95,13 +95,13 @@
   ]]></source>
 
   <p>
-    It is a good idea to set a region for each manager, but this behavior 
-    is optional.  There also will be no caching if JCS is 
+    It is a good idea to set a region for each manager, but this behavior
+    is optional.  There also will be no caching if JCS is
     not configured for the region given in the Constructor.
   </p>
 
   <p>
-    The generated object model classes have methods for getting objects 
+    The generated object model classes have methods for getting objects
     that are related by foreign keys.  If the FOO table contains an fk to
     the BAR table then Foo.getBar() will exist.  This method uses
     BarManager.getInstance(bar_id) and therefore will return a cached
@@ -118,7 +118,7 @@
     would be preferrable that repeated requests to this method returned
     cached results as opposed to hitting the db for each call.  It could be
     possible to add such caching to the generated method, and Criteria
-    implements an equals() method that would make this possible.  But 
+    implements an equals() method that would make this possible.  But
     determining the equality of a Criteria is complex and possibly buggy (this
     is the perception of the author of this doc, there are no known bugs).
     Invalidating the results has also not been reduced to templated Java code.
@@ -149,8 +149,8 @@
 
   <p>
     In the above code the database will be hit for every call to the method.
-    BarManager provides some convenience code to add caching to the above 
-    method, so it can be rewritten as:  
+    BarManager provides some convenience code to add caching to the above
+    method, so it can be rewritten as:
   </p>
 
   <source><![CDATA[
@@ -158,9 +158,9 @@
 {
     List result = null;
     Boolean b = (deleted ? Boolean.TRUE : Boolean.FALSE);
-    Object obj = BarManager.getMethodResult().get(this, "getFoos", type, b); 
-    if ( obj == null ) 
-    {        
+    Object obj = BarManager.getMethodResult().get(this, "getFoos", type, b);
+    if ( obj == null )
+    {
         Criteria crit = new Criteria();
         crit.add(FooPeer.TYPE_ID, type.getId());
         crit.add(FooPeer.DELETED, deleted);
@@ -168,7 +168,7 @@
 
         BarManager.getMethodResult().put(result, this, "getFoos", type, b);
     }
-    else 
+    else
     {
         result = (List)obj;
     }
@@ -202,16 +202,16 @@
 
   <p>
     An event model exists for invalidating cached method results.  Continuing
-    the example from above, BarManager should register itself as a listener 
+    the example from above, BarManager should register itself as a listener
     with the FooManager.
     Then FooManager will notify BarManager, if a foo.save() is called
-    that might affect its cached results.  The following code is added to 
+    that might affect its cached results.  The following code is added to
     BarManager.java which implements the CacheListener interface.
   </p>
 
   <source><![CDATA[
     /**
-     * Method should be overridden to notify other managers with 
+     * Method should be overridden to notify other managers with
      * relevant CacheEvents.
      */
     protected void registerAsListener()
@@ -226,11 +226,11 @@
 
     public void addedObject(Persistent om)
     {
-        if (om instanceof Foo) 
+        if (om instanceof Foo)
         {
             getMethodResult().removeAll(om, "getFoos");
         }
-        else if (om instanceof X) 
+        else if (om instanceof X)
         {
             getMethodResult().remove(om, GET_URLS);
             getMethodResult().removeAll(om, GET_COMMENTS);
@@ -255,12 +255,12 @@
   ]]></source>
 
   <p>
-    When a foo which is of interest to BarManager is saved, the instance is 
+    When a foo which is of interest to BarManager is saved, the instance is
     passed
     to the appropriate listener method.  This object may contain information
     that could result in no action or possibly more precise repair of the
     cached data.  In the above examples the cache is just cleared of all
-    data that is potentially invalid. 
+    data that is potentially invalid.
     Some code is also added to FooManager to support the invalidation.
   </p>
 
@@ -283,7 +283,7 @@
         List listeners = (List)listenersMap.get(FooPeer.BAR_ID);
         notifyListeners(listeners, oldOm, om);
         return oldOm;
-    }                
+    }
   ]]></source>
 
   <p>

Modified: db/torque/runtime/trunk/xdocs/maven-howto.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/maven-howto.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/maven-howto.xml (original)
+++ db/torque/runtime/trunk/xdocs/maven-howto.xml Wed Aug 24 05:38:09 2005
@@ -58,7 +58,7 @@
   <p>
     The advent of Maven allows Torque to be used in a much simpler manner. With
     the Maven plugin, absolutely no Torque-related resources (except the Torque
-    jar file iteself) are required to be locally installed in each project. 
+    jar file iteself) are required to be locally installed in each project.
     Instead, the plugin will automatically download any required resources for
     you.
   </p>
@@ -82,25 +82,25 @@
   <p>
     Building the maven plugin from source is relatively easy - you might want
     to do this if there are fixes or enhancements in SVN that you want to make
-    use of.  Another reason you might want to do this is if you wish to 
-    make your own copy of the plugin that includes a set of customized 
+    use of.  Another reason you might want to do this is if you wish to
+    make your own copy of the plugin that includes a set of customized
     generator templates to modify the object model class files that will be
     produced.
   </p>
 
   <p>
     The first thing to do is to check out Torque from SVN (make sure you use
-    branch tag you desire).  If you want to modify any of the generator 
-    templates you would do this before running <code>maven 
-    plugin:install</code> from the <code>src/maven-plugin</code> directory. 
-    This will jar together the various plugin files copy it into your 
-    <code>${maven.home}/plugins</code> directory.  
+    branch tag you desire).  If you want to modify any of the generator
+    templates you would do this before running <code>maven
+    plugin:install</code> from the <code>src/maven-plugin</code> directory.
+    This will jar together the various plugin files copy it into your
+    <code>${maven.home}/plugins</code> directory.
   </p>
 
   <p>
-    For consistency you should also install the corresponding 
+    For consistency you should also install the corresponding
     generator and runtime jars in your local maven repository by running
-    <code>maven jar:install</code> from the <code>src/generator</code> 
+    <code>maven jar:install</code> from the <code>src/generator</code>
     and <code>src</code> directories respectively.
   </p>
 
@@ -109,8 +109,8 @@
 <section name="Configuration">
 
   <p>
-    The Torque Maven plugin is configured via properties defined in your 
-    project.properties file.  See the 
+    The Torque Maven plugin is configured via properties defined in your
+    project.properties file.  See the
     <a href="maven-plugin/properties.html">properties reference</a> for
     details on the various properties that can be configured.
   </p>
@@ -120,7 +120,7 @@
   <p>
     Instead of relying on the typical <code>build.properties</code>, the Maven
     plugin uses the project-wide settings in the <code>project.properties</code>
-    file.  
+    file.
   </p>
 
   <p>
@@ -130,7 +130,7 @@
   </p>
 
   <p>
-    
+
     Here is a sample configuration from <code>project.properties</code>:
 
 <source><![CDATA[
@@ -156,7 +156,7 @@
 ]]></source>
 
   </p>
-  
+
 </subsection>
 
 

Modified: db/torque/runtime/trunk/xdocs/mssql-howto.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/mssql-howto.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/mssql-howto.xml (original)
+++ db/torque/runtime/trunk/xdocs/mssql-howto.xml Wed Aug 24 05:38:09 2005
@@ -27,9 +27,9 @@
 
 <p>
 This HOWTO was written some time ago and was targeted at the
-version of Torque that was coupled with the 
+version of Torque that was coupled with the
 <a href="http://jakarta.apache.org/turbine/">Turbine</a> application framework.
-Contributions towards updating the information below can be submitted to the 
+Contributions towards updating the information below can be submitted to the
 <a href="mailto:torque-dev@db.apache.org">Torque Dev mailing list</a>.
 </p>
 
@@ -39,8 +39,8 @@
 
 <p>
 This howto contains configuration help on using MS SQL Server with Turbine.
-This Howto supplements the 
-<a href="http://jakarta.apache.org/turbine/tdk/tdk-howto.html">TDK Howto</a> 
+This Howto supplements the
+<a href="http://jakarta.apache.org/turbine/tdk/tdk-howto.html">TDK Howto</a>
 page.
 </p>
 
@@ -67,11 +67,11 @@
 <section name="JDBC Driver">
 <p>
 Microsoft has a JDBC driver for MS SQL Server available from their <a
-href="http://www.microsoft.com/sql/downloads/">SQL Downloads page</a>. 
-Alternately, a third party commercial driver from 
+href="http://www.microsoft.com/sql/downloads/">SQL Downloads page</a>.
+Alternately, a third party commercial driver from
 <a href="http://industry.java.sun.com/products/jdbc/drivers">JDBC(TM)
 Technology - Drivers</a>, the JDBC-ODBC bridge driver from Sun, or one of the
-free drivers, <a href="http://www.freetds.org">FreeTDS</a> or 
+free drivers, <a href="http://www.freetds.org">FreeTDS</a> or
 <a href="http://jtds.sourceforge.net/">jTDS</a> can be used.
 </p>
 
@@ -82,7 +82,7 @@
 </p>
 
 <p>
-We have only recently been informed of the existence of 
+We have only recently been informed of the existence of
 <a href="http://jtds.sourceforge.net/">jTDS</a>, which is based on FreeTDS.
 Try it out and let us know how it goes.
 </p>

Modified: db/torque/runtime/trunk/xdocs/oracle-howto.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/oracle-howto.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/oracle-howto.xml (original)
+++ db/torque/runtime/trunk/xdocs/oracle-howto.xml Wed Aug 24 05:38:09 2005
@@ -26,31 +26,31 @@
   <section name="Oracle Howto" >
 
     <p>
-      Saravana Kannan is maintaining a patched version of Village that 
-      supports Oracle LOBs: 
-      <a href="https://sweb.uky.edu/~skkann2/village/index.html">Village 2.0 
+      Saravana Kannan is maintaining a patched version of Village that
+      supports Oracle LOBs:
+      <a href="https://sweb.uky.edu/~skkann2/village/index.html">Village 2.0
       Patched for Oracle LOBs - For use with Torque 3.1 and later</a>
     </p>
-    
+
     <p>
-      The data type TIME only has day accuracy for Oracle. This is due to the 
-      underlying village library and the fact that oracle does not support 
+      The data type TIME only has day accuracy for Oracle. This is due to the
+      underlying village library and the fact that oracle does not support
       a SQL type TIME.
       If you are using Oracle 9i and later, you can use the type TIMESTAMP
       instead which gives you millisecond accuracy.
     </p>
-    
+
     <subsection name="Oracle versions">
       <p>
-        This version of Torque is optimized for Oracle 9i and later. 
+        This version of Torque is optimized for Oracle 9i and later.
         The following issues exist for older versions of Oracle:
       </p>
-     
+
       <p>
         The data type TIMESTAMP is not supported up to and including
-        Oracle 8.1.7. Either use the types DATE or TIME instead of TIMESTAMP 
-        or change the following line in the class 
-        org.apache.torque.engine.platform.PlatformOracleImpl 
+        Oracle 8.1.7. Either use the types DATE or TIME instead of TIMESTAMP
+        or change the following line in the class
+        org.apache.torque.engine.platform.PlatformOracleImpl
         in the generator source
       </p>
 
@@ -60,7 +60,7 @@
       <p>
         to
       </p>
-      
+
       <source>
 setSchemaDomainMapping(new Domain(SchemaType.TIMESTAMP, "DATE"));</source>
 
@@ -69,7 +69,7 @@
         However, both possibilities will give you only day accuracy for the
         data types DATE, TIME and TIMESTAMP
       </p>
-      
+
     </subsection>
 
   </section>
@@ -78,10 +78,10 @@
 <section name="Introductory note for the following sections">
 
 <p>
-The following part of this HOWTO was written some time ago and was 
-targeted at Oracle 8i and the version of Torque that was coupled with the 
+The following part of this HOWTO was written some time ago and was
+targeted at Oracle 8i and the version of Torque that was coupled with the
 <a href="http://jakarta.apache.org/turbine/">Turbine</a> application framework.
-Contributions towards updating the information below can be submitted to the 
+Contributions towards updating the information below can be submitted to the
 <a href="mailto:torque-dev@db.apache.org">Torque Dev mailing list</a>.
 </p>
 
@@ -92,7 +92,7 @@
 <p>
 This HOWTO aims to be a simple guide to make Turbine run with an existing
 Oracle 8i database. The process of making Turbine run is not covered in
-this guide, proceed to the 
+this guide, proceed to the
 <a href="http://jakarta.apache.org/turbine/">Turbine</a> site for
 help on how to install Turbine.
 </p>

Modified: db/torque/runtime/trunk/xdocs/peers-howto.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/peers-howto.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/peers-howto.xml (original)
+++ db/torque/runtime/trunk/xdocs/peers-howto.xml Wed Aug 24 05:38:09 2005
@@ -28,11 +28,11 @@
 <section name="Working With Peers">
 
 <p>
-Peers are an Object Relation mapping tool, built on top of 
+Peers are an Object Relation mapping tool, built on top of
 <a href="http://share.whichever.com/village/">Village</a> that gives
 you access to a relational database via Java objects.  Peers act on a somewhat
 lower level than other O-R mapping tools like
-<a href="http://www.castor.org/">Castor</a> or 
+<a href="http://www.castor.org/">Castor</a> or
 <a href="http://osage.sourceforge.net/">Osage</a>. This means that
 you have to do some coding by hand, but it allows for the most flexible
 solution.
@@ -137,7 +137,7 @@
 </p>
 
 <p>
-DatabaseMaps are constructed by classes called MapBuilders.  Torque 
+DatabaseMaps are constructed by classes called MapBuilders.  Torque
 generates MapBuilder classes for each of the tables in your schema.
 </p>
 </section>
@@ -226,7 +226,7 @@
 </p>
 
 <p>
-The ID Broker is used in the underlying Peer code.  After you have generated 
+The ID Broker is used in the underlying Peer code.  After you have generated
 your object model classes you need not worry about it anymore.
 </p>
 

Modified: db/torque/runtime/trunk/xdocs/postgres-howto.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/postgres-howto.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/postgres-howto.xml (original)
+++ db/torque/runtime/trunk/xdocs/postgres-howto.xml Wed Aug 24 05:38:09 2005
@@ -25,36 +25,36 @@
 
   <section name="PostgreSQL versions">
     <p>
-      The generator templates in Torque 3.2 are optimized for 
+      The generator templates in Torque 3.2 are optimized for
       PostgreSQL 7.3 and later.
       To use an older version of PostgreSQL, do the following:
     </p>
-    
+
     <p>
-      In the generator, locate the template 
-      templates/sql/base/postgresql/drop.vm 
+      In the generator, locate the template
+      templates/sql/base/postgresql/drop.vm
       and replace the line
     </p>
-    
+
     <source>
 DROP TABLE $table.Name CASCADE;</source>
-    
+
     <p>
       by
     </p>
-    
+
     <source>
 DROP TABLE $table.Name;</source>
-      
+
   </section>
 
 <section name="Note">
 
 <p>
-The following sections of this HOWTO were written some time ago 
-and were targeted at the version of Torque that was coupled with the 
+The following sections of this HOWTO were written some time ago
+and were targeted at the version of Torque that was coupled with the
 <a href="http://jakarta.apache.org/turbine/">Turbine</a> application framework.
-Contributions towards updating the information below can be submitted to the 
+Contributions towards updating the information below can be submitted to the
 <a href="mailto:torque-dev@db.apache.org">Torque Dev mailing list</a>.
 </p>
 

Modified: db/torque/runtime/trunk/xdocs/references.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/references.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/references.xml (original)
+++ db/torque/runtime/trunk/xdocs/references.xml Wed Aug 24 05:38:09 2005
@@ -56,9 +56,9 @@
       <ul>
         <li>
           <a href="http://www.devaki.org/">Devaki-Nextobjects</a>
-           Nextobjects is an Integrated Development Tool for Entreprise 
-           Applications. Nextobjects will help you choose database structure 
-           from system analysis and design, down to generating strongly designed 
+           Nextobjects is an Integrated Development Tool for Entreprise
+           Applications. Nextobjects will help you choose database structure
+           from system analysis and design, down to generating strongly designed
            data layer Object Model.
         </li>
       </ul>

Modified: db/torque/runtime/trunk/xdocs/release-changes.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/release-changes.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/release-changes.xml (original)
+++ db/torque/runtime/trunk/xdocs/release-changes.xml Wed Aug 24 05:38:09 2005
@@ -295,7 +295,7 @@
               </li>
               <li>
                 Added DOUBLE as a valid type for a column in a datamodel
-                descriptor. 
+                descriptor.
               </li>
               <li>
                 Fixed the TorqueDataDTDTask.

Modified: db/torque/runtime/trunk/xdocs/schema-howto.xml
URL: http://svn.apache.org/viewcvs/db/torque/runtime/trunk/xdocs/schema-howto.xml?rev=239636&r1=239635&r2=239636&view=diff
==============================================================================
--- db/torque/runtime/trunk/xdocs/schema-howto.xml (original)
+++ db/torque/runtime/trunk/xdocs/schema-howto.xml Wed Aug 24 05:38:09 2005
@@ -37,7 +37,7 @@
 Torque has some rudimentary support for Database schemas when
 accessing a database. Schema names can either be specified when
 generating classes via the generator, or they can be specified
-in the runtime. Note that specifying explicit schema names both at 
+in the runtime. Note that specifying explicit schema names both at
 generate time and at runtime is not tested and most likely causes problems.
 </p>
 
@@ -70,7 +70,7 @@
 
 <p>
 If no schema is configured in the torque properties, Torque will not
-qualify its table names. 
+qualify its table names.
 </p>
 
 </section>
@@ -91,7 +91,7 @@
 
 Torque.setSchema("bar", "foo");
 
-/* Reset the schema names (no longer qualify 
+/* Reset the schema names (no longer qualify
  * accesses to the tables of the "bar" datasource
  */
 Torque.setSchema("bar", null);
@@ -106,10 +106,10 @@
   <section name="Using Schema Names at generate time">
 
     <p>
-      To define the schema of a table in the schema.xml, use the 
-      fully qualified table name as name attribute in the &lt;table&gt; 
+      To define the schema of a table in the schema.xml, use the
+      fully qualified table name as name attribute in the &lt;table&gt;
       element of your schema.xml.
-      For example, to use the schema "bookstore" for the table "book", 
+      For example, to use the schema "bookstore" for the table "book",
       use the following table definition:
     </p>
 
@@ -121,9 +121,9 @@
     </source>
 
     <p>
-      If the standard naming method is used, the resulting 
-      java class will be named BookstoreBook. If you want to omit 
-      the schema name in the java name 
+      If the standard naming method is used, the resulting
+      java class will be named BookstoreBook. If you want to omit
+      the schema name in the java name
       (i.e. the resulting java class should be named "Book"),
       you can either use the javaName attribute of the table definition:
     </p>
@@ -136,7 +136,7 @@
     </source>
 
     <p>
-      or you can use the attribute 
+      or you can use the attribute
       defaultJavaNamingMethod="underscoreOmitSchema"
       in the database definition:
     </p>
@@ -149,13 +149,13 @@
       </source>
 
     <p>
-      Note that the defaultJavaNamingMethod attribute of a table 
-      will only affect the column names in the table and cannot 
+      Note that the defaultJavaNamingMethod attribute of a table
+      will only affect the column names in the table and cannot
       be used to change the name of the table itself.
     </p>
 
     <p>
-      If you use a sequence to autogenerate ids, the sequence will be generated in the same schema 
+      If you use a sequence to autogenerate ids, the sequence will be generated in the same schema
       as the table.
     </p>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message