Due to key SPI interfaces such as ConnectionProvider and JtaPlatform changing their package location in Hibernate 4.3, we have to resort to reflection in a few places. Most importantly, the ConfigurableJtaPlatform used by the setJtaTransactionManager method has now been redesigned as a reflective proxy.
Issue: SPR-10839
@ -140,7 +139,7 @@ public class LocalSessionFactoryBuilder extends Configuration {
@@ -140,7 +139,7 @@ public class LocalSessionFactoryBuilder extends Configuration {
@ -149,7 +148,8 @@ public class LocalSessionFactoryBuilder extends Configuration {
@@ -149,7 +148,8 @@ public class LocalSessionFactoryBuilder extends Configuration {
@ -158,12 +158,13 @@ public class LocalSessionFactoryBuilder extends Configuration {
@@ -158,12 +158,13 @@ public class LocalSessionFactoryBuilder extends Configuration {
"Can only apply JtaTransactionManager which has a TransactionManager reference set");
@ -44,7 +44,7 @@ public class SpringSessionContext implements CurrentSessionContext {
@@ -44,7 +44,7 @@ public class SpringSessionContext implements CurrentSessionContext {
@ -53,9 +53,17 @@ public class SpringSessionContext implements CurrentSessionContext {
@@ -53,9 +53,17 @@ public class SpringSessionContext implements CurrentSessionContext {
thrownewIllegalStateException("Could not introspect Hibernate JtaPlatform for SpringJtaSessionContext",ex);
}
}
@ -79,7 +87,7 @@ public class SpringSessionContext implements CurrentSessionContext {
@@ -79,7 +87,7 @@ public class SpringSessionContext implements CurrentSessionContext {
// Switch to FlushMode.AUTO, as we have to assume a thread-bound Session
// with FlushMode.MANUAL, which needs to allow flushing within the transaction.