-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate to Spring 5 #116
Comments
(I don't think any of the security issues are relevant to us) |
That was a long time ago, but the migration to Spring 5 for rgr went smoothly. The biggest concerns for Gemma is the breaking changes in spring-security from 3 to 4 and the lack of support for Hibernate 3. Spring 4 still supports Hibernate 3 and would allow us to focus on security-related changes. Then migrating to Spring 5 would be a major overhaul of the DAO layer. |
Spring 3, 4 and 5 all support Hibernate 4 and with #351, we can relatively easily make this move as it will be just a matter of changing our bean configurations. |
I just finished and merged Spring 5 (via Spring Boot 2.6.8) migration for RDP PavlidisLab/rdp@ca4799d. I'll do a recap next dev meeting. |
I stand corrected, Spring 5 requires Hibernate 5 as a minimum. |
Spring 4 has just reached end of life, so this is long overdue.
HibernateDaoSupport
, the session factory can be injected directly in BaseDao, and we can rely on Hibernate API directly like we currently do for nearly all use cases (this involves a few HibernateTemplate replacements)I have started investigating Spring 4 to 5 migration in PavlidisLab/rdp#65 before the holidays. rgr shares numerous dependencies with Gemma and I think it would be preferable to migrate it first just to get an idea of the process at a smaller scale.
The text was updated successfully, but these errors were encountered: