9.4. Configuring and using transactions

So far, we’ve used convention over configuration when configuring transactions in Camel, by just adding <transacted/> to the route. This is often all you’ll need to use, but there can be situations where you need more fine-grained control, such as when specifying transaction propagation settings.

That’s the first thing we’ll look at in this section. Then we’ll look at how transactions work when multiple routes are used. At the end of the section, we’ll look at how you can return custom responses to the caller when a transaction fails.