Upgrade Meeting for Architecture Working Group: Spring 2 Issues, Spring 3 Benefits, and Oracle Migration
Table of Contents
- 1. Meeting
- 2. System upgrade (JVM, Tomcat, Spring)
- 2.1. Spring 2 issues
- 2.2. Some Spring 3 code is already in place
- 2.3. Spring 3 benefits
- 2.4. However, annotations can be a cause for concern
- 2.5. Move to JVM 7; what's required?
- 2.6. The schedule for moving from Resin
- 2.7. Options for deprecation
- 2.8. Business support is required to deprecate features
- 2.9. Effects on Oracle migration with app deprecation
- 2.10. New features will require upgrades to JVM and Tomcat
- 2.11. Dependency management becomes much easier w/o Resin
- 2.12. Major refactoring may force a sprint-long code freeze
- 2.13. Scheduling
- 3. Oracle migration
- 4. Collections/Collectables/Actionable Object Collection
- 5. Roadmap
1. Meeting
- Attendees: To: "jin.kim@memorylane.com" <jin.kim@memorylane.com>, "Davidson, Steven" <Steven.Davidson@memorylane.com>, "Davis, Lee" <Lee.Davis@memorylane.com>, "Skillen, Paul" <Paul.Skillen@memorylane.com>, Jason Walsh
- When: 3:00 PM - 4:00 PM January 12, 2012
- Subject: Architecture Working Group
- Location: Conf. SEA - Scream 6- 8 5335 <Conf.SEA-Scream@classmates.com>
2. System upgrade (JVM, Tomcat, Spring)
2.1. Spring 2 issues
2.1.1. Interceptors for controllers fragile
Forms: POST -> authentication -> SAT
Spring 2.5.6 requires monolithic interceptors.
If someone sets up the default controller the security is lost.
Spring 3.1 allows annotations on the controllers for multiple interceptors.
2.2. Some Spring 3 code is already in place
For tiles integration.
2.4. However, annotations can be a cause for concern
JPA mappings nearly difficulty.
2.5. Move to JVM 7; what's required?
Will require moving off of Resin before the jump to 7.
Current work is for moving search off of Resin.
Message boards are tentatively scheduled for deprecation.
The road-map includes references to "message board" that likely diverge.
2.6. The schedule for moving from Resin
2.6.1. Search
2.6.2. Photos
Likely just a technical debt issue.
No more presentation. Just supports the actual processing of the photos. There are fewer photos being uploaded as well.
2.6.3. Community (workplace, military, and neighborhood)
There was a comment of just noting that the person was in the military rather than a full affiliation.
2.6.4. Profile
As long as go/x isn't still present this could be done.
2.6.5. Directory
Being ported now (Titans).
2.7. Options for deprecation
2.7.1. EOL but available
Keep it available but have no upgrades.
Use all the new JDK and Tomcat.
2.7.2. Migrate
Not an active support. For example, header changes.
Things like trivial UI changes: link updates could still be done but core couldn't be rebuilt.
2.8. Business support is required to deprecate features
If deprecation occurs early then some of the upgrade work may just go away.
2.9. Effects on Oracle migration with app deprecation
For example, data migration of message boards. Data is threaded message by community including private communities.
2.10. New features will require upgrades to JVM and Tomcat
2.10.1. Tomcat 7: servlet
2.10.2. Async HTTP
2.11. Dependency management becomes much easier w/o Resin
No more dual builds.
2.12. Major refactoring may force a sprint-long code freeze
Could be other options but the merge locations may just go away.
This would largely just be about core.
2.12.1. Shouldn't affect UI changes
2.12.2. Would also require regression testing
Some work has already been done for the integration testing of services but this would need to be part of the planning.
2.13. Scheduling
2.13.1. Starting only depends on the deprecation
Splitting up core and Spring upgrade.