The original intent was to move all the jta stuff in an own module which would then automatically enable the JtaPersistenceStrategy.
But we actually have a 3rd option: Create an AutodetectPersitenceStrategy and make this the default. It could lookup the one to take via configuration. That way a user could override according to his intention. LieGrue, strub ----- Original Message ----- > From: Arne Limburg <[email protected]> > To: "[email protected]" > <[email protected]> > Cc: > Sent: Thursday, July 5, 2012 11:03 AM > Subject: [DISCUSS] [DELTASPIKE-175] [DELTASPIKE-219] @Transactional > > Hi, > > yesterday I startet working on the JTA support for @Transactional. > My current approach is to implement a JtaPersistenceStrategy. > However that leads me to the problem: Who decides which PersistenceStrategy > should be taken and how should this decision be made? > I have three suggestions: > > 1. We detect, if a UserTransaction is available, if so, the > JtaPersistenceStrategy is taken, otherwise the > ResourceLocalPersistenceStrategy > is taken. > > 2. We detect, if the involved persistence units use JTA or > RESOURCE_LOCAL > (which would lead to another question: Would we like to support, that > @Transactional mixes both strategies?) and decide from that information > > 3. We let the user decide by making one (or both) persistence strategies > @Alternatives > What do you think? > > Cheers, > Arne >
