[
https://issues.apache.org/jira/browse/SLING-6634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923902#comment-15923902
]
Konrad Windszus commented on SLING-6634:
----------------------------------------
bq. it makes not sense for parsing FileVault XML - the contentloader takes a
"shortcut" here and directly uses JCR/jackrabbit APIs to import the XML file
content without having to parse it itself - which is of course the best solution
The XML format being used by FileVault is an extended document view format
(which is not specified/supported by plain JCR 2.0). E.g. it allows to specify
the type of property values and multivalues (compare with
https://issues.apache.org/jira/browse/JCRVLT-132). The current XML formats
(document and system view) should of course still be supported. It is unclear
though how to detect that an XML is enhanced DocView format.
> Use new FS Content Parser module in ContentLoader
> -------------------------------------------------
>
> Key: SLING-6634
> URL: https://issues.apache.org/jira/browse/SLING-6634
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR ContentLoader 2.1.10
> Reporter: Konrad Windszus
>
> With the new module being added with SLING-6592 it should be easy to add
> FileVault XML support to the JCR Contentloader.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
