You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Eric Norman (JIRA)" <ji...@apache.org> on 2018/12/20 19:28:00 UTC
[jira] [Updated] (SLING-3619) Content Loader should handle input
errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Norman updated SLING-3619:
-------------------------------
Fix Version/s: (was: JCR ContentLoader 2.2.8)
JCR ContentLoader 2.3.2
> Content Loader should handle input errors gracefully
> ----------------------------------------------------
>
> Key: SLING-3619
> URL: https://issues.apache.org/jira/browse/SLING-3619
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR ContentLoader 2.1.8
> Reporter: Yogesh Upadhyay
> Assignee: Oliver Lietz
> Priority: Minor
> Fix For: JCR ContentLoader 2.3.2
>
>
> After upgrading to latest sling jar file, content loader stopped working to load content using Sling-Initial-Content. Getting following message in log
> 29.05.2014 23:20:21.504 *INFO* [Background Install /var/folders/mh/tkx6mmq53tb_bcph_cfp7wzm0000gn/T/install2775061698862333307.tmp] org.apache.sling.jcr.contentloader.internal.DefaultContentCreator createFile: Cannot find content type for body.jsp, using application/octet-stream
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)