* </li>
* <li> <a href="#db-jpa-services">Testing a service that requires a transaction</a>
* </li>
+ * <li> <a href="#db-user-transaction">Controlling transactions through a <code>UserTransaction</code></a>
+ * </li>
* </ul>
*
* <p>
* });
* </pre>
*
+ * <p>
+ * Note that in addition to this method it is also possible to directly control transactions
+ * through {@link JpaBuilder#begin()}, {@link JpaBuilder#commit(javax.persistence.EntityManager)},
+ * and {@link JpaBuilder#rollback(javax.persistence.EntityManager)}.
+ * </p>
+ *
* <a name="db-jpa-plus-jdbc">
* <h2>JPA testing combined with JDBC and DBUnit</h2>
* </a>
* is in fact a so-called contextual reference.
* Next, the proxy is obtained from the factory. Invoking any method on it will make sure a new
* transaction is started and a new entity manager is created for the scope of that transaction.
- * </p>
+ * </p>
+ *
+ * <a name="db-user-transaction">
+ * <h2>Controlling transactions through a <code>UserTransaction</h2>
+ * </a>
+ *
+ * <p>
+ * It is also possible to manage JPA transaction through a <code>UserTransaction</code>.
+ * This is mostly useful if you are test software that uses <code>UserTransaction</code> for
+ * managing transactions, or if you want to manage multiple transactional resources.
+ * See the explanation at {@link org.wamblee.test.transactions.SimpleTransactionManager} for more details.
+ * </p>
*
* <a name="design-overview">
* <h2>Design overview</h2>