I try explain the case. We know that OAK doesnt'support Transaction, so the following should be the JCR implementation:
http://www.day.com/specs/jcr/2.0/10_Writing.html [cid:image003.jpg@01D19996.DE408710] When i use session write-methods, i can execute a sequence of session methods (example add nodes) but only when i use save method i persist the changes. Instead when i use Workspace-Write Methods (example VersionManager.checkin, checkout, checkpoint, restore, restoreByLabel, merge, cancelMerge, doneMerge, createActivity , removeActivity and createConfiguration), for each action i persist on the workspace. So, imagine a use case in which i must create a version of a document and save it in my repository in atomic way; if the first phase works but the second one is KO, we have inconsistent data: the document has a new version but is not saved. Which kind of workaround do you suggest to solve this problem ? Thanks in advance, best regards -----Messaggio originale----- Da: Julian Reschke [mailto:julian.resc...@gmx.de] Inviato: giovedì 14 aprile 2016 18:05 A: oak-dev@jackrabbit.apache.org Cc: Diquigiovanni Simone <simone.diquigiova...@siav.it>; Morelli Alessandra <alessandra.more...@siav.it> Oggetto: Re: critical question about oak: RDBMS and distributed transaction On 2016-04-14 17:24, Ancona Francesco wrote: > Hi, > > thanks for rdbms help. I managed to run my application also with > postgres and Oracle. My wrong has been that default installation > doesn't work; we need to set another collation. (in detail collation > C) > > Can i suggest to add these details to the documentation ? The only documentation right now is in RDBDocumentStore's javadoc, and that does mention it. > Now we have an other problem. > > We found that distributed transactions are not supported in OAK. This > could be a problem when we need to aggregate different kind of > services (our database and ecm services): so our data could be not > choerent in specific situations. > > Besides we noticed that there is a major issue opened in 2013 but not > closed. Specifically? > So i point out 3 question > > 1.Is there a roadmap or an indicative date to solve this issue? > > 2.Which kind of workaround do you suggest to solve the problem now ? > > 3.Do you know if adobe oak built-in product has implemented the > distributed transactions ? AFAIU, Oak wasn't designed with distributed transactions in mind, nor is it currently used that way. I'm not aware of any plans to change that... Best regards, Julian ************************************************************************************ This footnote confirms that this email message has been scanned by PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses. ************************************************************************************
