Hear, hear! My one hope for the new book is that the emphasis is on using POJOs for most message processing in lieu of using Processors. I've found that once my clients understand how Camel can select a method for invocation on a bean for a route and how easy that makes unit testing for constituent pieces a lightbulb goes on and they feel like Plain Ol' Java Programmers once again. An almost audible sigh of relief goes up. And not using the Processors means I also see less of the tendency to use Camel as something to read a file or endpoint in and then write a humongous application with I/O inside a processor and let Camel do the heavy lifting using the EIPs and components.
I'd save the intricate details of Processors for a more advanced topic in the later chapters. Brad On Fri, Sep 23, 2016 at 8:30 AM, jpeschke <pesc...@etone.de> wrote: > Hello, > I started learning Camel from scratch about two years ago and read "Camel > as > action" at the beginning. I can confirm that "Camel in Action" offers still > a very good point to start. I knew nothing about Camel or EIPs in general > and just bought the book to see if Camel could provide some nice features > for the application I was going to build (and yes, it could indeed :)). > > The book has a very clear didactic & straight-forward approach. Most of the > described topics stayed the same, more or less - if you develop a Camel > application, you may want to use the Camel website as your main reference, > because you often need very special endpoints/properties/features that > aren't documented in the book or where replaced by more flexible ones. But > to understand the basic idea behind camel, to understand what is good > practice (and what isn't), the book's perfect. > > Joerg > > > > -- > View this message in context: http://camel.465427.n5.nabble. > com/Camel-in-Action-Book-tp5787674p5787965.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
