Ok, here we go: (JPA 2.0 spec) 8.2.1.5 jta-data-source, non-jta-data-source In Java EE environments, the jta-data-source and non-jta-data-source elements are used to specify the global JNDI name of the JTA and/or non-JTA data source to be used by the persistence provider. If neither is specified, the deployer must specify a JTA data source at deployment or a JTA data source must be provided by the container, and a JTA EntityManagerFactory will be created to correspond to it.
Romain Manni-Bucau @rmannibucau http://www.tomitribe.com http://rmannibucau.wordpress.com https://github.com/rmannibucau 2014-11-22 11:13 GMT+01:00 hwaastad <[email protected]>: > HI, > I know, but I did'nt see why it was necessary, using RESOURCE_LOCAL.... > > I've been using eclipselink (and jta) 2.5.x with tomee all the way and I've > never had any issues with it. (even in high load production apps either). > > I'll go on with my nosql PU and see if I need a jta source there aswell. > > I'll keep you all posted :-) > > br hw > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/tomee-eclipselink-and-polygot-persistence-tp4672983p4672993.html > Sent from the TomEE Users mailing list archive at Nabble.com.
