Paul, I agree. I've used Blueprint for a long time and it is a thorny with Camel. I've limited my use of Blueprint these days to 1) configuration, 2) service management, and 3) bootstrap. If one keeps in minimal like that Blueprint is fine. But I've gone into a lot of different clients where they have reams of opaque Blueprint XML and Processors/Exchanges and even bright developers are struggling to understand it. Inevitably unit testing in those cases is non-existent. There are a three or four primary reasons testing gets jettisoned in that case. If one switches to using the Camel Java DSL and Java pojos for handlers, those problems melt away and Blueprint becomes tractable.
-- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
