Want to analyze your Java EE applications for a modernization project but don't want to get bogged down in the source code? Much can be learned from the compiled application EAR, WAR, and JAR files by looking at the class byte-code and other files in the archive! Do you want make discoveries like finding hard-coded URLs, figure out if you are ready for the next Java SE version, or get a heads up on the issues might be lurking when you move to a cloud environment? There is a solution!
In this session we will explore the power of tools available to scan your Java EE applications for issues related to Java version differences, Java EE differences, platform differences, potential class-loading issues and more. By looking at byte-code we can help you better understand your applications. And now, you can write your own rules to look for particular issues using a simple XML definition. We will demonstrate writing your own custom rules for analyzing your applications. In addition, we will demonstrate how the Eclipse Transformer can be used for migrating applications to Jakarta EE and show the updates the tool makes to the compiled binaries.
The discussion is relevant to developers and system administrations who are interested in evaluating applications before they are migrated and while making the code changes.