The move from Java EE to Jakarta EE means some updating of package names. Example: what was “javax.servlet.*” in Java EE now is “jakarta.servlet.*” in Jakarta EE. – Maybe you already have experienced this when installing existing applications with Tomcat 10 – having received corresponding ClassNotFound-exceptions…
CaptainCasa as framework now comes in two variants:
You find corresponding downloads both on our download page and in our Maven repository.
Jakarta EE is still quite young. Nearly all Java server projects are based on Java EE – and moving an application from Java EE to Jakarta EE means quite high effort: you not only have to do some renaming within your own classes, but also need to update all your dependencies which internally reference corresponding “javax.*” classes. – Many projects are using Spring, which uses Java EE, and which is not available for Jakarta EE currently.
For all existing users of CaptainCasa:
For new users of CaptainCasa: