Using AMQ redelivery has the benefit that the messages is already persistent in the broker.
So in case of server crash, server stopped during redelivery etc. Then when restarting the broker, the messages is not lost, and it can simply continue from where it left.
If you use Camel to do the redelivery, then the messages is in memory only. So in case of a server crash, that message is lost.
Camel redelivery makes sense to use when you do not use AMQ.
I just released some source code as a working example, that others might find helpful.
== ServiceMix OSGi Aries Blueprint Atomikos Beans ==
== Atomikos + Camel Integration to achieve XA Transactions ==
My Camel configuration using these Atomikos beans is here:
== Atomikos + Pojo Service Integration to achieve XA Transactions ==
My Service configuration using these Atomikos beans is here:
As I am deploying to the ServiceMix 4.4.x environment and as such I had to use do my manual transaction management, which is given here:
Thanks for sharing this with us.