You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Connection
- Doodle:
- Date: 2022-10-XX – XX:XX UT
- Zoom details will be sent out in an e-mail
Participants
Agenda
Discussion
- Should ACS forward the cbStop callback to the receivers when coming from the unexpected StartState / StopState states?
-
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Java 17 Upgrade
- Migration Plans - Java 17
- Target is 2023APR
- Offline docker images should upgrade the provided Java version around the time
- Applications explicitly defining source/target/release version could be transitioned gradually
- Java EE / Jakarta EE
- Migration Plans - Jakarta EE
- The proposal is to provide both package version of the APIs with ACS for a transition time (1 or 2 cycles at least)
- Hibernate 6.x / Spring 6.x
- This needs to be an observatory-wide transition
- Hibernate 6 is working fine
- Spring Framework 6 is working fine
- Migration Plans - Spring Framework 6
- Not yet officially released
- 6.0.0-RC1: Base libraries
- 6.0.0-M6: Security libraries
- 5.8.0-M2: Security CAS
- 3.0.0-RC1: LDAP
- Small configuration changes + discourage use of HibernateTemplate
- NullPointerException → Could be fixed by changing some configurations that ended up breaking other parts of the applications
- The official recommendation is to stop using HibernateTemplate anyway
- getHibernateTemplate().<save,delete,get,saveOrupdate,etc.>() → getSessionFactory().getCurrentSession()
- getHibernateTemplate().execute(...) → getSessionFactory().fromSession(...)
- TMCDB Explorer as test application
- Biggest pain was to replace Hibernate Criteria API by JPA's Criteria API
- Several smaller changes in code and configuration
- Additional unexpected changes in default configuration values and default behavior
- After several tweakings, TMCDB Explorer is working fine in all the use cases tested
Short Term (2022DEC)
- Maintenance (Bug-fixing / Improvements)
- Obsolescence Management
- No obsolescence management since 2022AUG is bug-fix only release
- Progress towards Java 17 / Jakarta EE / Hibernate 6.x / Spring Framework 6.x / Spring Boot 3.x
- Continue NC implementation study – 2022DEC
- Implement Java + C\+\+ code coverage mechanics – 2022DEC
- ComponentCaller API Security Implementation – 2022DEC
Mid Term (2023FEB --> 2023APR)
- Java 17
- Jakarta EE / Hibernate 6.x / Spring Framework 6.x / Spring Boot 3.x – 2023APR → 2023JUN
- C++ Modernization
- Logging Service refactoring/change of technology – 2023FEB → 2023AUG
- Development and Community OS Support
- Jenkins Build + Phase A tests
Long Term (TBD)
- Java 17 – 2023APR+
- Will be scheduled for some point during 2023 aiming to Cycle 11 (2024-10 deployment) – 2023APR+
- Jakarta EE 9+ / Hibernate 6+ / Spring 6+ / Springboot 3+ / Tomcat 10+ (Java-17 and Jakarta EE 9 baseline for spring framework 6) – 2023JUN+
- ACS Services Modernization
- ZeroMQ-based BulkData transfer implementation
- CDB API alternative (REST, SOAP, G-RPC, Falcor, ICE, etc.)
- Logging system technology replacement (Boost::Log, etc.)
- Interface Repository (???)
- Naming Service (???)
De-scoped:
Not Relevant
Conclusions
2022DEC
* Tentative base for 2022DEC until the meeting has been held
issuekey |
summary |
issuetype |
created |
updated |
duedate |
assignee |
reporter |
priority |
status |
resolution |
Unable to locate Jira server for this macro. It may be due to Application Link configuration.
|
Priorities
- Maintenance
- Testing Coverage Work
- Component Caller API Security Implementation
- NC Implementation Study
- Obsolescence Management
Action Items