[ https://issues.apache.org/jira/browse/JCRVLT-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17853634#comment-17853634 ]
Julian Reschke edited comment on JCRVLT-755 at 6/10/24 12:33 PM: ----------------------------------------------------------------- In both ZIPs I see "test4" as empty node. What is the import mode? REPLACE? UPDATE? What does happen with "test4". Is it *deleted*, or replaced by an empty node? was (Author: reschke): In both ZIPs I see "test4" as empty node. What is the import mode? REPLACE? UPDATE? What does happen woth "test4". Is it *deleted*, or replaced by an empty node? > 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)