They are very similar, but a Processor is more limited than using Beans. We can use Processor for simpler use cases that just interact with the Exchange, etc. Also, inline processors in camel route are a great way to interact in route without having to create a separate class.
Beans provide more flexibility and also support a true POJO approach. This allows you to more easily integrate with existing APIs. Good support of annotations like @headers, @header and @body. So most of the exchange items can be accessed Beans also provide great features/flexibility with regards to Camel routing/EIP integration -- View this message in context: http://camel.465427.n5.nabble.com/Preferring-bean-or-processor-invocations-on-a-route-tp5756652p5756666.html Sent from the Camel - Users mailing list archive at Nabble.com.
