[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224675#comment-17224675 ]
Oliver Lietz commented on SLING-3619: ------------------------------------- [~enorman], [~jeb], [~dklco], You guys have worked mainly on Content Loader in the past – is this issue still relevant or should we close it? > 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.4.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 (v8.3.4#803005)