[
https://issues.apache.org/jira/browse/SLING-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928282#comment-15928282
]
ASF GitHub Bot commented on SLING-6592:
---------------------------------------
GitHub user stefanseifert opened a pull request:
https://github.com/apache/sling/pull/203
SLING-6592 switch to stream-based API for ContentParser
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stefanseifert/sling
feature/SLING-6592-contentparser-stream-api
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/203.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #203
----
commit 54159e8cba118cfa9df109e4e7fea6ce6ce1a55e
Author: sseifert <sseif...@pro-vision.de>
Date: 2017-03-16T15:28:18Z
SLING-6592 switch to stream-based API for ContentParser
----
> 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)
