Bug#1040226: tomcat10: deployment-time Java EE to Jakarta EE migration fails

[Tamás J.Tóth]

Hi,

I’ve installed the tomcat-jakartaee-migration package, but it still
throws the same exception. Are you sure the JAR file it contains is on
the classpath of Tomcat?

Also, thinking about what I would’ve done if this package was suggested
or even recommended – I probably wouldn’t have installed it. It’s
obvious that it’s suggested to use it if one *doesn’t* want to use the
deployment-time migration, so I would’ve thought that the suggestion is
because of that, not because it’s necessary for Tomcat to work properly.
If you decide to make it only a recommendation or suggestion, please
indicate in the package description of tomcat10 that it’s necessary for
the deployment-time migration.

I realized that I missed an important detail in my report: I ran Tomcat
manually as root using tomcat-start.sh (in a Docker container) rather
than as a systemd service. I don’t have Sid with systemd set up, but
testing on Bookworm with systemd throws a different exception: instead
of a NoClassDefFoundError at HostConfig.java:1243, it already throws an
IOException at HostConfig.java:1232 – it tries to write the
webapps-javaee directory, but only the webapps directory is read/write
enabled in the systemd unit file. After editing the unit file to enable
read/write access for the webapps-javaee directory, the systemd service
also throws the NoClassDefFoundError. Testing on Bookworm by manually
running tomcat-start.sh as root also throws the NoClassDefFoundError.

Regards,
Tamás
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20230704/de893101/attachment.htm>