[
https://issues.apache.org/jira/browse/SLING-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14014496#comment-14014496
]
Yogesh Upadhyay commented on SLING-3619:
----------------------------------------
Hello [~olli] I found what issue was. Content loader failed to work after
throwing this exception
30.05.2014 20:31:59.060 *ERROR* [Background Update app (107)]
org.apache.sling.jcr.contentloader.internal.Loader Failed to process file
bundle://107.23:0/SLING-CONTENT/test.xml
30.05.2014 20:31:59.071 *ERROR* [Background Update app (107)]
org.apache.sling.jcr.contentloader.internal.Loader Cannot load initial content
for bundle app : unknown type: Long[]
javax.jcr.RepositoryException: unknown type: Long[]
at
org.apache.sling.jcr.contentloader.internal.Loader.createNode(Loader.java:490)
at
org.apache.sling.jcr.contentloader.internal.Loader.handleFile(Loader.java:415)
at
org.apache.sling.jcr.contentloader.internal.Loader.installFromPath(Loader.java:375)
at
org.apache.sling.jcr.contentloader.internal.Loader.installFromPath(Loader.java:370)
at
org.apache.sling.jcr.contentloader.internal.Loader.installFromPath(Loader.java:370)
at
org.apache.sling.jcr.contentloader.internal.Loader.installContent(Loader.java:239)
at
org.apache.sling.jcr.contentloader.internal.Loader.registerBundleInternal(Loader.java:149)
at
org.apache.sling.jcr.contentloader.internal.Loader.registerBundle(Loader.java:96)
at
org.apache.sling.jcr.contentloader.internal.ContentLoaderService.bundleChanged(ContentLoaderService.java:140)
at
org.apache.felix.framework.util.EventDispatcher.invokeBundleListenerCallback(EventDispatcher.java:869)
at
org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:790)
at
org.apache.felix.framework.util.EventDispatcher.fireBundleEvent(EventDispatcher.java:515)
at org.apache.felix.framework.Felix.fireBundleEvent(Felix.java:4409)
at org.apache.felix.framework.Felix.activateBundle(Felix.java:2142)
at org.apache.felix.framework.Felix.startBundle(Felix.java:2070)
at org.apache.felix.framework.Felix.updateBundle(Felix.java:2410)
at org.apache.felix.framework.BundleImpl.update(BundleImpl.java:994)
at
org.apache.felix.webconsole.internal.core.UpdateHelper.doRun(UpdateHelper.java:60)
at
org.apache.felix.webconsole.internal.core.BaseUpdateInstallHelper.doRun(BaseUpdateInstallHelper.java:89)
at
org.apache.felix.webconsole.internal.core.UpdateHelper.doRun(UpdateHelper.java:70)
at
org.apache.felix.webconsole.internal.core.BaseUpdateInstallHelper.run(BaseUpdateInstallHelper.java:121)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.IllegalArgumentException: unknown type: Long[]
at javax.jcr.PropertyType.valueFromName(PropertyType.java:269)
at
org.apache.sling.jcr.contentloader.internal.readers.XmlReader$PropertyDescription.create(XmlReader.java:456)
at
org.apache.sling.jcr.contentloader.internal.readers.XmlReader.parseInternal(XmlReader.java:279)
at
org.apache.sling.jcr.contentloader.internal.readers.XmlReader.parse(XmlReader.java:171)
at
org.apache.sling.jcr.contentloader.internal.Loader.createNode(Loader.java:484)
... 21 common frames omitted
I had following entry in test.xml
<property>
<name>bodyPartId</name>
<value>1</value>
<type>Long[]</type>
</property>
I feel that loader should ignore exception gracefully and continue with next
node in case of error.
> Content Loader Not working in current trunk build
> -------------------------------------------------
>
> Key: SLING-3619
> URL: https://issues.apache.org/jira/browse/SLING-3619
> Project: Sling
> Issue Type: Bug
> Reporter: Yogesh Upadhyay
> Assignee: Oliver Lietz
>
> 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
(v6.2#6252)
