Hi, Still on Jackrabbit atm. but would like to move to Oak at some point. (Have been avoiding using features that are not included on Oak as much as possible)
We are also using (shallow) open scoped locks to prevent various concurrency issues (protect id counters and as part of our optimistic locking of content), it would be good to have some sort of locking mechanism (preferably at node level) in the toolbox when moving to Oak. -- Best Regards Chris On Mon, Sep 9, 2019 at 3:23 PM Julian Reschke <julian.resc...@gmx.de> wrote: > On 08.09.2019 22:52, Søren Jensen wrote: > > Hi > > > > I see through OAK-6421 that locking is being phased out and is > > currently deprecated. Since the Jira issue currently has the fix > > version set for the next stable release, I have some questions for > > this. > > > > For our current setup, we have a non-distributed application in which > > users may reserve documents and folders of documents for long periods > > of time. Currently, we represent this through locks, such that any > > invalid attempts at modifying a resource reversed by somebody else > > results in a LockExpection. Furthermore, for reserving folders (and > > underlying contents) we make use of deep locks. > > Are you aware that in Oak, these modifications actually are not > prohibited by locks? > > (That's the reason it's deprecated; it doesn't work as advertised...) > > > ... > > Best regards, Julian >
