The OSGi Enterprise Specification defines a Blueprint Service. Apache
Aries and Eclipse Gemini are two independent projects providing
implementations of this specification, and a lot more.
Spring DM is discontinued and has become the basis of Eclipse Gemini
Blueprint.
If you're interested in a tight integration with vanilla Spring then
you'll probably find it easier to work with Gemini Blueprint.
The most important but too poorly documented fact is, Gemini Blueprint
includes the entire set of basic Spring bundles, and all Spring features
like declarative transactions by annotation and AOP can be configured
from blueprint.xml using custom XML namespaces.
In other words, for basic dependency injection and interaction with the
OSGi service registry, you use the standardized Blueprint XML syntax
instead of Spring <bean> elements, and all other Spring features not
part of the Blueprint Specification are available as Blueprint
extensions via custom namespaces.
Hope that helps,
Harald
