[JCRVLT-255] ImportModes act on file serialization level not on node level

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.5.0
• Component/s: Packaging
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 18/Dec/17 10:00
• Updated: 25/May/21 05:17
• Resolved: 20/May/21 06:07

Description

When reading the docs at http://jackrabbit.apache.org/filevault/importmode.html I would assume that for ImportMode.MERGE the merging happens on node level (i.e. indepent of the actual serialization format). Unfortunately this is not the case: If I have a serialized docview .content.xml file covering the current node and three levels below the merging is not done if the entry node level does already exist in the repository, although not all child nodes are in the repository yet.

This is due to the guard in https://github.com/apache/jackrabbit-filevault/blob/8b2fedaf329b3bf4a049e41563c0bc83487406f7/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/FileArtifactHandler.java#L226. which prevents the DocViewSAXImporter from kicking in, although there are indeed subnodes in the .content.xml which are not yet in the repository.

Please either fix this behaviour of make the documentation at http://jackrabbit.apache.org/filevault/importmode.html clearer because it explicitly says there:

It is important to note, that the import mode always operates on entire nodes and subtrees...

Issue Links

• is duplicated by: JCRVLT-124 Inconsistent behaviour of ImportMode.MERGE
• is related to: JCRVLT-124 Inconsistent behaviour of ImportMode.MERGE
• is related to: SLING-7501 FilveVault 3.1.38 breaks the Sling IDE Tools "Import from server..."
• relates to: JCRVLT-396 Import mode "MERGE" and "UPDATE" still may remove properties during import