JB, Thanks for the feedback. Blueprint itself was never a big issue for me or my clients so much as Blueprint/Camel. I’m not sure how big a deal Camel is in the Karaf world writ large. A lot of my concerns are about TDD and also making sure that standards and libraries adopted don’t become deprecated in a couple of years and not being an early adopter either.
I’m at the point with Blueprint that I can use it in a rather minimalist way and can show developers how to write 90% of their tests and code without deploying to the container. And I realize this isn’t a Camel forum so that isn’t party of the Felix/Karaf equation. But the testing with CamelBlueprintTestSupport was flaky for a long time and uses PojoSR under the covers while PAX Exam was slow, verbose, and hard to use. So most developers I ran across just threw in the towel on unit tests and started doing everything by deployment to container and QA’ing by hand. In doing a new prototype on a greenfield I’m trying to get ahead of that and need to do a bit of due diligence on the state of the art. I think Blueprint is fine for most of bootstrap, configuration and export/import of service references. I’m not sure if the XML was ever a good idea for Camel routes but even if it was going to be used it should have been written without the routes being defined in the Camel context itself. That’s a big fly in the ointment for development and testing. Fortunately just using the Java DSL gets around that and standardizes and let’s Blueprint work just fine. The issue with going to DS is that I won’t get the automatic bootstrapping of the Camel context and the configuration that goes along with it. I know how to bootstrap the Camel context from code and worked with an abstract class that does that. But that isn’t really standard practice. A lot of clients have problems finding developers who can work with the technology stack so the closer I can make it hew to a paradigm where Java developers can simply look at a bundle and get what’s going on and do bug fixes, tests, and new development, the better. So that’s where CDI has some attractiveness over Blueprint. Ranx -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
