[
https://issues.apache.org/jira/browse/JCR-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109335#comment-13109335
]
angela commented on JCR-3078:
-----------------------------
thanks for patch. looks good.
i will apply it with some minor modifications:
- passing the source/destination davresources instead of source-locator and
destination path
- in analogy to the IOHandler and PropertyHandler i would create a
copymovecontext that allows to retrieve
the workspace and/or session object and provides additional details of the
copy/move operation.
such as e.g. if the copy should be shallow or not.
hope that fits your needs.
> Add CopyMoveHanlder so that the copy/move behavior can be customized (as this
> is the case for the IOHandler and PropertyHandler)
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JCR-3078
> URL: https://issues.apache.org/jira/browse/JCR-3078
> Project: Jackrabbit Content Repository
> Issue Type: New Feature
> Components: jackrabbit-jcr-server
> Affects Versions: 2.2.7
> Reporter: Philipp Koch
> Assignee: angela
> Fix For: 2.3.0
>
> Attachments: CopyMoveHandler.patch
>
>
> The IOHandler impls let you define a specific import/export behavior either
> for specific nodetypes/locations/etc which is just great. this works well
> while you create or modify a web dav resource but does not work for the
> copy/move use case.
> the attached patch provides a proposal for an additional CopyMoveHandler.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
