[ 
https://issues.apache.org/jira/browse/SLING-6440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15876056#comment-15876056
 ] 

Stefan Seifert commented on SLING-6440:
---------------------------------------

Completed: At revision: 1783893  

first implementation - short summary:
* a new osgi config parameter {{provider.json.content}} is introduced (default: 
false). if this is set to true the JSON support is activated.
* when activated all .json files in the filesystem are detected and "mounted" 
as resources. the "overlaying" of filesystem resources with JCR content 
resources does no longer happen in this case.
* apache johnzon is used internally as JSON parser (embedded in the JAR due to 
open issue GERONIMO-6560)
* ordering of json nodes is retained, comments in json files are supported
* a simplified read-only implementation of JCR Node and Property is added as 
well, so applications still relying on JCR API to do simple content read 
operations are supported as well
* the file monitor only sends resource events for the root node where the 
content structure for the json file begins when the file is changed.

i leave this ticket open for a few days while testing it further.

> Filesystem Resource Provider: Support "mounting" content resources from JSON 
> files
> ----------------------------------------------------------------------------------
>
>                 Key: SLING-6440
>                 URL: https://issues.apache.org/jira/browse/SLING-6440
>             Project: Sling
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>             Fix For: File System Resource Provider 1.3.0
>
>
> it would be nice if the filesystem resource provider does not only support 
> serving binary files and folders, but also arbitrary resources stored in 
> .json files in the folder hierarchy which are normally extracted when 
> installing the bundle with sling-initial-content.
> is is necessary to explicitly switch this feature on per configuration, 
> because it may be desired to directly serve the JSON files as binary files in 
> some cases.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to