Alex Rivera | Logout

OSGi: Blueprint vs. Spring DM

Asked 2012-04-04T09:53:19.343
37

I am a little bit confused about Blueprint and Spring DM:

From what I think is true:

  • Spring DM is a framework defined by Spring Source
  • Blueprint is a framework defined by the OSGi Alliance
  • Blueprint has "taken" many of it's ideas from Spring DM

No?

Can we expect that those two frameworks become one in the future (merge)? If not, which one will be the most future-proof?

Edit
Report

2 Answers

30

OSGi 4.2 introduces the Blueprint Service specification based on Spring Dynamic Modules project for which Spring DM (2.x) is the Reference Implementation (RI).

In short: Blueprint is a specification, Spring DM is an implementation of Blueprint API

answered 2012-04-04T10:04:02.097
17

Blueprint was developed in the OSGi Alliance under the lead of SpringSource/Interface21.

However, if you're looking for a way to leverage OSGi use Declarative Services (DS) with annotations between bundles (services). In my experience, you do not really need the wiring XML when you make small cohesive bundles. DS is much better in working with services than Blueprint/Spring DM since they tend to to want to "hide" the dynamicity while DS just makes it trivial to use.

answered 2012-04-05T12:48:56.803

Your Answer