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 <[email protected]>: > 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: [email protected] Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
