[jira] Commented: (GERONIMO-2277) Remove TransactionContextManager

2006-08-08 Thread David Jencks (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2277?page=comments#action_12426447
 ] 

David Jencks commented on GERONIMO-2277:


I've carefully studied the changes, merged notcm to trunk, and checked that the 
notcm branch works.

+1

 Remove TransactionContextManager
 

 Key: GERONIMO-2277
 URL: http://issues.apache.org/jira/browse/GERONIMO-2277
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: transaction manager
Reporter: Dain Sundstrom
 Assigned To: Dain Sundstrom
 Fix For: 1.2

 Attachments: GERONIMO-2277.patch


 If you use the  Geronimo TransactionContextManager,  you can't use the 
 TransactionManager interface directly since the TCM needs to know about all 
 TM calls.  Additionally, to use the TCM you must demarcate all changes in 
 component context by starting an unspecified transaction context.  This is 
 all quite invasive and makes it hard to use our code in third part 
 environments such as Spring or plain old Tomcat.
 I propose we remove the TransactionContextManager and replaced all uses with 
 a plain old TransactionManager.  This will also allow us to removed all code 
 from web containers, app client and timer that was simply demarcating an 
 unspecified transaction context, which is no longer needed.  

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (GERONIMO-2277) Remove TransactionContextManager

2006-08-08 Thread Matt Hogstrom (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2277?page=comments#action_12426788
 ] 

Matt Hogstrom commented on GERONIMO-2277:
-

I've looked at the merge and concur

+1

 Remove TransactionContextManager
 

 Key: GERONIMO-2277
 URL: http://issues.apache.org/jira/browse/GERONIMO-2277
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: transaction manager
Reporter: Dain Sundstrom
 Assigned To: Dain Sundstrom
 Fix For: 1.2

 Attachments: GERONIMO-2277.patch


 If you use the  Geronimo TransactionContextManager,  you can't use the 
 TransactionManager interface directly since the TCM needs to know about all 
 TM calls.  Additionally, to use the TCM you must demarcate all changes in 
 component context by starting an unspecified transaction context.  This is 
 all quite invasive and makes it hard to use our code in third part 
 environments such as Spring or plain old Tomcat.
 I propose we remove the TransactionContextManager and replaced all uses with 
 a plain old TransactionManager.  This will also allow us to removed all code 
 from web containers, app client and timer that was simply demarcating an 
 unspecified transaction context, which is no longer needed.  

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[jira] Commented: (GERONIMO-2277) Remove TransactionContextManager

2006-08-07 Thread Jeff Genender (JIRA)
[ 
http://issues.apache.org/jira/browse/GERONIMO-2277?page=comments#action_12426253
 ] 

Jeff Genender commented on GERONIMO-2277:
-

+1...this will be good to have.

 Remove TransactionContextManager
 

 Key: GERONIMO-2277
 URL: http://issues.apache.org/jira/browse/GERONIMO-2277
 Project: Geronimo
  Issue Type: Improvement
  Security Level: public(Regular issues) 
  Components: transaction manager
Reporter: Dain Sundstrom
 Assigned To: Dain Sundstrom
 Fix For: 1.2

 Attachments: GERONIMO-2277.patch


 If you use the  Geronimo TransactionContextManager,  you can't use the 
 TransactionManager interface directly since the TCM needs to know about all 
 TM calls.  Additionally, to use the TCM you must demarcate all changes in 
 component context by starting an unspecified transaction context.  This is 
 all quite invasive and makes it hard to use our code in third part 
 environments such as Spring or plain old Tomcat.
 I propose we remove the TransactionContextManager and replaced all uses with 
 a plain old TransactionManager.  This will also allow us to removed all code 
 from web containers, app client and timer that was simply demarcating an 
 unspecified transaction context, which is no longer needed.  

-- 
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira