Jump To Close Expand all Collapse all Table of contents Managing JTA transactions with the Quarkus transaction manager Preface Providing feedback on Red Hat documentation Making open source more inclusive 1. Prerequisites 2. The Narayana JTA transaction manager and Quarkus 3. Installing the Quarkus Narayana JTA extension 4. Managing JTA transactions declaratively using the annotations Expand section "4. Managing JTA transactions declaratively using the annotations" Collapse section "4. Managing JTA transactions declaratively using the annotations" 4.1. Defining transaction boundaries declaratively 4.2. Configuring a transaction for rollback declaratively 4.3. Configuring a transaction timeout declaratively 4.4. Methods returning reactive values 5. Managing JTA transactions programmatically using the API approach Expand section "5. Managing JTA transactions programmatically using the API approach" Collapse section "5. Managing JTA transactions programmatically using the API approach" 5.1. Defining transaction boundaries using the API approach 5.2. Configuring a transaction for rollback using the API approach 6. Overwriting the default transaction timeout 7. Configuring the transaction node name identifier for XA transactions 8. Overview of Quarkus transaction configuration properties Legal Notice Settings Close Language: 简体中文 日本語 English Language: 简体中文 日本語 English Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Language and Page Formatting Options Language: 简体中文 日本語 English Language: 简体中文 日本語 English Format: Multi-page Single-page PDF Format: Multi-page Single-page PDF Managing JTA transactions with the Quarkus transaction manager Red Hat build of Quarkus 1.11Legal NoticeAbstract Use the Narayana JTA extension to manage transactions in your Quarkus application. Next