Author: buildbot
Date: Tue Jun 30 20:32:31 2015
New Revision: 956450
Log:
Staging update by buildbot for deltaspike
Modified:
websites/staging/deltaspike/trunk/content/ (props changed)
websites/staging/deltaspike/trunk/content/documentation/data.html
Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Jun 30 20:32:31 2015
@@ -1 +1 @@
-1688515
+1688516
Modified: websites/staging/deltaspike/trunk/content/documentation/data.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/documentation/data.html (original)
+++ websites/staging/deltaspike/trunk/content/documentation/data.html Tue Jun
30 20:32:31 2015
@@ -1243,7 +1243,7 @@ annotations, the <code>singleResult</cod
from the <code>EntityRepository</code>, the repository will figure out if a
transaction is needed or not, and if so, if there is already one
ongoing. The Data module uses the <code>TransactionStrategy</code> provided by
the
-<a href="http://deltaspike.apache.org/jpa";>JPA Module</a> for this. See the JPA
+<a href="http://deltaspike.apache.org/documentation/jpa.html";>JPA Module</a>
for this. See the JPA
module documentation for more details.</p>
</div>
<div class="admonitionblock important">
