[jira] [Commented] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224934#comment-17224934 ] Eric Norman commented on SLING-3619: I would also agree that failing fast and stopping on the first error is the safer approach. > 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 > > 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_cfp7wzmgn/T/install277506169886207.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)
[jira] [Commented] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224703#comment-17224703 ] Oliver Lietz commented on SLING-3619: - And it doesn't stop if the content type is unknown. > 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_cfp7wzmgn/T/install277506169886207.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)
[jira] [Commented] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17224682#comment-17224682 ] Dan Klco commented on SLING-3619: - IMO -- the content loader should fail fast rather than attempting to recover. I vote to close. > 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_cfp7wzmgn/T/install277506169886207.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)
[jira] [Commented] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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_cfp7wzmgn/T/install277506169886207.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)
[jira] [Commented] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766886#comment-15766886 ] Oliver Lietz commented on SLING-3619: - Yes > 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.2.0 > > > 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_cfp7wzmgn/T/install277506169886207.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 (v6.3.4#6332)
[jira] [Commented] (SLING-3619) Content Loader should handle input errors gracefully
[ https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15766807#comment-15766807 ] Carsten Ziegeler commented on SLING-3619: - [~olli] Is there anything left to do? > 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.2.0 > > > 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_cfp7wzmgn/T/install277506169886207.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 (v6.3.4#6332)
