You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by de...@geronimo.apache.org on 2004/10/03 19:08:32 UTC

[jira] Created: (GERONIMO-352) TransactionContext is not associated with imported transactions

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
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: Unassigned
   Priority: Major

    Project: Apache Geronimo
 Components: 
             connector
   Versions:
             1.0-M2

   Assignee: 
   Reporter: David Jencks

    Created: Sun, 3 Oct 2004 10:08 AM
    Updated: Sun, 3 Oct 2004 10:08 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

[jira] Commented: (GERONIMO-352) TransactionContext is not associated with imported transactions

Posted by de...@geronimo.apache.org.
The following comment has been added to this issue:

     Author: David Jencks
    Created: Sun, 3 Oct 2004 10:52 AM
       Body:
In addition, the XATerminator interface should be exposed by the TransactionContextManager for the same reasons.
---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/GERONIMO-352?page=comments#action_53646

---------------------------------------------------------------------
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: Sun, 3 Oct 2004 10:52 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

[jira] Commented: (GERONIMO-352) TransactionContext is not associated with imported transactions

Posted by de...@geronimo.apache.org.
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

[jira] Closed: (GERONIMO-352) TransactionContext is not associated with imported transactions

Posted by de...@geronimo.apache.org.
Message:

   The following issue has been closed.

---------------------------------------------------------------------
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: Closed
   Priority: Major
 Resolution: FIXED

    Project: Apache Geronimo
 Components: 
             connector
   Fix Fors:
             1.0-M3
   Versions:
             1.0-M2

   Assignee: David Jencks
   Reporter: David Jencks

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

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

[jira] Closed: (GERONIMO-352) TransactionContext is not associated with imported transactions

Posted by de...@geronimo.apache.org.
Message:

   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:
  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: Closed
   Priority: Major
 Resolution: FIXED

    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, 19 Oct 2004 2:21 PM

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

[jira] Reopened: (GERONIMO-352) TransactionContext is not associated with imported transactions

Posted by de...@geronimo.apache.org.
Message:

   The following issue has been reopened.

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

forgot the resolved in part
---------------------------------------------------------------------
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: Reopened
   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, 19 Oct 2004 2:21 PM

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