<section name="Introduction">
<p>Several utilities are provide for Java EE testing: </p>
<ul>
- <li><a href="apidocs/org/wamblee/support/package-summary.html">Basic Support</a></li>
- <li><a href="apidocs/org/wamblee/support/jndi/package-summary.html">JNDI</a></li>
- <li><a href="apidocs/org/wamblee/support/persistence/package-summary.html">Persistence</a></li>
+ <li><a href="apidocs/org/wamblee/test/inject/package-summary.html">inject</a>: general
+ dependency injection in unit test. </li>
+ <li><a href="apidocs/org/wamblee/test/cdi/package-summary.html">cdi</a>: CDI dependency
+ injection in unit test. </li>
+ <li><a href="apidocs/org/wamblee/test/transactions/package-summary.html">transactions</a>:
+ Transaction support in unit test. </li>
+ <li><a href="apidocs/org/wamblee/test/jndi/package-summary.html">jndi</a>: JNDI support in
+ unit test.</li>
+ <li><a href="apidocs/org/wamblee/test/persistence/package-summary.html">persistence</a>: JPA
+ support in unit test. </li>
</ul>
</section>
<li>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). </li>
- <li>You also want to define your own specific JPA version. </li>
+ <li>The specific JPA implementation and version to use <em>must</em> be determined by you
+ and not by the test support library. </li>
</ul>
-
+
<subsection name="The general JPA test support library">
<p>Always include the dependency below: </p>
<table>
</tr>
</table>
</subsection>
-
+
<subsection name="JPA implementation-specific library">
<p>Choose one from the choices below: </p>
<table>
<tr>
<td>Toplink</td>
<td>org.wamblee</td>
- <td>wamblee-test-toplink</td>
+ <td>wamblee-test-toplink-essentials</td>
</tr>
<tr>
<td>Hibernate (from 3.4.0.GA and higher).</td>