No, you don't have to concern yourself with any of that. That is the
very point, camel takes care of all of it. The only concern you would
have is to implement a component that deals with the rabbitmq
technology, i.e. define the endpoint and its configuration and the
necessary producers and consumers.
Even that you may not need/want to do, because there is something
already available (outside the ASF distro)  from lshift . I
briefly took a look at it some 6 months ago, and it needs more work, but
it's a good start. What is not clear (to me) is under what license the
authors made available the code.
> Hi all,
> I'm very new to Camel.
> I have to define a Camel component for RabbitMQ.
> I'm investigating on definition of routes and its impact on my component.
> For example if I apply a filter on a route
> I suppose that it hasn't an impact on my component (I mean I don't have to
> manage the filtering in my rabbitmq camel component code).
> What about multicast? Do I have to manage it?
> For example: from("jms:xmlOrders").multicast().to("jms:accounting",
> Do I have to intercept the multicast request in some way or is the camel
> context that manages it?
> View this message in context: http://camel.465427.n5.nabble.com/Camel-and-RabbitMQ-tp5525547p5525547.html > Sent from the Camel Development mailing list archive at Nabble.com.