We use Blueprint mainly to have a code which makes use of services but without dealing with OSGi or annotations (as far as possible => few wappers). As long with the maven-bundle-plugin it is a kind of magic. I would say Blueprint+Maven+Karaf makes things really easy.
I would suggest to make a simple but representative example using CDI, DS, and Blueprint. Take time to have a full picture with you editor, plugins and compilation / assembly. See what is means in terms of effort to make, and think about what it would cost to enhance and maintain. JP -----Message d'origine----- De : akuhtz [mailto:andreas.ku...@gmail.com] Envoyé : vendredi 18 mars 2016 11:24 À : user@karaf.apache.org Objet : Blueprint or DS or what to use? 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.
