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
