No real doc unfortunately. The spring part is a bundle which provides support for all spring namespaces from blueprint. You can mix and match spring / blueprint beans, or can simply import a set of spring xml using <bean:import/> This include support for the main spring namespace, but also support for spring custom namespaces such as util, tx, etc... Interactions with the OSGi registry must be done using blueprint. You can find an example at
https://github.com/apache/aries/blob/trunk/blueprint/blueprint-testbundles/src/main/resources/OSGI-INF/blueprint/config.xml The extender part is really built on top of the above but aims to be a replacement at the deprecated spring-dm (which does not support spring 4.x) for exemple. Spring-DM bundles are supported out-of-the-box using the bundle. Interaction with the OSGi registry can be done using the spring osgi custom namespace. You can find a sample bundle at https://github.com/apache/aries/tree/trunk/blueprint/blueprint-testbundlee Guillaume 2016-04-25 9:47 GMT+02:00 Michael Täschner <m.taesch...@gmail.com>: > Hi Guillaume, > > do you have some documentation for the > blueprint-spring/blueprint-spring-extender usage? Does it use the blueprint > service/reference declarations for OSGi integration? > > The Aries frontpage seems quite outdated ... > > Thanks and Best Regards, > Michael > > 2016-04-24 23:15 GMT+02:00 Guillaume Nodet <gno...@apache.org>: > >> You can use the blueprint-spring namespace handler and >> blueprint-spring-extender bundle. >> The first one provides full support for spring namespaces (including >> custom ones) from a blueprint app. So you can simply have an empty >> blueprint which import the spring xml. >> >> The second one is an equivalent of spring-osgi / spring-dm. The exact >> same namespace is supported, but on top of the above. >> >> Those bundles have been released at Aries in version 0.2.0 very >> recently. Feel free to have a look and see if they help. >> >> >> 2016-04-23 10:42 GMT+02:00 Tomek <tomasz.wozn...@s3group.com>: >> >>> Christian and Tom >>> >>> Thanks for Your answer, so I see now that spring in OSGi is problematic >>> in >>> general it is not only our case. >>> >>> Unfortunately Blueprint or DS is not an option for us because there is no >>> agreement in the team to use something else than spring (it is a strong >>> resistance) so we stay with our library for spring on osgi for long. >>> But Christian Your plugin is also a nice solution as it reduce the work >>> related to maintaining blueprint.xml , I didn't spotted it earlier >>> >>> Thanks >>> Tomasz >>> >>> >>> >>> -- >>> View this message in context: >>> http://karaf.922171.n3.nabble.com/How-do-You-use-spring-in-OSGi-tp4046335p4046338.html >>> Sent from the Karaf - User mailing list archive at Nabble.com. >>> >> >> >> >> -- >> ------------------------ >> Guillaume Nodet >> ------------------------ >> Red Hat, Open Source Integration >> >> Email: gno...@redhat.com >> Web: http://fusesource.com >> Blog: http://gnodet.blogspot.com/ >> >> > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: gno...@redhat.com Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
