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.
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. HTH, Jan On Jun 19, 2011, at 7:09 PM, Danilo Ghirardelli wrote: > > Hello everyone, > Maybe it's already documented but I haven't found anything useful in google. > Is there any transaction manager in Magnolia or Jackrabbit? How does it work? > I have a custom control that saves its data in a couple of different point > (different repos), and I was wondering what happens if saving in a single > repo fails. If the save in the first repo is ok and the second fails for some > reason (concurrency or whatever), the data in the first repo would be altered > anyway? > I'm pretty sure there is "OpenSessionInView"-like mechanism that opens a > jackrabbit session for each request, just like the spring-hibernate one, but > I don't know if this has something that would do commit/rollback at the end > of the request or if any operation is just immediately effective. If this is > the case, I suppose the only way to have (or at least simulate) > transactionality would be to version all repos and go boack in versions as > "rollback". Or am I missing something? > Or simply these kind of problems are specific of relational databases and > does not apply to Jackrabbit? Thank you for any info. > > Regards, Danilo. > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
