[
https://issues.apache.org/jira/browse/JCRVLT-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ilyas Türkben updated JCRVLT-124:
---------------------------------
Attachment: example-2.zip
example-1.zip
> Inconsistent behaviour of ImportMode.MERGE
> ------------------------------------------
>
> Key: JCRVLT-124
> URL: https://issues.apache.org/jira/browse/JCRVLT-124
> Project: Jackrabbit FileVault
> Issue Type: Bug
> Components: Misc
> Affects Versions: 3.1.28
> Reporter: Ilyas Türkben
> Priority: Minor
> Attachments: example-1.zip, example-2.zip
>
>
> In \[0], it is stated that with {{ImportMode.MERGE}} option;
> bq.Existing content is not modified, i.e. only new content is added and none
> is deleted or modified.
> however in the code \[1], it imports the content only “if node is an
> authorizable or ACL”.
> Is it a documentation issue or implementation issue ? Which behavior the
> customer should expected?
> *Steps to reproduce are available:*
> # Install [^example-1.zip]
> # Install [^example-2.zip]
> Expected: apps/i18n/en/example2 should be created
> Outcome: Node is not created
>
> \[0] - [http://jackrabbit.apache.org/filevault/importmode.html]
>
> \[1]
> {{org.apache.jackrabbit.vault.fs.impl.io.GenericArtifactHandler.accept(WorkspaceFilter,
> Node, String, ArtifactSetImpl)}}
> {code:java}
> if (name.length() == 0 || parent.hasNode(name)) {
> if (wspFilter.getImportMode(path) == ImportMode.MERGE) {
> // do import the content if node is an authorizable or ACL
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
