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 Fri, 20 Oct 2006 16:45:35 GMT
    [ http://issues.apache.org/jira/browse/OPENJPA-61?page=comments#action_12443894 ] 
            
Patrick Linskey commented on OPENJPA-61:
----------------------------------------

I'd say that we (OpenJPA) should not worry about the older versions -- we (BEA) will just
need to add the appropriate logic in Kodo to handle the older versions of WebSphere.

> Missing usage of TransactionSynchronizationRegistry
> ---------------------------------------------------
>
>                 Key: OPENJPA-61
>                 URL: http://issues.apache.org/jira/browse/OPENJPA-61
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>            Reporter: Kevin Sutter
>         Assigned To: Kevin Sutter
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message