The following comment has been added to this issue:
Author: David Jencks
Created: Tue, 5 Oct 2004 12:04 AM
Body:
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 class.
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/GERONIMO-352?page=comments#action_53702
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/GERONIMO-352
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
Components:
connector
Versions:
1.0-M2
Assignee: David Jencks
Reporter: David Jencks
Created: Sun, 3 Oct 2004 10:08 AM
Updated: Tue, 5 Oct 2004 12:04 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
