You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2017/03/17 21:03:41 UTC

[jira] [Resolved] (SLING-6592) JCR Content Parser

     [ https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert resolved SLING-6592.
-----------------------------------
    Resolution: Fixed

Revision: 1787499

content parser API is changed to a Stream API (as discussed in mailing list)

> JCR Content Parser
> ------------------
>
>                 Key: SLING-6592
>                 URL: https://issues.apache.org/jira/browse/SLING-6592
>             Project: Sling
>          Issue Type: New Feature
>          Components: JCR
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>             Fix For: JCR Content 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)