this is more of a heads up than an issue per se, but it is bound to happen when old servlet containers reach EOL, or when people want to deploy VOLLT in the newest version(s) of servlet containers like Tomcat.
Jakarta EE (formerly Java EE) has had a namespace change from javax.servlet to jakarta.servlet starting from the Servlet 5.0 API. As such, newest servlet containers will not find the associated classpath. This is a breaking change and old code will not work out of the box; which is quite counterproductive.
As a measure, Tomcat has developed a tool which allows to make Java EE applications Jakarta EE compatible. I think it could be useful to note it on the readme file in order to make people aware instead of wondering why their deployment returns a 404 error.
Hi,
this is more of a heads up than an issue per se, but it is bound to happen when old servlet containers reach EOL, or when people want to deploy VOLLT in the newest version(s) of servlet containers like Tomcat.
Jakarta EE (formerly Java EE) has had a namespace change from
javax.servlettojakarta.servletstarting from the Servlet 5.0 API. As such, newest servlet containers will not find the associated classpath. This is a breaking change and old code will not work out of the box; which is quite counterproductive.As a measure, Tomcat has developed a tool which allows to make Java EE applications Jakarta EE compatible. I think it could be useful to note it on the readme file in order to make people aware instead of wondering why their deployment returns a 404 error.