Please prioritize release to registry1.dsop.io

The other released tomcat containers all use version 10. Tomcat version 10 breaks backward compatibility with most existing web frameworks (such as Spring) since they are based on different servlet specs. Tomcat 9 and prior support the javax.servlet package used by most existing web frameworks, where as Tomcat 10 makes a breaking change to the jakarta.servlet package.

The result for developers is that the Tomcat 10 server works (starts up fine), but when most web applications are deployed, they are not recognized and you get endless 404 errors because nothing gets deployed. Since there is a huge volume of existing .war files that will never work with tomcat 10, please prioritize the release of tomcat 9 based images.

I've done some preliminary testing with the tomcat:latest (which is Tomcat 9 - search for 'latest' tag) image from Docker Hub and some of our existing .war files are deploying/running as expected. When switching the the IronBank or Docker Hub tomcat 10 versions we get endless 404 errors.

Here's the relevant references for what I'm talking about if needed for justification.

Change in servlet api from tomcat 9 to tomcat 10

• http://tomcat.apache.org/whichversion.html
• https://tomcat.apache.org/download-10.cgi
• http://tomcat.apache.org/migration-10.html#Servlet_5.0_API
• https://github.com/apache/tomcat-jakartaee-migration

Spring Framework (latest 5.3.3) only works with older server spec (3.x/4.x)

• https://github.com/spring-projects/spring-framework/wiki/What%27s-New-in-Spring-Framework-5.x
• https://github.com/spring-projects/spring-framework/blob/master/spring-web/spring-web.gradle
• https://github.com/spring-projects/spring-framework/issues/25354

TL;DR Without getting a Tomcat 9 image released, I don't think many java-based web applications will be able to run on the IronBank containers.