[ https://issues.apache.org/jira/browse/JCR-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14586524#comment-14586524 ]
Tobias Bocanegra commented on JCR-3884: --------------------------------------- [~satyadeep] I added some comments on the patch on github. ,mainly: - more / better javadoc - don't need public modifiers on methods of public interfaces - no {{[DELETE_HANDLER]}} prefixes in log messages. > Add handler to handle webdav based DELETE requests > -------------------------------------------------- > > Key: JCR-3884 > URL: https://issues.apache.org/jira/browse/JCR-3884 > Project: Jackrabbit Content Repository > Issue Type: Improvement > Components: jackrabbit-webdav > Reporter: Satya Deep Maheshwari > Assignee: Tobias Bocanegra > > The AbstractWebdavServlet takes care of handling > the webdav requests. In case of DELETE, it just goes ahead and deletes the > resource. See [1]. A mechanism is needed to hook in any code here to get > invoked whenever a DELETE request is made, similar to CopyMoveHandler which > get invoked in case of COPY/MOVE requests. > Related conversation on this in jackrabbit users' mailing list at [2]. > Proposed Solution: > https://github.com/sdmcraft/jackrabbit/commit/a0799f724d8c68f5047d2103645693cb313abda4 > [1]-https://github.com/apache/jackrabbit/blob/trunk/jackrabbit-webdav/src/main/java/org/apache/jackrabbit/webdav/server/AbstractWebdavServlet.java#L336 > [2]-http://jackrabbit.510166.n4.nabble.com/Handling-webdav-DELETE-request-td4662375.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)