[
https://issues.apache.org/jira/browse/JCR-3884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564531#comment-14564531
]
Satya Deep Maheshwari commented on JCR-3884:
--------------------------------------------
Here's a proposed solution at [1]. A new Delete Handler and manager is added to
take care for delete requests. It follows exactly the same pattern as the
pre-existing CopyMoveHandler. The reason for adding a new handler is that its
minimally invasive and does not change in the existing API of existing
handlers. Hence preventing any api incompatibility. Please review. If this
proposed solution is acceptable, I will clean it up and formalize it.
[1] -
https://github.com/sdmcraft/jackrabbit/commit/14490d3e29bfc72624879df9b91586e1ef31a7fe
> 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
>
> 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].
> [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)
