Thomas Fromm created ISPN-1862: ---------------------------------- Summary: fire TransactionCompletedEvent not as part of the transaction Key: ISPN-1862 URL: https://issues.jboss.org/browse/ISPN-1862 Project: Infinispan Issue Type: Enhancement Components: Core API Affects Versions: 5.1.1.FINAL Reporter: Thomas Fromm Assignee: Manik Surtani When catching TransactionCompletedEvent I would expect, the transaction is committed, especially when isTransactionSuccessful() == true. I need to perform some operations after a transaction was completed. My workaround is ATM to suspend the transaction, perform my (async) stuff, and resume it afterwards. But in case of errors after resume, I get another TransactionCompletedEvent for this transaction with isTransactionSuccessful() == false. You see, I need something like a TransactionReallyCompletedEvent :-) My change request is, that the TransactionCompletedEvents should be fired, after the transaction was committed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira