Hi Brad, Camel CDI only works at the level of CDI beans, that is it won’t manage RouteBuilder instances that are declared as SCR component.
Then you can imagine having Camel CDI and SCR components collaborating through the OSGi registry, using PAX CDI in the mix. That being said, Camel CDI / SCR integration is an area that still needs some work. Antonin > On 21 Aug 2016, at 02:38, Brad Johnson <brad.john...@mediadriver.com> wrote: > > I've been working a bit with both the Camel SCR and CDI lately. The CDI is > quite impressive and works very well. SCR I'm not so certain about yet. > > What I'm really unsure about is if they are compatible and can be used > together. I don't suppose there is anything that technically keeps them > from working together but the examples of Camel SCR use the AbstractCamel > runner which requires a list of route builders. > > The Camel CDI automatically runs RouteBuilders it finds that are marked as > such so it might end up with two of them making two starts. > > Are they not supposed to be used together? > > Part of what makes this a real question for me know is the Kura library as > well. It has an OSGi way of exposing it to the world. > > <scr:component name="org.eclipse.kura.example.camel.MyKuraRouter" > activate="activate" deactivate="deactivate" enabled="true" immediate="true"> > <implementation class="org.eclipse.kura.example.camel.MyKuraRouter"/> > </scr:component> > > So it's difficult to imagine how all three of those technologies might be > used together or if they should be used together. > > Any insights or thoughts or guesses are appreciated. > Brad
