Sure. First let me provide the background context. When a file is edited using some common desktop applications like MS Word, Adobe Photoshop etc. the following happens:
1. A temp file is created for the original file being edited. 2. When the use clicks on 'Save', the original file is deleted. 3. The temp file is renamed to the original file. If this file is in a mapped drive mounted from jackrabbit, all these events are received as webdav requests in the jackrabbit's webdav servlet. Now coming to our application, the 'delete' operation on the original file (as in step#3) above causes all versioning information on the original file to be removed as well. We want to avoid this as this 'delete' wasn't a user initiated delete but one of the intermediate steps of editing a file. So I want to have a handle to hook in our application logic to salvage the version history before the file gets deleted. Hope I was able to explain the problem. On Sat, May 30, 2015 at 11:33 AM, Julian Reschke < [email protected]> wrote: > On 2015-05-29 12:23, Satya Deep Maheshwari wrote: > >> I have logged JCR-3884 <https://issues.apache.org/jira/browse/JCR-3884> >> to >> track this. Have also added a proposed solution in it. Please take a look. >> >> Regards >> Satya Deep >> > > It would be helpful to understand *why* you need application-specific > logic for DELETE. Can you provide an example? > > Best regards, Julian >
