-
Enhancement
-
Resolution: Done
-
Minor
-
1.17, 2.1
-
None
-
False
-
None
-
False
Not defining driverClassName leads to non-proper XAResource usage in pool implementation, therefor determination via Spring internal tooling helps to get better DataSource configuration.
NarayanaTransactionIntegration is actually lacking LRCO availability and not naming could cause issues with multiple DataSources
- causes
-
AG-220 Do not register RecoveryRegistry when not applicable in Spring Configuration
- Closed