You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/10/30 10:30:12 UTC
[jira] [Commented] (CAMEL-5534) OSGi split package
org.apache.camel.component, both camel-core and camel-spring export
[ https://issues.apache.org/jira/browse/CAMEL-5534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486766#comment-13486766 ]
Claus Ibsen commented on CAMEL-5534:
------------------------------------
We have seen the reverse happen also, asking for ResourceEndpoint which is in camel-core, but gets a NoClassDefFoundException.
I wonder if there is any merge-first or whatever that osgi syntax is, would help? We should possible just force the package to always look in camel-core as there are the classes which is needed by Velocity, Freemarker etc.
> OSGi split package org.apache.camel.component, both camel-core and camel-spring export
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-5534
> URL: https://issues.apache.org/jira/browse/CAMEL-5534
> Project: Camel
> Issue Type: Bug
> Components: camel-core, camel-spring
> Affects Versions: 2.9.0
> Reporter: Scott Cranton
> Labels: OSGi
> Fix For: 3.0.0
>
>
> Both camel-core and camel-spring export package org.apache.camel.component. camel-spring contains org.apache.camel.component.ResourceBasedComponent, and camel-core does not, so any bundles that resolve to camel-core (most do) will get a ClassNotFoundException for ResourceBasedComponent
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira