Weird, I didn't see this last year after you posted it. I don't know why. I
was up here reading on the latest as I'm going to be doing some prototyping
with Fuse 7 and wanted to see what latest best practices are and where CDI
is after the February release date.
I probably should write a blog/
I posted this to the Karaf forum but it may more appropriately belong here.
It's going to be one or the other.
Has CDI been deprecated from the OSGi specification. I was hoping to use it
in the future instead of Blueprint or DS or in addition to them. I re all
last year a new OSGi service expor
What I found odd about the Camel comment that Claus made is that Guillaume
just put in the CDI annotations for service export and reference last year.
Initially he did it with Blueprint but swapped it out with DS. I prefer
working with CDI as there is a lot of testing I can do in Camel that uses
Matt,
This is an exchange between Christian and Guillaume from couple of months
back when I was asking about this. I've put Guillaume's comments in bold.
DI would be great but it is is less well supported on OSGi than blueprint
and the current implementations also have the same bad proxy behav
I did use it not too long ago but had to get back to a paying gig. But the
technology is certainly what we need, I think.
SCR is fine until you then realize that you have wire things up in your
bundle and don't have too many good choices about the matter. Blueprint is
a little long tooth and cl
I certainly don't share Camel routes between bundles on an interface or
implementation somehow and I do use OSGi services when appropriate. Just
not as much as I used to. I'm aware of the trade offs.
One such trade off is by using Camel routes I can move a bundle from one
instance running on o
I'm not quite sure I grok this. I've used both Blueprint and DS. I've also
used CDI but it isn't quite ready for primetime.
But CDI permits exporting services, referencing services, and wiring bundle
internals with injection annotations. It greatly simplifies testing.
So I'm not quite sure what
Christian,
I've also seen a lot of people using Processors/Exchanges which
unnecessarily couples their cod to the Camel framework. Unfortunately the
Camel in Action book doesn't get around to advising against that practice
until your well over 100 pages into the books. And when it does it is in
