One distinction not mentioned by Ben and Petter is that properties are safely stored for the entire duration of the processing of the message in Camel. In contrast, headers are part of the message protocol, and may not be propagated during routing. For example, JMS has limitations what you can store as headers etc. You … Read more
It’s important to remember that an Endpoint, created by a Component (i.e. Endpoint Factory), can sit at either end of a Camel Route. If you put the Component at the start of a route then there must be an implementation of the Consumer part of the Component. This does the work of converting the specific … Read more
The problem is not in your code but in your json: {“Compemployes”:[{“id”:1001,”name”:”jhon”}, {“id”:1002,”name”:”jhon”}]} this represents an object which contains a property Compemployes which is a list of Employee. In that case you should create that object like: class EmployeList{ private List<Employe> compemployes; (with getter an setter) } and to deserialize the json simply do: EmployeList … Read more
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 … Read more
The “direct:start” above is simply saying that the route starts with a Direct Component named “start”. The direct endpoint provides synchronous invocation of a route. If you want to send an Exchange to the direct:start endpoint you would create a ProducerTemplate and use the various send methods. ProducerTemplate template = context.createProducerTemplate(); template.sendBody(“direct:start”, “This is a … Read more
ActiveMQ is a message broker which implements the JMS API and supports a number of cross language clients and network protocols. It lets you implement queues or topics and write listeners or subscribers to respond to queue events. Mule and ServiceMix are open source ESB (enterprise service bus). An ESB has capabilities beyond JMS: queuing … Read more
there is a working example of doing nearly the same thing here… http://camel.apache.org/cxf-proxy-example.html start with this, then drop your changes in one-by-one and see where it breaks…
It is now 2016 and a lot has changed since the question was initially asked, so I’d like to revisit it for new viewers. Strategically speaking Apache Camel has stayed true to its roots and has not evolved into a heavyweight nor fully-fledged runtime platform. It is versatile and modular, and can run: Embedded in … Read more
We choose Camel over Spring-Integration because the fluent API is really nice. We actually use it in Spring projects and use Spring to configure part of it. The programming API’s are clear and there is a large set of sensible components. We did a small scale shootout and basically at that time for our requirement … Read more
My take to describe this in a more accessible way… In order to understand what Apache Camel is, you need to understand what are Enterprise Integration Patterns. Let’s start with what we presumably already know: The Singleton pattern, the Factory pattern, etc; They are merely ways of organizing your solution to the problem, but they … Read more