You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@deltaspike.apache.org by bu...@apache.org on 2013/05/28 22:07:02 UTC
svn commit: r863537 - in /websites/staging/deltaspike/trunk/content: ./
deltaspike/jpa.html
Author: buildbot
Date: Tue May 28 20:07:02 2013
New Revision: 863537
Log:
Staging update by buildbot for deltaspike
Modified:
websites/staging/deltaspike/trunk/content/ (props changed)
websites/staging/deltaspike/trunk/content/deltaspike/jpa.html
Propchange: websites/staging/deltaspike/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 28 20:07:02 2013
@@ -1 +1 @@
-1486427
+1487089
Modified: websites/staging/deltaspike/trunk/content/deltaspike/jpa.html
==============================================================================
--- websites/staging/deltaspike/trunk/content/deltaspike/jpa.html (original)
+++ websites/staging/deltaspike/trunk/content/deltaspike/jpa.html Tue May 28 20:07:02 2013
@@ -369,7 +369,7 @@ So it's possible to catch an exception i
<p>If you have multiple persistence-units and you have to use both transaction-types or the settings for development have to be different than the production settings, you can use <code>org.apache.deltaspike.jpa.impl.transaction.EnvironmentAwareTransactionStrategy</code> instead.</p>
<p><strong>Hint:</strong></p>
<p>In case of some versions of Weld (or OpenWebBeans in BDA mode), you have to configure it as global-alternative instead of an <code><alternatives></code> in beans.xml. That means you have to add e.g.:
-org.apache.deltaspike.jpa.spi.transaction.TransactionStrategy=org.apache.deltaspike.jpa.impl.transaction.BeanManagedUserTransactionStrategy
+<code>globalAlternatives.org.apache.deltaspike.jpa.spi.transaction.TransactionStrategy=org.apache.deltaspike.jpa.impl.transaction.BeanManagedUserTransactionStrategy</code>
to /META-INF/apache-deltaspike.properties</p>
</div>
</div>