Hibernate does something similar. They have their own internal transaction manager lookup classes for various platforms, and you can specify JNDI locations.
We should probably have something like this in the transaction module. On Wed, Nov 20, 2013 at 9:29 AM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > BTW to make some code on 2): https://gist.github.com/rmannibucau/7564089 > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > > > > 2013/11/20 Romain Manni-Bucau <rmannibu...@gmail.com>: >> Hi >> >> testing new mapping feature (really appreciated once >> SimpleQueryInOutMapperBase was added) I realized we still don't >> support @transactional on repos. >> >> What's blocking for it? Since we handle the impl we can add the >> transaction strategy handling. >> >> That said it rings 2 questions: >> 1) why don't we handle nested transactions? >> 2) why don't we have a TransactionStrategy backed by a transaction manager? >> 2') if 2) can't we support default locations like >> http://grepcode.com/file/repo1.maven.org/maven2/org.apache.openjpa/openjpa-all/2.1.0/org/apache/openjpa/ee/AutomaticManagedRuntime.java?av=f >> . This is great cause make it working with 0 config in a JavaEE >> server. >> >> wdyt? >> >> Romain Manni-Bucau >> Twitter: @rmannibucau >> Blog: http://rmannibucau.wordpress.com/ >> LinkedIn: http://fr.linkedin.com/in/rmannibucau >> Github: https://github.com/rmannibucau
