svn commit: r855829 - in /websites/staging/deltaspike/trunk/content: ./ deltaspike/jpa.html

[bu...@apache.org]

Author: buildbot
Date: Mon Mar 25 01:05:33 2013
New Revision: 855829

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 Mon Mar 25 01:05:33 2013
@@ -1 +1 @@
-1460498
+1460499

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 Mon Mar 25 01:05:33 2013
@@ -357,6 +357,10 @@ 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. That means you have to add e.g.:
+org.apache.deltaspike.jpa.spi.transaction.TransactionStrategy=org.apache.deltaspike.jpa.impl.transaction.EnvironmentAwareTransactionStrategy
+to /META-INF/apache-deltaspike.properties</p>
           </div>
       </div>