I don't think there are any awailable yet, and actually I don't expect there to be much of a difference. Both are basically doing the same thing. Blueprint does have an extender that will do the wiring for you, so there might be a "overhead" on the start of the bundle ... but I don't expect there to be an overhead later on, or at least not significant. DS is just a "convenience-wrapper" for standard OSGi technology. During build-time the BND or what ever will transform the annotations to Service-Trackers and Service Registrations.
At the end it boils down to services and service-trackers that are "hidden" for the user, either by a xml syntax and an extender, or an annotation and a build time enhancement. regards, Achim 2014-03-03 22:55 GMT+01:00 asookazian2 <[email protected]>: > Any info on perf metrics on DS vs. BP? thx. > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/performance-metrics-blueprint-vs-declarative-services-in-karaf-3-0-x-tp4032028.html > Sent from the Karaf - User mailing list archive at Nabble.com. > -- Apache Karaf <http://karaf.apache.org/> Committer & PMC OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer & Project Lead blog <http://notizblog.nierbeck.de/> Software Architect / Project Manager / Scrum Master
