[
https://issues.apache.org/jira/browse/JCR-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2565.
-------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
Assignee: angela
changed overwrite header to F and adjusted the copy/move operation in the
servlet in order NOT to fail in case of existing destination including
some comments why this is required for the remoting although not in accordance
with the RFC.
in addition added a test to jackrabbit-jcr-test for copying twice with
SNS-enabled at the destination checking if this results
in 2 child nodes. this didn't work with the overwrite header T either as the
existing node got removed...
> spi2dav: Overwrite header T specified for MOVE and COPY causes failure if
> some API tests
> ----------------------------------------------------------------------------------------
>
> Key: JCR-2565
> URL: https://issues.apache.org/jira/browse/JCR-2565
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-spi2dav
> Affects Versions: 2.0.0
> Reporter: angela
> Assignee: angela
> Fix For: 2.1.0
>
>
> failing tests are:
> org.apache.jackrabbit.test.api.WorkspaceCopySameNameSibsTest#testCopyNodesNodeExistsAtDestPath
> org.apache.jackrabbit.test.api.WorkspaceMoveSameNameSibsTest#testMoveNodesNodeExistsAtDestPath
> those would be fixed by setting the overwrite header to F(alse)... however,
> this doesn't fit those cases where same-same
> siblings would be allowed and the copy/move to a destination with existing
> item would succeed in JCR.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
