Interesting. I knew about the "backdoor" approach for accessing the various Transaction Managers, but I thought OpenJPA would have had the new TransactionSynchronizationRegistry as well. I will open a JIRA report to address this issue.
Kevin On 9/27/06, Marc Prud'hommeaux <[EMAIL PROTECTED]> wrote:
David- We don't use TransactionSynchronizationRegistry (not yet, at least). Instead, we manually locate the TransactionManager via appserver- specific heuristics defined in openjpa-kernel/src/main/java/org/ apache/openjpa/ee/AutomaticManagedRuntime.java If the Geronimo TransactionManager is accessible from JNDI or some method invocation, you can just add it into AutomaticManagedRuntime as a default (you can test it out by specifying the "openjpa.ManagedRuntime" property to "jndi (TransactionManagerName=java:/GeronimoJNDINameForTransactionManager)". We may add support for integration via TransactionSynchronizationRegistry in the future, but the fact that it doesn't provide support for accessing the current Transaction would mean that we would need to rework some OpenJPA internals. On Sep 27, 2006, at 10:39 AM, David Jencks wrote: > I'm trying to get openjpa running in geronimo and wonder how > openjpa locates the TransactionSynchronizationRegistry. Greping > for TransactionSynchronizationRegistry I don't see it used anywhere > in the code base. What am I missing? > > thanks > david jencks >
