Hi, From an OSGi standards perspective it’s worth pointing out that the Blueprint specification has not been touched since it was first released in OSGi 4.2. There are a few proposed extension RFCs for Blueprint, but none have seen much activity in five years or more.
Declarative Services, however, has been actively extended with new features over the last few specification releases. Annotation-based metadata, type-safe configuration, PrototypeServiceFactory support, field injection support, and dynamic service wiring control using Configuration Admin are all cool DS features that seem unlikely to ever make it into a Blueprint standard. Karaf and Apache Aries have done a lot of work to enhance the Blueprint Container with namespaces and interceptors, however all of these additions are implementation specific and tie you in to that particular stack. This is not a problem for some applications, and is a problem for others. In summary, moving your application from Spring DM to Blueprint will almost certainly be faster to achieve because Blueprint was heavily based on Spring DM. I, however, would use this opportunity to move to DS because the standard is actively being maintained and extended. As further food for thought, the OSGi enRoute project (http://enroute.osgi.org <http://enroute.osgi.org/>) is entirely DS based, and doesn’t offer Blueprint in its platform at all. I wish you all the best with your decision. Regards, Tim > On 18 Mar 2016, at 10:30, Christian Schneider <ch...@die-schneider.net> wrote: > > I have a comparison in my DS tutorial. > > http://www.liquid-reality.de/display/liquid/2015/06/30/Apache+Karaf+Tutorial+part+10+-+Declarative+services > > The main two things missing in DS are the namespaces and the interceptors. In > karaf internally we would not need those. > In a typical user application blueprint is probably still better. > > Christian > > On 18.03.2016 11:24, akuhtz wrote: >> Hello, >> >> I've an application running with spring-dm and because spring-dm is no >> longer developed I'm looking for a replacement. >> >> Now I'm confused because there was a shift in karaf (core) from blueprint to >> DS and today I saw a post on the dev list, saying that DS does not support >> as much as blueprint does. >> As an end-user I would like to know what the proposed way to go is: DS or >> blueprint, both or what else? >> >> >> >> -- >> View this message in context: >> http://karaf.922171.n3.nabble.com/Blueprint-or-DS-or-what-to-use-tp4045845.html >> Sent from the Karaf - User mailing list archive at Nabble.com. > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com >
