François I'm looking forward to "winegrower". So tantalizing. I guess if you've got the Cellar you need some wine to put in it.
You're right, the beauty of Karaf/Felix is that you have all these options. It's also a downside and it becomes even more of a downside when you start throwing technologies like Camel and Camel Blueprint DSL into the mix. I think it's OK to support a lot of paradigms but obviously when I'm making a recommendation to a client about an architecture, practices, procedures, development, testing, and so on, it has to be a standard that the organization is going to use. Using multiple paradigms isn't going to go over very well as there is already a lot to take in. While I think SpringBoot is on the wrong track as an approach, I will say that I do think their taking an opinionated approach to development, testing, documentation and code samples is acceptable and preferable. Let's hypothesize that the folks in charge of Apache Karaf decided that from now on, all code samples would used CDI/DS and its use, testing and practices would be rigorously documented. That wouldn't mean that Blueprint was abandoned or unusable. The cacophony of documentation and code samples is deafening in the OSGi/Karaf/Camel world. If Karaf provides a lot of options, Camel does that in spades and putting the two together is a square of the problem. I'm not sure how may Camel users exist in the Karaf/Felix world but I run into this so frequently I've actually thought of setting up tutorials and code samples to show simple/easy to follow mechanisms (if only I had a spare minute). -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
