[
https://issues.apache.org/jira/browse/SLING-11134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17490308#comment-17490308
]
Robert Munteanu edited comment on SLING-11134 at 2/10/22, 2:51 PM:
-------------------------------------------------------------------
[~kwin] - I am currently looking into parsing vault .content.xml files in
DocView format . Since the {{oak:index}} structure is arbitrary, I am looking
at writing a generic parser that reads them and returns arbitrary structures (
JcrNode, JcrProperty, etc ).
I looked into the FileVault codebase looking for a parser that builds an
intermediate representation of the parsing result, without requiring a JCR
repository. All I found was the
[DocViewSaxImporter|https://github.com/apache/jackrabbit-filevault/blob/jackrabbit-filevault-3.5.8/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewSAXImporter.java],
which I cannot use. Is there a way of parsing .content.xml files that reuses
at least some of the FileVault code?
was (Author: rombert):
[~kwin] - I am currently looking into parsing vault .content.xml files in
DocView format . Since the {{oak:index}} structure is arbitray, I am looking at
writing a generic parser that reads them and returns arbitrary structures (
JcrNode, JcrProperty, etc ).
I looked into the FileVault codebase looking for a parser that builds an
intermediate representation of the parsing result, without requiring a JCR
repository. All I found was the
[DocViewSaxImporter|https://github.com/apache/jackrabbit-filevault/blob/jackrabbit-filevault-3.5.8/vault-core/src/main/java/org/apache/jackrabbit/vault/fs/impl/io/DocViewSAXImporter.java],
which I cannot use. Is there a way of parsing .content.xml files that reuses
at least some of the FileVault code?
> Extract Oak index definitions and package them as an additional file
> --------------------------------------------------------------------
>
> Key: SLING-11134
> URL: https://issues.apache.org/jira/browse/SLING-11134
> Project: Sling
> Issue Type: New Feature
> Components: Content-Package to Feature Model Converter
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Content-Package to Feature Model Converter 1.1.12
>
>
> It is sometimes useful to read the Oak index definitions from the content
> package and package them as an additional file ( in JSON format? ) so they
> can be more easily consumed by downstream tools that need to know the index
> definitions.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)