On JDBC 3.0, this transaction manager supports nested transactions via JDBC 3.0 - * Savepoints. 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 objects. 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 + *
This transaction manager supports nested transactions via JDBC 3.0 Savepoints. + * 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). Note that Hibernate itself does not * support nested transactions! Hence, do not expect Hibernate access code to * semantically participate in a nested transaction. diff --git a/spring-orm/src/main/java/org/springframework/orm/hibernate3/HibernateTransactionManager.java b/spring-orm/src/main/java/org/springframework/orm/hibernate3/HibernateTransactionManager.java index 1f5938ae168da2de3c15f4c94fc5cba41f118f1f..7939cf0bc167bb651599970e3ac11f23d8a5a491 100644 --- a/spring-orm/src/main/java/org/springframework/orm/hibernate3/HibernateTransactionManager.java +++ b/spring-orm/src/main/java/org/springframework/orm/hibernate3/HibernateTransactionManager.java @@ -100,12 +100,12 @@ import org.springframework.transaction.support.TransactionSynchronizationManager * special restrictions with EJB CMT and restrictive JTA subsystems: See * {@link org.springframework.transaction.jta.JtaTransactionManager}'s javadoc for details. * - *
On JDBC 3.0, this transaction manager supports nested transactions via JDBC 3.0 - * Savepoints. 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 objects. 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 + *
This transaction manager supports nested transactions via JDBC 3.0 Savepoints. + * 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). Note that Hibernate itself does not * support nested transactions! Hence, do not expect Hibernate access code to * semantically participate in a nested transaction. diff --git a/spring-orm/src/main/java/org/springframework/orm/jdo/JdoTransactionManager.java b/spring-orm/src/main/java/org/springframework/orm/jdo/JdoTransactionManager.java index e71b0862139288e6c36568df77b79cb025035239..6734c64618d2f69604b8b323fbeb174b4888c991 100644 --- a/spring-orm/src/main/java/org/springframework/orm/jdo/JdoTransactionManager.java +++ b/spring-orm/src/main/java/org/springframework/orm/jdo/JdoTransactionManager.java @@ -73,10 +73,10 @@ import org.springframework.transaction.support.TransactionSynchronizationManager * that acts as "connectionFactory" of the PersistenceManagerFactory, so you usually * don't need to explicitly specify the "dataSource" property. * - *
On JDBC 3.0, this transaction manager supports nested transactions via JDBC 3.0 - * Savepoints. The {@link #setNestedTransactionAllowed} "nestedTransactionAllowed"} - * flag defaults to "false", though, as nested transactions will just apply to the - * JDBC Connection, not to the JDO PersistenceManager and its cached objects. + *
This transaction manager supports nested transactions via JDBC 3.0 Savepoints. + * The {@link #setNestedTransactionAllowed} "nestedTransactionAllowed"} flag defaults + * to "false", though, as nested transactions will just apply to the JDBC Connection, + * not to the JDO PersistenceManager 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 JDO transactions (provided that your * JDBC driver supports Savepoints). Note that JDO itself does not support diff --git a/spring-orm/src/main/java/org/springframework/orm/jpa/JpaTransactionManager.java b/spring-orm/src/main/java/org/springframework/orm/jpa/JpaTransactionManager.java index a4308ff32def27d5daf6e0a7b835224e7f6213ed..761cb5888fd5efef452ee34293b272185546f623 100644 --- a/spring-orm/src/main/java/org/springframework/orm/jpa/JpaTransactionManager.java +++ b/spring-orm/src/main/java/org/springframework/orm/jpa/JpaTransactionManager.java @@ -1,5 +1,5 @@ /* - * Copyright 2002-2013 the original author or authors. + * Copyright 2002-2014 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. @@ -85,10 +85,10 @@ import org.springframework.util.CollectionUtils; * used as known connection factory of the EntityManagerFactory, so you usually * don't need to explicitly specify the "dataSource" property. * - *
On JDBC 3.0, this transaction manager supports nested transactions via JDBC 3.0 - * Savepoints. The {@link #setNestedTransactionAllowed} "nestedTransactionAllowed"} - * flag defaults to "false", though, as nested transactions will just apply to the - * JDBC Connection, not to the JPA EntityManager and its cached objects. + *
This transaction manager supports nested transactions via JDBC 3.0 Savepoints. + * The {@link #setNestedTransactionAllowed} "nestedTransactionAllowed"} flag defaults + * to "false", though, as 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 "true" if you want to use nested transactions * for JDBC access code which participates in JPA transactions (provided that your * JDBC driver supports Savepoints). Note that JPA itself does not support