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

Stefan Seifert commented on SLING-11189:
----------------------------------------

i've prepared a PR which actually fixed the problem on my environment: 
https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/12

it's using 4 separate defined references for the for content loaders because at 
least when using the DS annotations it's not possible to define a minimum 
cardinality of 4 - but the result is the same.

> Content Loader: Race condition registering readers vs. loading content
> ----------------------------------------------------------------------
>
>                 Key: SLING-11189
>                 URL: https://issues.apache.org/jira/browse/SLING-11189
>             Project: Sling
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: JCR ContentLoader 2.5.0
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>            Priority: Major
>
> in SLING-11168 we detected a specific problem with Composum in Sling Starter 
> 12, which only occured on Windows 10 environments (and even there not 
> consistently in every scenario).
> it seems that it may happen that Sling-Initial-Content is loaded from the 
> bundles when the ContentReader implementations are not yet registered on the 
> ContentReaderWhiteboard.
> when this happens, the content is loaded into the repository, but files like 
> *.json are not transformed to nodes and properties, but is stored as binary 
> json files in the repository.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to