Table of Contents
Marks a route as a transaction
The Transacted pattern marks the beginning of a transaction in a route. All of the nodes following the transacted node are included in a transaction. All of the nodes preceding the transacted node are not included in the transaction.
![[Important]](imagesdb/important.png) | Important |
|---|---|
The transaction includes only the currently executing thread. Any message processing done in a subthread will not be included in the transaction. |
The Transacted pattern is usually placed directly following the from endpoint in a route.
However, it can appear anywhere in the route body.
Table 73, “Transacted Properties” describes the properties you can specify using the properties editor.
Table 73. Transacted Properties
| Name | Description |
|---|---|
| Specifies a text description for the node. This description is included in the generated XML file, but it is informational only. It is not used by Apache Camel. |
| Specifies a unique identifier for the endpoint. The tooling automatically generates an id for a node when it is created, but you can remove that id or replace it with your own. The Camel debugger requires all nodes with a breakpoint set to have a unique id. You can use the id to refer to endpoints in your Camel XML file. |
| Specifies a reference to a transaction policy. |