Remove java.sql dependencies from ReflectionUtils and TransactionDefinition [SPR-17464] #21996
Comments
Dimitrios Liapis commented Juergen Hoeller I could take a look at this if no-one has picked it up already. How are we planning to replace these two invokeJdbcMethod methods? Removing them on a non-major release would break backwards compatibility, no? |
Juergen Hoeller commented Dimitrios Liapis, I've prepared the first step here already: deprecating Thanks for volunteering, in any case! |
Dimitrios Liapis commented Juergen Hoeller thanks for the details explanation. |
liuming-dev
added a commit
to liuming-dev/compass-x
that referenced
this issue
Jul 9, 2020
fix compatibility after spring version bump and update test units: 1. invokeJdbcMethod was removed from ReflectionUtils, see spring-projects/spring-framework#21996 2. queryForInt was removed from JdbcTemplate, see spring-projects/spring-framework@c1c27e7 3. org.springframework.orm.hibernate3 was removed and renamed to org.springframework.orm.hibernate5 after spring 5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Juergen Hoeller opened SPR-17464 and commented
ReflectionUtils
provides a helper for JDBC method invocations that throwjava.sql.SQLException
, andTransactionDefinition
derives its transaction constants fromjava.sql.Connection
. Both of those can easily be avoided in order to allowspring-core
and the transaction abstraction inspring-tx
to be usable on JDK 9+ images without thejava.sql
module present.Issue Links:
Referenced from: commits c834790, d9c1811, 0a7dcf1
The text was updated successfully, but these errors were encountered: