[
https://issues.apache.org/jira/browse/JCRVLT-509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17363710#comment-17363710
]
Dominik Süß commented on JCRVLT-509:
------------------------------------
[~kwin] this feature creates slight trouble. Not so well written packages that
were created by export may contain protected system properties like jcr:created
maintained by the system. The options would be to
A) either in general exclude protected properties from processing and move them
back to warn (they were clearly never able to install but are leftovers from an
export)
B) OR add a declarative exclude list of properties to skip (which would never
be attempted to be written)
> Make DocView import failures fail the whole installation
> --------------------------------------------------------
>
> Key: JCRVLT-509
> URL: https://issues.apache.org/jira/browse/JCRVLT-509
> Project: Jackrabbit FileVault
> Issue Type: Improvement
> Affects Versions: 3.4.10
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Major
> Fix For: 3.5.0
>
>
> Currently all ACL, authorizable and regular node exceptions are caught in
> https://github.com/apache/jackrabbit-filevault/blob/f91c3d73ab33e4155837768d70b7c3e8c7da9e2d/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewSAXImporter.java#L683
> and just logged. Afterwards the import of the package just continues. Only
> in case the ImportOptions.setStrict() is set to {{true}} it will lead to a
> PackageException in the end.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
