[jira] Commented: (CAMEL-775) camel osgi DynamicImport-Package

["Cameron Braid (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51157#action_51157 ] 

Cameron Braid commented on CAMEL-775:
-------------------------------------

I've hit a similar issue - using camel 2.0 snapshot

I added static import of org.apache.camel to my manifest and it didn't fix it.

Adding "DynamicImport-Package: org.apache.camel.*" fixes it.

[SpringOsgiExtenderThread-2] DEBUG org.apache.camel.impl.DefaultPackageScanClassResolver - Loading from osgi buindle using classloader: BundleDelegatingClassLoader for [cut (cut)]
[SpringOsgiExtenderThread-2] DEBUG org.apache.camel.impl.DefaultPackageScanClassResolver - Could not find class 'org/apache/camel/component/file/GenericFileProducer.class' in classloader: BundleDelegatingClassLoader for [cut (cut)]. Reason: java.lang.ClassNotFoundException: org.apache.camel.component.file.GenericFileProducer not found from bundle [cut]
java.lang.ClassNotFoundException: org.apache.camel.component.file.GenericFileProducer not found from bundle [cut]
	at org.springframework.osgi.util.BundleDelegatingClassLoader.findClass(BundleDelegatingClassLoader.java:103)
	at org.springframework.osgi.util.BundleDelegatingClassLoader.loadClass(BundleDelegatingClassLoader.java:156)

If this is a different issue, I am happy to open a new ticket.

> camel osgi DynamicImport-Package
> --------------------------------
>
>                 Key: CAMEL-775
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-775
>             Project: Apache Camel
>          Issue Type: Sub-task
>          Components: camel-core, camel-osgi
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>             Fix For: 1.6.0, 2.0-M1
>
>
> See parent issue.
> Thanks Claus. I hope this can help getting it resolved. Let me know if it is, even a snapshot will do very well for us.
> Another question, is below "DynamicImport-Package workaround" supposed to be bug? Or it's just the way Camel needs to be configured on OSGi? If so it should be mentioned somewhere in the docs... not everybody knows that DynamicImport-Package even exists.. (even some OSGi programmers)
> First of all, to even get this to "work" requires my own bundle to have this manifest:
> DynamicImport-Package: org.apache.camel.*
> Failing to do so will result in more classloading errors.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.