[jira] [Commented] (JCRVLT-755) All contents are deleted when a content package created from a folder is applied

["Christian Schneider (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCRVLT-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17864133#comment-17864133 ] 

Christian Schneider commented on JCRVLT-755:
--------------------------------------------

[~reschke] I think we always use REPLACE mode. test4 is deleted in the case of deleted.zip.

Is this expected?

 

> All contents are deleted when a content package created from a folder is applied
> --------------------------------------------------------------------------------
>
>                 Key: JCRVLT-755
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-755
>             Project: Jackrabbit FileVault
>          Issue Type: Bug
>          Components: vlt
>            Reporter: Christian Schneider
>            Priority: Critical
>         Attachments: deleted.zip, working.zip
>
>
> We have a strange issue where replication of a folder deletes all contents of the folder on destination system. 
> We create a filevault package from the folder and apply the package using filevault on the destination system. 
> It seems the behaviour is different depending if the folder or parent folder has a jcr:content sub node. 
> I attached two content packages:
>  * working.zip  : Export of /content/experience-fragements/test2 when experience-fragements has jcr:content subnode. In this case an existing experience fragement at /content/experience-fragements/test2/test4 is not deleted
>  * deleted.zip :  Export of /content/experience-fragements/test2 when experience-fragements does not have jcr:content subnode. In this case prio existing test4 content fragment was deletedon apply.
> The content packages look different. In the case with jcr:content experience-fragments and test2 are folders in the zip. 
> In case without jcr:content inside experience-fragments there are no folders like above. Instead the sub nodes are inside a single content.xml



--
This message was sent by Atlassian Jira
(v8.20.10#820010)