geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Closed: (GERONIMO-352) TransactionContext is not associated with imported transactions
Date Tue, 19 Oct 2004 21:21:52 GMT

   The following issue has been closed.

   Resolver: David Jencks
       Date: Tue, 19 Oct 2004 2:21 PM

simplification done some time ago.
View the issue:

Here is an overview of the issue:
        Key: GERONIMO-352
    Summary: TransactionContext is not associated with imported transactions
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Apache Geronimo

   Assignee: David Jencks
   Reporter: David Jencks

    Created: Sun, 3 Oct 2004 10:08 AM
    Updated: Tue, 19 Oct 2004 2:21 PM

The WorkManager starts and ends imported transactions by directly interacting with the XAWork
interface, implemented by the TransactionManagerProxy.  Whether or not there is a TransactionContext
associated with this transaction, it won't be repeatedly associated with the multiple calls
in the same transaction, thus losing ejb caching/dirty info etc.  

Solution: the tx import interfaces should be moved out into TransactionContextManager.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message