db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jdo Wiki] Update of "TestRunner" by MichelleCaisse
Date Fri, 03 Jun 2005 15:50:54 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jdo Wiki" for change notification.

The following page has been changed by MichelleCaisse:

  There may be multiple orm and xml files for a single persistence capable (pc) class or package.
 These are distinguished by different mapping designators in their filenames.  For example,
a given test configuration may run a set of tests on databases derby and mysql with mapping
4.  The mapping metadata files are package-derby4.orm and package-mysql4.orm; the test data
files are package-derby4.xml and package-mysql4.xml. The orm, jdo, xml, and class files are
in the same package in the jar file.
+ Currently, the class directory tree is deleted after the jar files are created.  However,
doing so obviates the benefit of making packaging a separate goal, because the classes would
have to be re-enhanced every time repackaging is required.  Not doing so, on the other hand,
obviates the need to package the files into jar files.  Why not just put the classes tree
with metadata and test files on the classpath.  To summarize, these are the three choices:
+  1. Package and delete the class tree.  Re-enhance whenever repackaging is required.
+  1. Package and don't delete the class tree.  If the classes and jdo metadata are up to
date, re-enhancement is not required before repackaging. The class tree is redundant with
the jar files.
+  1. Don't package and don't delete the class tree.  Provide the class tree on the classpath.
  == Identity Type ==
  (See question 3 in the Configuration Files section.)

View raw message