Upgrading a Legacy Java EE App with Style

Track: Jakarta EE

Abstract

In the span of several weeks, we took a legacy app that had been running in production for 12 years, moved it to git, mavenized it, upgraded from Java 6 to Java 8, and upgraded from Java EE 5 to Java EE 7. Oh, and did I mention that it uses SOAP, JSP, and JSF 1.2? We did all this with a relatively minor amount of code changes, thanks to the backward compatibility of Java 8 and Java EE. Come to this session to learn how we did it, what issues we ran into, which app server we were using, and why we didn't move to a newer JDK, Java EE 8 or Jakarta EE.

Kito Mann

Kito D. Mann is the Principal Consultant at Virtua, Inc. (http://virtua.tech), specializing in enterprise application architecture, training, development, and mentoring with Web Components, Polymer, Angular, JavaServer Faces, and Java EE technologies. He is also the editor-in-chief of JSFCentral.com (www.jsfcentral.com), co-host of the Enterprise Java Newscast (http://www.enterprisejavanews.com), and the author of JavaServer Faces in Action (Manning). Mann has participated in several Java Community Process expert groups (including CDI, JSF and Portlets) and is also an internationally recognized speaker. He is also a Java Champion and Google Developer Expert in Web Technologies. He holds a BA in Computer Science from Johns Hopkins University.