From 1b47f6e6f8f3a2a097342c75cefad190e722ad40 Mon Sep 17 00:00:00 2001 From: erik Date: Tue, 6 Jul 2010 20:21:15 +0000 Subject: [PATCH] corrections to documentation. ` --- .../support/persistence/package-info.java | 19 ++++++++++++------- test/enterprise/src/site/xdoc/index.xml | 3 ++- 2 files changed, 14 insertions(+), 8 deletions(-) diff --git a/test/enterprise/src/main/java/org/wamblee/support/persistence/package-info.java b/test/enterprise/src/main/java/org/wamblee/support/persistence/package-info.java index 1ea78e25..979dde6f 100644 --- a/test/enterprise/src/main/java/org/wamblee/support/persistence/package-info.java +++ b/test/enterprise/src/main/java/org/wamblee/support/persistence/package-info.java @@ -42,7 +42,7 @@ * * *

- * See the design overview for a an overview of the design. + * See also the design overview. *

* * @@ -53,9 +53,13 @@ * Database db = DatabaseBuilder.getDatabase(); * DataSource dataSource = db.start(); * + *

* If nothing is specified in the user's environment, an inmemory database is started (derby). - * Using the datasource is just standard JDBC now. - * Stopping the database + * Using the datasource is just standard JDBC now. + *

+ *

+ * After a test it is good practice to stop the database: + *

* 
  *      db.stop();
  *
@@ -75,7 +79,7 @@ *

* However, the most convenient way to set the capabilities is usually to set a system property or environment * variable see the javadocs of {@link DatabaseBuilder}. and - * specifically {@link DatabaseBuilder#DB_CAPABILITIES_PROP} + * specifically DatabaseBuilder.DB_CAPABILITIES_PROP *

* * @@ -105,7 +109,8 @@ *

Using DB Unit in your tests

* * - *

To work with DBUnit, {@link DatabaseUtils#createDbTester(org.dbunit.dataset.filter.ITableFilterSimple)} + *

To work with DBUnit, + * DatabaseUtils#createDbTester(org.dbunit.dataset.filter.ITableFilterSimple) * must be used passing it in the tables to use in the form of a {@link org.dbunit.dataset.filter.ITableFilterSimple} * object.

* @@ -129,7 +134,7 @@ * want to test. *

*

Second step is to make sure that all entities are listed explicitly in your - * 

persistence.xml
. Currently, class path scanning appears to fail when + * persistence.xml. Currently, class path scanning appears to fail when * run from junit. * Specifying all entities explicitly is not necessarily a bad thing as it is also more efficient. *

@@ -168,8 +173,8 @@ * get them directly from the JPATester after initializing it: * 
  *      builder = jpaTester.getJpaBuilder();
- *      dbtester = jpaTester.getDbUtils().createDbTester(new MyTables());
  *      dbutils = jpaTester.getDbUtils();
+ *      dbtester = dbutils.createDbTester(new MyTables());
  *
* * diff --git a/test/enterprise/src/site/xdoc/index.xml b/test/enterprise/src/site/xdoc/index.xml index 429c8ea3..8f58bf4f 100644 --- a/test/enterprise/src/site/xdoc/index.xml +++ b/test/enterprise/src/site/xdoc/index.xml @@ -31,7 +31,8 @@
  • Different JPA providers can, in general, not be used within the same application. (an exception is of course an OSGI environment when JPA is used as per the OSGI enterprise spec).
    • -
  • You also want to define your own specific JPA version.
    • +
  • The specific JPA implementation and version to use must be determined by you + and not by the test support library.
    • -- 2.31.1