You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Jason E Bailey (JIRA)" <ji...@apache.org> on 2019/08/06 17:39:00 UTC

[jira] [Commented] (SLING-7927) JSON Content Loading errors out import on malformed json

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

Jason E Bailey commented on SLING-7927:
---------------------------------------

This is definitely an issue with the Content Loader. Because this happened in AEM land. BTW the Content Loader does not use the Content Parser in the way that you would think. It embeds one or two specific files into the Content Loader bundle.

> JSON Content Loading errors out import on malformed json
> --------------------------------------------------------
>
>                 Key: SLING-7927
>                 URL: https://issues.apache.org/jira/browse/SLING-7927
>             Project: Sling
>          Issue Type: Bug
>            Reporter: Jason E Bailey
>            Assignee: Jason E Bailey
>            Priority: Major
>             Fix For: JCR ContentLoader 2.3.2
>
>
> Current Behaviour:
> During the importing of json content from a bundle. If one of the files contains malformed json the load process is discontinued and exits. This stops the loading of any other, correctly formatted, data.
>  
> Expected Behaviour:
> If a single file contains malformed content, that specific file should discontinue, the error logged and then the process continues to import the rest of the provided content.
> As it is right now, it's possible to load the bundle and have the application in an unworkable state. preventing the ability to trouble shoot and investigate the root cause.
>  



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)