AFAIK, the save to the workspace is transactional as long as underlying DB and connection is XA capable. However, JR doesn't use or expose distributed XA so you can't add more resources to the transaction. You would need to write your own PM to expose transaction manager and modify the scope of transaction.
Do you know if it's already transactional if simply the driver/connection supports it or is there some property to set to enable transactional behaviour? I honestly don't like the idea of writing my own persistence manager, if I want to do thing right testing would be really heavy, and also I don't like the idea of touching a core component that I don't fully know.
As for simulating distributed transactions, yes, using version store to backup your content is what I would do. Make sure to set the rules correctly otherwise you might end up versioning whole site when you try to backup the home page.
Uhm... given the situation, as a first shot I'd like to try and see if I can leave everything without this extra complexity. Now I'm just wondering what happens without the enterprise soft locking module... If there is a concurrent edit, is there an exception or simply the latest win and overwrites everything?
Regards, Danilo. ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
