[
https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15892708#comment-15892708
]
Konrad Windszus commented on SLING-6592:
----------------------------------------
I would recommend to rely for the extended document view format (being support
by FileVault) on FileVault internal classes. Otherwise you might run into
issues like SLING-6368. The extended docview xml format is nowhere formally
specified, therefore all reimplementations of the parser must fail. I would
really recommend to leverage {{DocViewNode}} and {{DocViewProperty}} for
vault-compatible XML file parsing instead.
> File System Content File Parser
> -------------------------------
>
> Key: SLING-6592
> URL: https://issues.apache.org/jira/browse/SLING-6592
> Project: Sling
> Issue Type: New Feature
> Components: Commons
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Fix For: File System Content File Parser 1.0.0
>
>
> for different usecases around file system resource provider and sling mocks
> (see related tickets) we need to parse content structures from files in the
> file system, e.g. in JSON format or JCR XML format.
> we should put this code in a new commons library so it can be reused from the
> different projects.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
