Author: tfischer
Date: Tue Apr 17 19:46:16 2012
New Revision: 1327242
URL: http://svn.apache.org/viewvc?rev=1327242&view=rev
Log:
TORQUE-139: create Totque3 -> Torque4 migration guide
Added:
db/torque/torque4/trunk/torque-site/src/site/xdoc/migration-from-torque-3.xml
Modified:
db/torque/torque4/trunk/torque-site/src/site/site.xml
Modified: db/torque/torque4/trunk/torque-site/src/site/site.xml
URL:
http://svn.apache.org/viewvc/db/torque/torque4/trunk/torque-site/src/site/site.xml?rev=1327242&r1=1327241&r2=1327242&view=diff
==============================================================================
--- db/torque/torque4/trunk/torque-site/src/site/site.xml (original)
+++ db/torque/torque4/trunk/torque-site/src/site/site.xml Tue Apr 17 19:46:16
2012
@@ -31,6 +31,7 @@
<menu name="General information">
<item name="Overview" href="/index.html"/>
<item name="News and Status" href="/status.html"/>
+ <item name="Migration from Torque 3"
href="/migration-from-torque-3.html"/>
<item name="Downloads" href="/download.html"/>
<item name="Addons" href="/addons.html"/>
<item name="Changes" href="/changes-report.html"/>
Added:
db/torque/torque4/trunk/torque-site/src/site/xdoc/migration-from-torque-3.xml
URL:
http://svn.apache.org/viewvc/db/torque/torque4/trunk/torque-site/src/site/xdoc/migration-from-torque-3.xml?rev=1327242&view=auto
==============================================================================
---
db/torque/torque4/trunk/torque-site/src/site/xdoc/migration-from-torque-3.xml
(added)
+++
db/torque/torque4/trunk/torque-site/src/site/xdoc/migration-from-torque-3.xml
Tue Apr 17 19:46:16 2012
@@ -0,0 +1,97 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<document>
+ <properties>
+ <title>Migration from Torque 3</title>
+ </properties>
+
+ <body>
+ <section name="Changes in Torque 4">
+ <p>
+ The most prominent changes in Torque 4 are:
+ </p>
+ <ul>
+ <li>
+ At least java 1.5 is now required.
+ </li>
+ <li>
+ The following databases are now officially supported:
+ MySQL, PostgreSQL, Derby, HSQLDB, Oracle MSSQL.
+ </li>
+ <li>
+ Column names are now stored in objects implementing
+ the org.apache.torque.Column interface. As the Peer column name
+ constants are generated accordingly, you only need to consider this
+ if you assemble column names from strings
+ (use org.apache.torque.ColumnImpl constructors to create Column
+ instances from Strings).
+ </li>
+ <li>
+ The org.apache.torque.util.Criteria object is now deprecated
+ and is replaced by a new implementation
+ org.apache.torque.criteria.Criteria. The old Criteria object has
+ the same semantics as the Torque 3.3 Criteria and is perfectly
+ functional, but will be removed in the future. The new Criteria
+ object differs from the old one in that it has a different semantics
+ in the "or" methods (check the javadoc) and treats Strings
+ in the first argument as Strings, not as column names
+ (e.g. criteria.and("string1", "string2") has a different meaning in
+ the old and the new Criteria).
+ </li>
+ <li>
+ Database views are now supported out-of-the-box.
+ </li>
+ <li>
+ The Torque generator is now a general-purpose code generator.
+ This has the effect that the templates used by the generator need to
be
+ specified. See the template docs, the maven2 plugin docs or
+ the tutorial on how to specify the torque templates for the generator.
+ See the generator docs for more details on how to use it
+ as code generator.
+ </li>
+ <li>
+ The Torque runtime does not use the village library any more.
+ </li>
+ <li>
+ Supplying "null" as value for a database connection now results in
+ an error in Torque 4. In Torque 3, Torque automatically opened
+ a database connection if a connection argument was null.
+ </li>
+ </ul>
+ <p>
+ There are many more improvements and bug fixes. See the
+ <a href="changes-report.html">changes report</a> for details.
+ </p>
+ </section>
+ <section name="Migrating from Torque 3 to Torque 4">
+ <p>
+ There are no big API Redesigns in Torque 4 as compared to Torque 3,
+ so migrating an existing application from Torque 3 to Torque 4 should
+ be possible without too much pain.
+ </p>
+ <p>
+ As a first migration step, check out the changes above to see whether
+ they affect your application. If yes, modify these parts.
+ </p>
+ <p>
+ Validate your database schema against the torque 4 xsd
+ (from the torque templates documentation).
+ If there are any validation errors, check the subtasks of the jira issue
+ <a href="https://issues.apache.org/jira/browse/TORQUE-126";
>TORQUE-126</a>
+ whether a matching change is reported there; if yes, modify your schema
+ accordingly. If in doubt, ask the users list.
+ </p>
+ <p>
+ Then, change your project's build system to use Torque 4 instead of
+ Torque 3. Then build your application. If your application compiles,
+ chances are that your application is ok.
+ </p>
+ <p>
+ Finally, test your application thoroughly. Though
+ Torque 4 looks and feels similar to Torque 3, many changes have been
+ made under the hood and perhaps your application depended on a
+ special implementation of a Torque feature.
+ </p>
+ </section>
+ </body>
+</document>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
