Remove Akka-specific transaction class
Refactor STM so that the Akka-specific transaction class is not needed. See if the persistent storage data structures and the JTA integration can hook straight into the Multiverse transaction lifecycle listeners.
Leave a comment
Peter Veentjer: "I don't think that the Akka transactions need to be removed. But instead of relying on akka to wrap a transaction around something, injecting some kind of callback interface that sets up/tears down non multiverse datastructures would be a better approach than the current approach."
Coming in the 0.7 release of Multiverse.
Also, the Akka transactions can be disabled (if persistence storage and JTA are not used) by passing hooks = false option to TransactionFactory.
Coming in the 0.7 release of Multiverse.
Also, the Akka transactions can be disabled (if persistence storage and JTA are not used) by passing hooks = false option to TransactionFactory.