Isis automatically wraps each action (or interaction) in a transaction; so all changes made will be done atomically.
That's either a good thing or a bad thing. It's a good thing in that it "just works". It's a bad thing in that, if you wanted to divide your action into separate transactions, well, you can't. The only control we give you is to "flush" any pending changes, using DomainObjectContainer.flush(). That said, we do this automatically in any repository queries, so even then you can probably ignore it. I can think of ways of getting more control than that (eg publishing an event and using the scheduler service to consume it asynchronously), but would probably qualify as over- engineering. HTH Dan On 20 July 2013 02:14, Okwui <[email protected]> wrote: > I am trying to implement a business system. I want to be able to make a > set of changes to different entities which will either succeed or fail > together. Is there a way to manage transactions?
