I've been using Blueprint for a few years now and a couple of years ago I was
kicking the tires on DS and CDI. At the time there was a vigorous debate
about the future of OSGi and the place for Blueprint, DS and CDI. I've been
developing in Fuse primarily so was stuck with Karaf 2.x and the standar
You'll want to use the bundle plugin and create a blueprint.xml to bootstrap
your Camel Java DSL. I use the Camel Java DSL all the time in Blueprint for
a variety of reasons (testing is easier as the RouteBuilders exist without
the camel context). I’m not sure why your Camel blueprint archetype i
Hi Ranx,
Blueprint is still maintained and supported by Karaf. There are pros and
cons for blueprint.
DS/SCR is a nice alternative.
At the end of the day, behind the hood, it's OSGi services, that you can
use with "native" OSGi approach.
We don't necessary agree with all OSGi alliance dire
You can also directly use the Camel Blueprint DSL directly, just putting
your route in OSGI-INF/blueprint/route.xml:
http://camel.apache.org/schema/blueprint";>
...
Reg
Note that there is now an OSGI CDI spec with the reference implementation part
of Apache Aries. Whatever the technical tradeoffs between this and the PAX CDI
one I suspect the latter is not going to be vigorously maintained.
While blueprint certainly works I think that using it is likely to dis
Thank you.. I was thinking of abandoning the Java DSL and ultimately going
this way, given my lack of success of "dumping it" into an OSGi container of
some sort. The rest of my shop, though, are not blueprint DSL, Camel or Apache
product savvy, so the learning curve for my coworkers will be m
Hi,
I'm agree with JB, this the big force of Karaf is to provide all the
possibilities for the users to test and make the right choice for their
own usages.
Karaf is based on OSGi but it doesn't say that users have to use OSGi :)
Keep tune for Winegrower, it will be very nice!
regards,
Françoi
