[
https://issues.apache.org/activemq/browse/CAMEL-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-775.
-------------------------------
Resolution: Working as Designed
Fix Version/s: 1.5.1
Willem Jiang has done some great update on the camel-osgi side in Camel 2.0 and
1.6.
Closing this one, also based on gnodets suggestion that the dynamic is not
needed.
> 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.5.1, 2.0.0
>
>
> 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.
