James,
On 2/11/26 11:49 AM, James H. H. Lampert via users wrote:
I'm not entirely sure how all this affects IBM Midrange installations of
Tomcat.
I don't think I've ever even heard talk of Jakarta support on IBM
Midrange boxes (but I've just asked the nice folks on the Java list at
Midrange.com about it).
Jakarta is entirely a Java thing, so no IBM support would be required.
It's entirely up to the application.
If the application is written using Jakarta APIs, then it will run on
Tomcat 10.1 and later. (This will not be the case for you, since
presumably you are using Tomcat 9 which only supports Java EE.)
If the application is written using Java EE APIs, then you have a few
options:
1. Fix the application. This is the best long-term solution. Often, you
can fix this "just" by swapping JavaEE libraries with their JakartaEE
replacements and then changing imports in your Java source files.
Sometimes it can be more complicated if those "replacements" also made
other changes as they transitioned from JavaEE to JakartaEE.
2. Use the Tomcat Migration Tool as a standalone, uh, tool. Download it,
then run it against your application's exploded-WAR directory or WAR
file and it will produce a JakartaEE0-compatible exploded-WAR directory
or WAR file for you.
3. Use the automated migration process built into Tomcat 10.1 and later.
Instead of putting your exploded-WAR directory or WAR file into Tomcat's
webapps/ directory, put it into the webapps-javaee/ directory instead.
This will just perform option #2 above for you.
YMMV on that automated migration tool. If your application or one if its
dependencies is doing something very tricky, then you may encounter some
problems. As I said, the best long-term solution is to fix the
application. It's probably less effort than you might think.
I've had great success with the automated migration tool, and I
routinely test my application (which is firmly JavaEE-facing) on Tomcat
10.1 by dropping it directly into webapps-javaee/ and it works exactly
the same as it does on Tomcat 9.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
