support for Tomcat 10 / Jakarta EE

[cseppan]

Tomcat 10 uses the jakarta. namespace instead of javax.. This is due to the move from Java EE 8 to Jakarta EE 9+.

Tasks

• Understand how Java EE 8 is used in the EMF code and dependencies
• Update library dependencies to newer versions which use Jakarta (Hibernate 6, Spring 6, etc.)
• Identify older dependencies (Axis 1.4) that don't have an upgrade and determine migration path
• Convert namespace in EMF code - Tomcat has a migration tool: https://github.com/apache/tomcat-jakartaee-migration

Interim options

• Stick with Tomcat 9 (still active, no end-of-life date announced yet)
• Run the EMF server under Tomcat 10 using Tomcat's automatic conversion:

  Tomcat can convert an existing web application from Java EE 8 to Jakarta EE 9 at deployment time using the Apache Tomcat migration tool for Jakarta EE. To make use of the feature, the web application should be placed in the Host legacyAppBase folder (by default named webapps-javaee) and they will be converted to an equivalent Jakarta EE web application in the Host appBase folder (by default named webapps).

In my dev setup, the deploy-time conversion is working and I haven't run into problems during my limited usage (log in, view datasets, view data for a dataset, export a dataset with automatic download).