Please also understand its not limited to META-INF/apache-deltaspike.properties, but any other config source you may have at runtime.
On Sat, Aug 6, 2016 at 9:53 AM Romain Manni-Bucau <[email protected]> wrote: > Updated the website, let me know if it is not better. > > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://blog-rmannibucau.rhcloud.com> | Old Wordpress Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> | JavaEE Factory > <https://javaeefactory-rmannibucau.rhcloud.com> > > 2016-08-06 13:36 GMT+02:00 nicolasduminil < > [email protected]>: > > > I would propose the following: > > > > "In the case of some versions of Weld, including but not limited to Weld > > 1.1.36 which comes with JBoss EAP/Wildfly, or OpenWebBeans in BDA mode, > you > > have to configure it as a global alternative instead of an alternative in > > beans.xml. That means you have to add either > > > > globalAlternatives.org.apache.deltaspike.jpa.spi.transaction. > > TransactionStrategy > > > =org.apache.deltaspike.jpa.impl.transaction.BeanManagedUserTransactionStra > > tegy > > > > or > > > > globalAlternatives.org.apache.deltaspike.jpa.spi.transaction. > > TransactionStrategy > > > =org.apache.deltaspike.jpa.impl.transaction.ContainerManagedTransactionStr > > ategy > > > > depending on your BMT/CMT strategy, to the > > /META-INF/apache-deltaspike.properties file" > > > > > > > > -- > > View this message in context: http://apache-deltaspike- > > incubator-discussions.2316169.n4.nabble.com/A-JTA- > > EntityManager-cannot-use-getTransaction-tp4663224p4663238.html > > Sent from the Apache DeltaSpike Incubator Discussions mailing list > archive > > at Nabble.com. > > >
