In the open source community, it’s important to keep up to date on major and minor release updates because that’s how the software is patched. Tomcat 10 Migration and Upgrade Considerations Otherwise the main changes we’re seeing are security patches and maintenance changes. The changes to the package names in the Jakarta Servlet and other related technologies from javax to Jakarta are the primary things to be adjusted. With the way Tomcat is designed, 10 is supposed to be fully compatible with 9 as far as upgrading goes. Having changed package naming conventions from javax to Jakarta, web applications will need to be recompiled against the new API’s. Both require Java+, but there is one thing worth mentioning difference wise: Between 9 and 10 there is a significant breaking change involving the java packaged in use by the specification API’s. 10, functionally, we’re not looking at a lot of tangible feature changes. tomcat-websocket.jar (WebSocket 2.0 implementation).tomcat-jni.jar (Interface to the native component of the APR/native connector).tomcat-jdbc.jar (Tomcat's database connection pooling solution).tomcat-dbcp.jar (package renamed database connection pool based on Commons DBCP 2).tomcat-coyote.jar (Tomcat connectors and utility classes).tomcat-api.jar (Interfaces shared by Catalina and Jasper).jasper-el.jar (Jasper 2 EL implementation).jasper.jar (Jasper 2 Compiler and Runtime).ecj-4.20.jar (Eclipse JDT Java compiler).catalina-tribes.jar (Group communication).catalina-storeconfig.jar (Generation of XML configuration from current state).catalina-ssi.jar (Server-side Includes module).catalina-ha.jar (High availability package).
0 Comments
Leave a Reply. |