[
https://issues.apache.org/jira/browse/JCRVLT-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18041120#comment-18041120
]
Christian Schneider commented on JCRVLT-755:
--------------------------------------------
I did a quick comparison with cursor:
h2. Comparison Summary
h3. Main difference: experience-fragments content
deleted.zip (deleted_contents):
* Contains an empty experience-fragments node in the XML
* No experience-fragments directory structure
* The .content.xml shows <experience-fragments/> as an empty element
working.zip (working_contents):
* Contains a full experience-fragments directory structure
* Includes experience-fragments/test2/ with content
* The .content.xml shows the full structure with test2 and test4 nested inside
h3. Detailed differences:
# File structure:
* deleted.zip: 7 files total
* working.zip: 9 files total (includes 2 additional .content.xml files for the
experience-fragments structure)
# jcr_root/content/.content.xml:
* deleted.zip: Has <experience-fragments/> (empty)
* working.zip: Has full XML structure with test2 and test4 nested inside
experience-fragments
# Metadata differences:
* Different package IDs and timestamps in MANIFEST.MF and properties.xml
* deleted.zip created: 2024-06-07T10:52:12.817Z
* working.zip created: 2024-06-07T10:30:12.422Z
# Missing in deleted.zip:
* jcr_root/content/experience-fragments/.content.xml
* jcr_root/content/experience-fragments/test2/.content.xml
Conclusion: deleted.zip appears to be a version where the
experience-fragments/test2 content was removed, while working.zip contains the
complete structure with the test2 experience fragment and its test4 child 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 prior
> existing test4 content fragment was deleted on 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)
