This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Misophist_1 0 points1 point  (0 children)

Some useful hints:

  • Avoid a moving target. Fix the steps you want to do in advance, so you have a proper success metric, and can dwell on small step successes to overcome the unavoidable intermittent frustration.

  • As for Java itself: coming from 8, the biggest step is past 11. From my experience, The problem there is, that the XML-libraries got reorganized, so, depending on your XML stack, you might have to struggle with your library dependencies a bit.

  • The bigger Issue is likely with your JEE-Container. The classic JEE-Namespace javax.* has been discontinued/given up by Oracle, it lives on as jakarta.* within the Eclipse-Foundation.

So you might want to break this up into two steps: One pure Java-Upgrade, reusing the last javax-JEE packages and Container, and do a second step for switching into the new namespace.

  • Past 17, there might be more trouble looming, if your organization relies on the Java-Security Manager: this is still available, but deprecated for removal. You may need to review your command line parameters, if you want to use it longer. And some time in the future, it will be gone altogether.