I have a question about Apache Camel. I wasn't able to find whether the multicast is transacted. If it is transacted, how the transactions are implemented? what is the transaction boundary?
The Multicast EIP allows to route the same message to a number of endpoints and process them in a different way. The Multicast EIP has many features and is also used as baseline for the Recipient List and Split EIPs.
If noop=true, Camel will set idempotent=true as well, to avoid consuming the same files over and over again. Expression (such as File Language) used to dynamically set the filename when moving it before processing. For example to move in-progress files into the order directory set this value to order.
A transacted Camel route creates a transaction scope around the whole route (1) or more specific the unit of work. Let's take an example: a route that reads from a JMS queue, transforms the data and writes to multiple other JMS queues.
You save the original body in an property and also the body from endpoint1. You then send the exchange to direct:req2 with the original body in the exhcnage body and the body form endpoint1 in a property which you then can access (in you processor or else where). Save this answer. Show activity on this post.
It is transacted, the boundary is the whole route, as if you weren't using multicast. You can see this discussion thread for more details: http://camel.465427.n5.nabble.com/Transaction-and-Multicast-or-to-AND-to-td476483.html
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With