Upgrading a Legacy Java EE App with Style
summary
A 12‑year production monolith of 550,000+ lines of Java and ~550 web pages moves from MKS to Git, from Java 6 to Java 8 and Java EE 5 to Java EE 7, keeping SOAP/JSP/JSF1.2 intact because JAX‑RPC forces staying on WebSphere 9; code is minimally changed, Maven replaces Ant with delegated tasks, builds run in Docker via Jenkins and Bitbucket, Okta replaces legacy IAM with custom servlet filters for SOAP and web flows, documentation and tests increase, and the upgraded system runs in production.
AI-written summary · about
chapters (10)
- 0:00Introduction and setup
- 2:09Legacy Java EE project background
- 8:17WebSphere upgrade challenges
- 12:33Backwards compatibility and minimal changes
- 14:56Security integration with Okta
- 19:27Testing and QA in legacy projects
- 22:17Documentation and version control fixes
- 26:50Build system and CI/CD modernization
- 33:14Key takeaways and lessons learned
- 36:03Audience Q&A on migration strategies
related talks
55mModernizing Legacy Code - While Not Bringing Down Prod
48mTo JAR Hell And Back - A Live Migration to the Java 9
44mFighting the Technical Debt of GlassFish
58mJourney to the Cloud - a Rearchitecting Story
43mFrom a legacy monolith to a scalable SaaS application
38mHow to Make Unmaintainable Project Maintainable - GlassFish Example
54mTesting in Legacy: From Rags to Riches
40mModernizing the Legacy