spring/spring-framework
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-framework.git synced 2026-09-17 16:39:29 +00:00
Code Issues Projects Releases Wiki Activity

Clarify intended nestedTransactionAllowed default in JpaTransactionManager

Browse Source 
Closes gh-35212
This commit is contained in:
Juergen Hoeller
2025-09-10 18:06:44 +02:00
parent 0e3e34bee0
commit 5b387615c6
2 changed files with 10 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spring-orm/src/main/java/org/springframework/orm/hibernate5/HibernateTransactionManager.java
+2 -2
View File
@@ -88,12 +88,12 @@ import org.springframework.util.Assert;
* such a scenario (see container setup).
*
* <p>This transaction manager supports nested transactions via JDBC Savepoints.
* The {@link #setNestedTransactionAllowed} "nestedTransactionAllowed"} flag defaults
* The {@link #setNestedTransactionAllowed "nestedTransactionAllowed"} flag defaults
* to "false", though, as nested transactions will just apply to the JDBC Connection,
* not to the Hibernate Session and its cached entity objects and related context.
* You can manually set the flag to "true" if you want to use nested transactions
* for JDBC access code which participates in Hibernate transactions (provided that
* your JDBC driver supports Savepoints). <i>Note that Hibernate itself does not
* your JDBC driver supports savepoints). <i>Note that Hibernate itself does not
* support nested transactions! Hence, do not expect Hibernate access code to
* semantically participate in a nested transaction.</i>
*
spring-orm/src/main/java/org/springframework/orm/jpa/JpaTransactionManager.java
+8 -7
View File
@@ -93,13 +93,14 @@ import org.springframework.util.CollectionUtils;
*
* <p>This transaction manager supports nested transactions via JDBC Savepoints.
* The {@link #setNestedTransactionAllowed "nestedTransactionAllowed"} flag defaults
* to {@code false} though, since nested transactions will just apply to the JDBC
* Connection, not to the JPA EntityManager and its cached entity objects and related
* context. You can manually set the flag to {@code true} if you want to use nested
* transactions for JDBC access code which participates in JPA transactions (provided
* that your JDBC driver supports Savepoints). <i>Note that JPA itself does not support
* nested transactions! Hence, do not expect JPA access code to semantically
* participate in a nested transaction.</i>
* to "true" but should rather be "false", as nested transactions will just apply to
* the JDBC Connection, not to the JPA EntityManager and its cached entity objects
* and related context. As of Spring Framework 7.0, the default will be "false" in
* alignment with other transaction managers, requiring an explicit switch to "true"
* if you want to use nested transactions for JDBC access code which participates
* in JPA transactions (provided that your JDBC driver supports savepoints).
* <i>Note that JPA itself does not support nested transactions! Hence, do not
* expect JPA access code to semantically participate in a nested transaction.</i>
*
* @author Juergen Hoeller
* @since 2.0