Community
Participate
Working Groups
Gemini Blueprint currently supports context declarations in META-INF/spring and OSGI-INF/blueprint, the former being the original spring-dm or spring-osgi standard and the latter the current blueprint spec standard. However, while blueprint declarations are supported in both places, the context declarations are treated in different ways: Declarations in META-INF/spring are instantiated without additional blueprint container capabilities but, for legacy support reasons, in the old spring-dm way with extra support for blueprint namespaces. Decladations in OSGI-INF/blueprint however feature all spring + blueprint namespace capabilities AND yield a standards compliant blueprint container. Since spring-dm / spring-osgi is long gone, it is time to remove this special treatment for the sake of simplicity and to avoid further confusion. See also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=532246 https://stackoverflow.com/questions/13703541/combine-osgi-blueprint-and-spring-configuration
Removed target milestone: Altering context behavior touches core components of gemini blueprint and requires extensive refactoring, as the spring-dm style context initialization represents the "original" spring-dm implemenation. This shall thus be adressed outside of the 3.x release.
