package rename for test libraries.

[utils] / test / enterprise / src / site / xdoc / index.xml

diff --git a/test/enterprise/src/site/xdoc/index.xml b/test/enterprise/src/site/xdoc/index.xml
index 42e38bc85060373c5ca69ebec772406f25a19dc6..49f8f8dbc144b64346e526aa702616b3fa6c7184 100644 (file)
--- a/test/enterprise/src/site/xdoc/index.xml
+++ b/test/enterprise/src/site/xdoc/index.xml
@@ -11,9 +11,9 @@
     <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">JPA</a></li>
+        <li><a href="apidocs/org/wamblee/test/transactionspackage-summary.html">transactions</a></li>
+        <li><a href="apidocs/org/wamblee/test/jndi/package-summary.html">jndi</a></li>
+        <li><a href="apidocs/org/wamblee/test/persistence/package-summary.html">Persistence</a></li>
       </ul>
     </section>
 
@@ -31,7 +31,8 @@
         <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">