felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Nodet <gno...@gmail.com>
Subject [Karaf] Switching to blueprint ...
Date Tue, 28 Apr 2009 13:45:00 GMT
The past days, I've been working on the blueprint implementation
inside Geronimo [1].
The spec is still being written so the implementation is not really
stable and is still missing a lot of features.
However, it's already somewhat usable and as I've hacked Karaf to
start using blueprint instead of spring-dm in a branch [2].
Tests do not even compile, but I've been able to start the console, so
I thought I would talk about it a bit.

This raises the question whether we want to switch to blueprint
instead of spring-dm.
I think we should, and even have to, given that  Spring-DM will switch
to support Blueprint at some point in the future too.  Also the
blueprint spec is way better than spring-dm wrt to namespace handlers
(that are considered dependencies, so we would not have problems with
namespace handlers not being available when a bundle is started) and
classloading (i think classes loaded for namespace handlers will be
loaded from the namespace handler bundle, thus freeing the bundle to
import all the namespace handlers packages), though those areas are in

If so, we might even want to do that before renaming the packages, as
the patch is quite big and would be quite broken after the rename imho

As for tests, we'd have to switch to something else, which could be
junit4osgi from iPojo or pax-exam for example.

Feedback welcome.

[1] https://svn.apache.org/repos/asf/geronimo/sandbox/blueprint
[2] https://svn.apache.org/repos/asf/felix/sandbox/gnodet/karaf-blueprint/

Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA

View raw message