I found the “aries-blueprint-spring” feature in Karaf’s Spring feature file: https://github.com/apache/karaf/blob/master/assemblies/features/spring/src/main/feature/feature.xml#L452
Seems like I’ve got the same setup. From: Nicholas Baker <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Tuesday, August 23, 2016 at 4:26 PM To: "[email protected]" <[email protected]> Subject: Using Aries Blueprint Spring Extender instead of SpringDM Hey All, I’m back to migrating another one of our legacy plugins over to OSGI. It creates a customized Spring ApplicationContext as part of its lifecycle and uses it directly in code to factory objects. I cannot change this last detail this release. I had immediate success using SpringDM and a fragment bundle to tell DM which ApplicationContext class to instantiate. I was then able to reference the ApplicationContext in a blueprint running within the same bundle. SpringDM is nice enough to publish it to the registry. All well and good. Except now I’m having issues with Java 8 bytecode coming into the project. SpringDM is using the old Spring 3.x codeline and apparently has a copy of some old ASM classes not compatible with Java 8. I’m trying to update to Spring 4 and use the Aries Spring Extender instead of SpringDM since I’ve heard such good things. I’ve deployed the following bundles as well as Snapshots of the latest of all Aries blueprint bundles: org.apache.aries.blueprint.spring org.apache.aries.blueprint.spring.extender Nothing’s happening though. The bundle times-out trying to find the <reference> to the ApplicationContext. Has anyone had success replacing SpringDM? If so can you detail what you had to do? Thanks, Nick
