OSGi DevCon Europe: Blueprint services

DI, yet Legacy code-compatible, OSGi Dynamics, Hide OSGi API

Configuration:

Uses the extender pattern: The Blueprint Extender scans bundles to find xml files, creates metadata from them, and then creates beans, services, references.

Manager Types:

Bean Manager: creates POJOs and possibly wire dependencies.
Single Service Reference Manager: one to one mapping with OSGi service
Multiple Services Reference Manager: one to many mapping with OSGi service
Service Registration Manager: Allows to register a POJO as an OSGi service

Bean Manager

takes as input a configuration which is very close from the Spring bean configuration.
No, in fact it is Spring configuration reloaded... ;)

To summarize: BluePrint is a standardization of Spring DM and of Spring DI configuration.
BluePrint already has other implementations (amongst them Geronimo Blueprint by G.Nodet who gave this talk)