Refactor transaction logic -------------------------- Key: JBCACHE-1394 URL: https://jira.jboss.org/jira/browse/JBCACHE-1394 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: Transactions Reporter: Manik Surtani Assignee: Mircea Markus Fix For: 3.1.0 There are some redundancies here, which need tidying up. Specifically: 1. Redundant behaviour between TxInterceptor and InvocationContextInterceptor. ICI should *just* be in change of setting up and clearing down contexts. TxI should start implicit txs if needed, register syncs, handle remote prepares, commits and rollbacks, etc. 2. InvocationContext and TransactionContext has some redundanceis which can be cleaned up and optimised. 3. TransactionTable has an unnecessary number of Maps - these can be improved. It basically needs to be able to look up a Transaction and TransactionContext given a GlobalTransaction (for remote transactions coming in), as well as look up a GlobalTransaction and a TransactionContext given a Transaction (local transactions, retrieved from the TransactionManager). It is probably best to wait for Optimistic and Pessimistic Locking to be removed before this since a lot of this is legacy support code. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira