The transactional client pattern, shown in Figure 9.7, refers to messaging endpoints that can participate in a transaction. Fuse Mediation Router supports transactions using Spring transaction management.
Not all Fuse Mediation Router endpoints support transactions. Those that do are called transaction oriented endpoints (or TOEs). For example, both the JMS component and the ActiveMQ component support transactions.
To enable transactions on a component, you must perform the appropriate initialization
before adding the component to the CamelContext
. This entails writing code to
initialize your transactional components explicitly.