+-0 for a switch to DS ... I don't really mind ... plain old OSGi ServiceTrackers (POOST) are fine with me, and the same applies for Bueprint and DS
regards, Achim 2016-02-09 13:30 GMT+01:00 Morgan Hautman <[email protected]>: > +1 seems logic. > We also have some DS examples for Karaf-boot so scr IMHO should even be > installed by default because sometimes it confuses users (even myself).. > but i don't know how you guys feel about it.. > > > On 02/09/2016 01:22 PM, Christian Schneider wrote: > >> I recently discussed with JB that the boilerplate code in decanter >> increases. One typical example is that a decanter module needs to reference >> EventAdmin, the Marshaller service and react on configurations. In many >> cases we also need to be able to work with ManagedServiceFactories. >> >> So for this case DS seems like a good idea. It can do all of the above >> with very simple annotations and can now also do type safe configs. >> >> The only disadvantage is that we then need the scr feature. As it is >> quite small I think this is a good tradeoff. >> >> What do you think? >> >> If there is no push back then I would like to switch decanter to DS once >> the decanter release 1.0.2 is done. JB then wants to switch the master to >> 1.1.x which allows us to do some more changes then in a bugfix line. >> >> Christian >> >> > -- Apache Member 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/> Co-Author of Apache Karaf Cookbook <http://bit.ly/1ps9rkS> Software Architect / Project Manager / Scrum Master
