From d6be43350140365e72532c05d6b8a680c2976920 Mon Sep 17 00:00:00 2001 From: Juergen Hoeller Date: Tue, 7 Oct 2014 00:43:33 +0200 Subject: [PATCH] Polishing --- .../orm/hibernate4/HibernateTransactionManager.java | 12 ++++++------ .../orm/hibernate3/HibernateTransactionManager.java | 12 ++++++------ .../orm/jdo/JdoTransactionManager.java | 8 ++++---- .../orm/jpa/JpaTransactionManager.java | 10 +++++----- 4 files changed, 21 insertions(+), 21 deletions(-) diff --git a/spring-orm-hibernate4/src/main/java/org/springframework/orm/hibernate4/HibernateTransactionManager.java b/spring-orm-hibernate4/src/main/java/org/springframework/orm/hibernate4/HibernateTransactionManager.java index 32f6101981..2ac8dfb7f5 100644 --- a/spring-orm-hibernate4/src/main/java/org/springframework/orm/hibernate4/HibernateTransactionManager.java +++ b/spring-orm-hibernate4/src/main/java/org/springframework/orm/hibernate4/HibernateTransactionManager.java @@ -81,12 +81,12 @@ import org.springframework.transaction.support.TransactionSynchronizationManager * transaction. The DataSource that Hibernate uses needs to be JTA-enabled in * such a scenario (see container setup). * - *

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 1f5938ae16..7939cf0bc1 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 e71b086213..6734c64618 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 a4308ff32d..761cb5888f 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 -- GitLab