Hi Andreas,
For now, the preferred mechanism in Karaf is the Aries Blueprint
implementation.
We prefer Aries Blueprint more than Spring DM as Aries Blueprint is more
flexible, especially around namespaces. But, if you want, you can still
use Spring DM (provided by feature).
As reminder, Spring DM and Aries Blueprint are both an implementation of
the OSGi Blueprint specificiation. The reference implementation of the
spec is Spring DM.
Another tip: as you said, Karaf provides shell/console, WebConsole, etc,
but it provides JMX MBeans for the management. It can be helpful for
you. You can easily extend the shell by adding your own command (linked
to your application).
I made an application on top on Karaf, using Blueprint, branding and
adding command. It's an example of what you can do:
http://buildprocess.svn.sourceforge.net/viewvc/buildprocess/builderaser/trunk/
Welcome to Karaf ;)
Regards
JB
On 10/26/2010 12:30 PM, ajuffing wrote:
Hi!
We are going to implement an application on top of the Karaf Framework. We
are considering to use several provided functions from the Karaf Framework
(Shell/Console, WebConsole). Our plan is to build execution/worker bundles
and a few management bundles for the WebConsole.
Now I'm struggling a bit with the different configuration/dependency
injection mechanism. Due to the early stage of the project we are basically
free to choose. Whats the main mechanism used in Karaf, so that we can best
integrate with the available Karaf bundles? Whats the roadmap (Spring DM 2)?
Thanks
Andreas
