On 22/02/2023 16:28, Andy Seaborne wrote:
Java EE is becoming Jakarta EE as part of the transfer to the Eclipse
Foundation.
APIs javax.* become jakarta.*
This affects the Fuseki war file. The migration should not be
user-visible for Fuseki as a runnable jar file.
Because the war file runs in a webapp container, the container execution
environment matters.
Apache Tomcat version 10 switches from javax.* to jakarta.*.
For the runnable jars, it is matter of rename and switch to Jetty 11.
Jetty version 10 and Jetty version 11 are the same except for the
package renaming.
Who's using Tomcat 9 or earlier to run the Fuseki warfile?
Is there anything stopping you upgrading to Tomcat 10?
We in general use Tomcat 9 or earlier due to the cost of migrating to 10
(sheer number of systems rather than hard blocker). Though, to be fair,
our current production use of fuseki is mostly based on the standalone
version and not the war.
However, we make significant use of embedded fuseki in tests and in some
cases do so with Spring Boot 2. Attempts to migrate some systems to
Spring Boot 3 got mired in many backward incompatibilities so I don't
see us managing to ditch SB 2 wholesale any time soon.
Has anyone tried the Tomcat-provided migration tool?
https://github.com/apache/tomcat-jakartaee-migration
No, sorry.
Dave
