camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raul Kripalani <>
Subject Re: Camel features and falling-back to Camel components
Date Fri, 02 Mar 2012 08:58:03 GMT

Not that I can think of. That is indeed the beauty of Camel.
Components and the routing EIPs are separated, so creating components
is simple and plug transparently into the engine that Camel provides.

Having said that, you might want to look leveraging the asynchronous
routing engine in Camel. You don't need to think about the EIPs, but
you do need to consider threading aspects.

When it comes to transactions, Camel will automatically open a
transaction with the referenced transaction manager just after the
message is consumed. So if you want the message consumption action
itself to be part of that transaction, you need to provide transaction
support at the endpoint level. And then you would be referencing the
same TransactionManager from the SpringTransactionPolicy (I.e.
transacted DSL element).


On 1 Mar 2012, at 09:11, "E.Gherardini" <> wrote:

> Hello everyone,
> I am developing a RabbitMQ camel component starting from scratch, using the
> RabbitMQ java client as the only basis for the development.
> Aside from the RabbitMQ features I am exposing to the users as options in
> the route (e.g. ?concurrentConsumers),
> I am wondering if there exist general Camel features (e.g. some camel DSL
> keywords) which needs to have some support from the component implementation
> to work properly.
> One of these, I am sure, is the transactional client EIP, with the
> "transacted()" keyword (
> Can someone point me to those, or give me some directions to address my
> reasonings ?
> Thanks a lot.
> Emanuele
> --
> View this message in context:
> Sent from the Camel Development mailing list archive at

View raw message