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

Guillaume Nodet commented on CAMEL-12026:
-----------------------------------------

So the problem is that simple camel context work, but it's not fully integrated 
in OSGi and can not retrieve components and such from the OSGi registry, etc...

I've added correct support in a new blueprint-spring-camel module, see 
ARIES-1761, and the code at 
https://github.com/apache/aries/tree/trunk/blueprint/blueprint-spring-camel/src/main/java/org/apache/camel/osgi.

> ensure camel bundle with spring configuration works in OSGi with 
> aries-blueprint-spring bridge
> ----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-12026
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12026
>             Project: Camel
>          Issue Type: Task
>            Reporter: Freeman Fang
>            Assignee: Guillaume Nodet
>            Priority: Major
>         Attachments: say-more-spring.tar
>
>
> the spring-dm won't work with spring 4.x, and there's a new blueprint-spring 
> introduced in Aries to make the spring configured bundle still work with 
> spring 4.x
> We need add back CamelContextFactoryBean.java and OsgiSpringCamelContext.java 
> which was removed with camel-spring-dm module, as they are "OSGi context 
> aware" and ensure we use OsgiComponentResolver, OsgiDataFormatResolver etc 
> with the bundle in OSGi.
> We need remove spring-dm dependency from those classes.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to