On 2 September 2016 at 11:30, Timothy Ward <timothyjw...@apache.org> wrote:
> As things stand currently blueprint is most widely used for working with > Camel. From what I can tell configuring Camel is horrible, and my > understanding is that the main advantage of blueprint is that there is a > huge amount of ready-built Camel integration available. If Camel had a > nicer, container agnostic configuration mechanism then I would see little > reason to choose blueprint over DS. > This right here is exactly how I feel. If there was a well supported way of simply using DS instead of Blueprint with Camel, then I'd drop Blueprint in a single sprint and never look back.
