openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-61) Missing usage of TransactionSynchronizationRegistry
Date Wed, 27 Jun 2007 12:11:25 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508521
] 

Patrick Linskey commented on OPENJPA-61:
----------------------------------------

I don't think that we want this to necessarily be the default ManagedRuntime implementation,
since the TSR does not provide any support for executing work in a separate transaction. This
behavior is required for sequence maintenance in some scenarios.

Maybe we should change our ManagedRuntime interface to get rid of the begin() / commit() etc.
APIs, and add a new interface for executing a Runnable in a different transaction. This would
allow us to use the TSR ManagedRuntime for general use, and just plug in different ways of
performing out-of-transaction work.

Thoughts?

> Missing usage of TransactionSynchronizationRegistry
> ---------------------------------------------------
>
>                 Key: OPENJPA-61
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-61
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>            Reporter: Kevin Sutter
>            Assignee: Kevin Sutter
>             Fix For: 1.0.0
>
>         Attachments: OPENJPA-61.patch
>
>
> A discussion on the dev mailing list indicates that OpenJPA currently does not utilize
the TransactionSynchronizationRegistry.  Although OpenJPA does provide other means of finding
and accessing the various TransactionManagers, we should update OpenJPA to use the standard
interfaces.  Following are the two notes on this subject...
> ========================================================================================
	
> o  David Jencks 	<david_jencks@yahoo.com> to open-jpa-dev 	 More options	  Sep
27 (19 hours ago)
> I'm trying to get openjpa running in geronimo and wonder how openjpa
> locates the TransactionSynchronizationRegistry.  Grep'ing for
> TransactionSynchronizationRegistry I don't see it used anywhere in
> the code base.  What am I missing?
> thanks
> david jencks
> ========================================================================================
> o  Marc Prud'hommeaux 	to open-jpa-dev	 More options	  Sep 27 (19 hours ago)
> 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.
> ========================================================================================

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message