You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by ajuffing <an...@kb.nl> on 2010/10/26 12:30:06 UTC
Blueprint, Spring DM, Spring DM 2, ...
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
--
View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-Spring-DM-Spring-DM-2-tp1772751p1772751.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint, Spring DM, Spring DM 2, ...
Posted by ajuffing <an...@kb.nl>.
Thanks! Using two different dependency mechanism doing the same thing is
exactly what I'm trying to avoid - I prefer consistency and I think we will
go for Aries Blueprint, due to the fact that the Karaf Framework is using
it.
Andreas
--
View this message in context: http://karaf.922171.n3.nabble.com/Blueprint-Spring-DM-Spring-DM-2-tp1772751p1773210.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Blueprint, Spring DM, Spring DM 2, ...
Posted by Guillaume Nodet <gn...@gmail.com>.
I second J-B here.
Also note that given both Spring DM 2.x and Aries Blueprint implement
the BLueprint spec, we haven't experimented much deploying both in the
same time (we're mostly using spring-dm 1.2.x when needed).
On Tue, Oct 26, 2010 at 12:49, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
> 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
>>
>
--
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Blueprint, Spring DM, Spring DM 2, ...
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
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
>