[
https://issues.apache.org/activemq/browse/CAMEL-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52444#action_52444
]
Guillaume Nodet commented on CAMEL-1730:
----------------------------------------
I know very well camel can be used in OSGi right now. One of the problem comes
from the way the osgi / camel integration works. If the camel-osgi bundles is
not correctly deployed (meaning camel-spring has been resolved after camel-osgi
has been installed), it leads to a lot of problems.
The goal is simple to remove some of the problems by merging the two bundles
together but still retain the existing behavior: i.e. just use plain Camel when
deployed in a non osgi env and use the camel / osgi integration when deployed
in OSGi.
I don't see any drawbacks to this approach if done correctly (i.e. no
additional dependency when used in a non osgi environement).
> Merge camel-spring and camel-osgi into a single bundle
> ------------------------------------------------------
>
> Key: CAMEL-1730
> URL: https://issues.apache.org/activemq/browse/CAMEL-1730
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: Guillaume Nodet
> Assignee: Willem Jiang
> Fix For: 2.0.0
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
