James,
On 2/25/25 11:59 AM, James H. H. Lampert wrote:
On 2/25/25 8:26 AM, Chuck Caldarale wrote:
Jakarta EE - all the related javax classes have been renamed to jakarta.
https://tomcat.apache.org/whichversion.html
Thanks. I've just asked the Java list over at Midrange.com about how
this affects running Tomcat 10 on an IBM Midrange box.
What effect (if any) does this have on the construction of webapp contexts?
Briefly, here's the deal with the Java EE -> Jakarta EE transition.
1. All "EE" related standards have released new versions, all of which
changed the package names from javax.foo to jakarta.foo
2. Your web application developers should do a migration as soon as is
practical. This can be complicated, due to the chicken-and-egg situation
that many core libraries are experiencing. Notably, there isn't enough
user demand to create libfoo.jakarta from libfoo.javaee so it doesn't
exist, yet. Users don't want to migrate to appfoo.jakarta because
libfoo.jakarta doesn't exist, so there is no demand on libfoo to create
libfoo.jakarta. *sigh*
3. Tomcat has a migration tool that can magically migrate
a. Individual libraries
b. Whole web applications
You can use 3(a) to manually-migrate your dependencies, then migrate
your application along with that. It allows you to break the
chicken-and-egg cycle and start leaning on libfoo to produce a Jakarta
EE-compatible version. Note that migrating a JAR file will completely
break its cryptographic signature, so if you NEED signed JARs, then this
isn't an option for you.
You can use 3(b) to migrate your whole web application, dependencies and
all, to Jakarta EE and with very few exceptions, it will Just Work.
4. Tomcat 10 and later have #3 above built-in. You can drop your
JavaEE-compatible WAR file into webapps-javaee/ instead of webapps/ and
Tomcat will automagically migrate your application during deployment.
This allows you to upgrade past Tomcat 9 without re-writing your
application if you really REALLY do not want to do that migration work.
But honestly, it's just a search-and-replace and update-dependencies
exercise.
... I say this as an application developer who is struggling with the
same thing you are: some dependencies just aren't there, yet, so I'm
contemplating migrating their JAR files and moving on with my life.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
