geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (GERONIMO-352) TransactionContext is not associated with imported transactions
Date Tue, 05 Oct 2004 07:06:33 GMT
The following comment has been added to this issue:

     Author: David Jencks
    Created: Tue, 5 Oct 2004 12:04 AM
This is fixed, but an additional refactoring and simplification is possible, namely to create
a new ImportedTransactionContext class that includes the info in the inner TransactionContextManager.ImportedTransactionInfo
View this comment:

View the issue:

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

     Status: Open
   Priority: Major

    Project: Apache Geronimo

   Assignee: David Jencks
   Reporter: David Jencks

    Created: Sun, 3 Oct 2004 10:08 AM
    Updated: Tue, 5 Oct 2004 12:04 AM

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