[ https://issues.apache.org/jira/browse/JCRVLT-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated JCRVLT-255: ----------------------------------- Fix Version/s: (was: 3.4.8) 3.4.10 > ImportModes act on file serialization level not on node level > ------------------------------------------------------------- > > Key: JCRVLT-255 > URL: https://issues.apache.org/jira/browse/JCRVLT-255 > Project: Jackrabbit FileVault > Issue Type: Bug > Components: Packaging > Reporter: Konrad Windszus > Priority: Major > Fix For: 3.4.10 > > > 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: > {quote} > It is important to note, that the import mode always operates on entire nodes > and subtrees... > {quote} -- This message was sent by Atlassian Jira (v8.3.4#803005)