Hi and thanks for this quick answer, We are storing heavy objects in the repository which have plenty of sub nodes. And we are trying to manage concurrent read/write access to some of these nodes. >From a functional point of view, these nodes are representing business objects and can be modified (removed) and read at the same time by different users. >From a technical aspect, we are some problems when a thread is trying to read the node as another one is removing it (some exceptions are triggered). Our goal is to put in place a concurrent access managing system. The idea is to prevent a thread to read and write a node while another one is editing it. So if there is any solution to fit with our needs, please advice.
Thanks Regards Romain SESSA [email protected] -----Original Message----- From: Jukka Zitting [mailto:[email protected]] Sent: 03 October 2011 12:55 To: [email protected] Subject: Re: FineGrainedISMLocking implementation for concurrent access. Hi, On Mon, Oct 3, 2011 at 11:41 AM, Sessa, Romain <[email protected]> wrote: > I'm a developer on a JAVA project that uses Jackrabbit. We need to have > a better management of concurrent access on a node. The LockManager API > isn't enough, among others read access is not forbidden on a locked > node. We find "FineGrainedISMLocking" interface that seems allow to > change lock policy for concurrent access. We don't found a simple > explanation of how to implement it. Have you some development lines for > us ? FineGrainedISMLocking is a low-level tool that you most likely shouldn't be using from the application level. Can you describe your use case in more detail? Without knowing the exact requirements it's hard to suggest a solution. BR, Jukka Zitting Information in this e-mail and any attachments is confidential, and may not be copied or used by anyone other than the addressee, nor disclosed to any third party without our permission. There is no intention to create any legally binding contract or other binding commitment through the use of this electronic communication unless it is issued in accordance with the Experian Limited standard terms and conditions of purchase or other express written agreement between Experian Limited and the recipient. Although Experian has taken reasonable steps to ensure that this communication and any attachments are free from computer virus, you are advised to take your own steps to ensure that they are actually virus free. Companies Act information: Registered name: Experian Limited. Registered office: Landmark House, Experian Way, NG2 Business Park, Nottingham, NG80 1ZZ, United Kingdom. Place of registration: England and Wales. Registered number: 653331
