Apache Camel: do Processors and Beans serve the same purpose?

apache-camel
redben picture redben · May 19, 2011 · Viewed 15.5k times · Source

It seems like both serve the same purpose. Is there any difference that makes one useful in certain situations and not the other ?

Answer

Ben ODay picture Ben ODay · May 20, 2011

In practice, they are very similar, but a Processor is more limited than a Bean. I generally use a Processor for simple use cases that just interact with the Exchange. Also, inline processors are a great way to interact 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 (just need to convert the inputs/outputs to match, etc).

Beans also provide great features/flexibility with regards to Camel routing/EIP integration, including...

Related questions

What exactly is Apache Camel?

I don't understand what exactly Camel does. If you could give in 101 words an introduction to Camel: What exactly is it? How does it interact with an application written in Java? Is it something that goes together with the server? …

Read More
how to convert JSONArray to List of Object using camel-jackson

Am having the String of json array as follow {"Compemployes":[ { "id":1001, "name":"jhon" }, { "id":1002, "name":"jhon" } ]} i want to convert this this jsonarray to List<Empolyee> . for this i had added the the maven dependency "camel-jackson" and also …

Read More
When to use Spring Integration vs. Camel?

As a seasoned Spring user I was assuming that Spring Integration would make the most sense in a recent project requiring some (JMS) messaging capabilities (more details). After some days working with Spring Integration it still feels like a lot …

Read More