From c36174b2636ad3b14ce3e16479dc23667c8e490d Mon Sep 17 00:00:00 2001 From: Juergen Hoeller Date: Sun, 6 Aug 2023 14:59:44 +0200 Subject: [PATCH] Polishing --- .../ROOT/pages/data-access/transaction.adoc | 19 ++++++++----------- .../transaction/ReactiveTransaction.java | 3 ++- 2 files changed, 10 insertions(+), 12 deletions(-) diff --git a/framework-docs/modules/ROOT/pages/data-access/transaction.adoc b/framework-docs/modules/ROOT/pages/data-access/transaction.adoc index 10254968d87..e21a2cd7acf 100644 --- a/framework-docs/modules/ROOT/pages/data-access/transaction.adoc +++ b/framework-docs/modules/ROOT/pages/data-access/transaction.adoc @@ -12,19 +12,16 @@ management that delivers the following benefits: than complex transaction APIs, such as JTA. * Excellent integration with Spring's data access abstractions. -The following sections describe the Spring Framework's transaction features and -technologies: +The following sections describe the Spring Framework's transaction features and technologies: -* xref:data-access/transaction/motivation.adoc[Advantages of the Spring Framework's transaction support model] - describes why you would use the Spring Framework's transaction abstraction - instead of EJB Container-Managed Transactions (CMT) or choosing to drive local - transactions through a proprietary API, such as Hibernate. +* xref:data-access/transaction/motivation.adoc[Advantages of the Spring Framework's transaction support model] + describes why you would use the Spring Framework's transaction abstraction instead of EJB + Container-Managed Transactions (CMT) or choosing to drive transactions through a proprietary API. * xref:data-access/transaction/strategies.adoc[Understanding the Spring Framework transaction abstraction] - outlines the core classes and describes how to configure and obtain `DataSource` - instances from a variety of sources. -* xref:data-access/transaction/tx-resource-synchronization.adoc[Synchronizing resources with transactions] describes - how the application code ensures that resources are created, reused, and cleaned up - properly. + outlines the core classes and describes how to configure and obtain `DataSource` instances + from a variety of sources. +* xref:data-access/transaction/tx-resource-synchronization.adoc[Synchronizing resources with transactions] + describes how the application code ensures that resources are created, reused, and cleaned up properly. * xref:data-access/transaction/declarative.adoc[Declarative transaction management] describes support for declarative transaction management. * xref:data-access/transaction/programmatic.adoc[Programmatic transaction management] covers support for diff --git a/spring-tx/src/main/java/org/springframework/transaction/ReactiveTransaction.java b/spring-tx/src/main/java/org/springframework/transaction/ReactiveTransaction.java index 76cfd8a9186..2c3a03e3785 100644 --- a/spring-tx/src/main/java/org/springframework/transaction/ReactiveTransaction.java +++ b/spring-tx/src/main/java/org/springframework/transaction/ReactiveTransaction.java @@ -1,5 +1,5 @@ /* - * Copyright 2002-2019 the original author or authors. + * Copyright 2002-2023 the original author or authors. * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. @@ -30,6 +30,7 @@ package org.springframework.transaction; * @since 5.2 * @see #setRollbackOnly() * @see ReactiveTransactionManager#getReactiveTransaction + * @see org.springframework.transaction.reactive.TransactionCallback#doInTransaction */ public interface ReactiveTransaction extends TransactionExecution {