Remove early adaptation to JTA 2.1 setReadOnly method
The UserTransaction read-only semantics are still in discussion. If they turn out to be stricter than Spring's read-only hint, we should only apply them when configured with an explicit enforceReadOnly=true flag at the Spring JtaTransactionManager level (similar to the same-named flag in DataSourceTransactionManager).
See gh-35915
See gh-35633
@ -143,10 +139,6 @@ public class JtaTransactionManager extends AbstractPlatformTransactionManager
@@ -143,10 +139,6 @@ public class JtaTransactionManager extends AbstractPlatformTransactionManager
@ -866,12 +858,6 @@ public class JtaTransactionManager extends AbstractPlatformTransactionManager
@@ -866,12 +858,6 @@ public class JtaTransactionManager extends AbstractPlatformTransactionManager
@ -918,21 +904,6 @@ public class JtaTransactionManager extends AbstractPlatformTransactionManager
@@ -918,21 +904,6 @@ public class JtaTransactionManager extends AbstractPlatformTransactionManager
@ -1190,14 +1161,6 @@ public class JtaTransactionManager extends AbstractPlatformTransactionManager
@@ -1190,14 +1161,6 @@ public class JtaTransactionManager extends AbstractPlatformTransactionManager
@ -41,8 +41,6 @@ public class JtaTransactionObject implements SmartTransactionObject {
@@ -41,8 +41,6 @@ public class JtaTransactionObject implements SmartTransactionObject {