Camel riders, I've been working on various approaches to a message-driven solution here at $WORK for quite some time, and I must say first of all that I totally love Camel.
That said, sometimes I find myself constantly refactoring my solution, because Camel offers so many different approaches to solve a problem. One particular thing that I'm struggling with is whether or not to refactor a set of subclasses I've written that extend Processor explicitly into something that's more flexible (and even more unit-testable) using Camel's POJO Bean Binding. For those who have written solutions: which do you find yourself using? Camel's bean binding, or explicit Exchange handling? --sgp
