Remove Serializable from TransactionInterceptor and TransactionManager [SPR-17044] #21582
Labels
Comments
Juergen Hoeller commented This is by design for the time being, with transaction managers potentially reconnecting themselves to a given runtime environment. The common resource transaction managers cannot do this but Granted, JTA is certainly as out-of-fashion as serialization is today. At some point we might be able to let go of both... but not within our planning horizon yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yanming Zhou opened SPR-17044 and commented
Java serialization is an anti-pattern now, most TransactionManagers rely on DataSource which is not serializable, and neither define
serialVersionUID
norreadObject()
will cause potential exception, I think is time to remove java.io.Serializable from TransactionInterceptor and *TransactionManager. Any one can explain what is the purpose to make them serializable?No further details from SPR-17044
The text was updated successfully, but these errors were encountered: