Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Message-ID: <20348829.1182951087187.JavaMail.jira@brutus>
Date: Wed, 27 Jun 2007 06:31:27 -0700 (PDT)
From: "Kevin Sutter (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Subject: [jira] Commented: (OPENJPA-61) Missing usage of
 TransactionSynchronizationRegistry
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kevin Sutter commented on OPENJPA-61:
-------------------------------------

Patrick, I agree with that idea.  That was exactly along the lines of my thinking, but I needed to get the first step done first -- get the TSR available.  Our "hack" for utilizing the WebSphere JTAExtendedTransaction interface wasn't cutting it and the TSR implementation that Marc provided got us around a couple of the problems.  So, I wanted to get a portion of the fix integrated.  Since the original problem as documented was resolved, I will create a new Issue to cover this additional "out of transaction" work request.  Sound okay?

> 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.