| Which namespace does it use? | WebLogic 14.1.2 implements Jakarta EE 8 (the javax namespace). WebLogic 15.1.1 implements Jakarta EE 9.1 (the jakarta namespace), per Oracle's release notes. | Tomcat 9.0 uses javax (Servlet 4.0). Tomcat 10.1 (Servlet 6.0) and 11.0 (Servlet 6.1) use jakarta. | Current WildFly and JBoss EAP 8 releases use the jakarta namespace. | Payara 7 implements Jakarta EE 11, so it uses jakarta. |
|---|
| What does it carry over from WebLogic? | Everything. Nothing moves, and the Oracle-specific APIs and descriptors keep working. | Servlets, JSP and WebSocket. EJB, JMS and a JTA transaction manager are not part of Tomcat, so an application that uses them needs libraries added or a different target. | A full Jakarta EE platform with EJB, JTA and embedded messaging. WebLogic descriptors and APIs still need mapping. | A full Jakarta EE platform from the GlassFish line. WebLogic descriptors and APIs still need mapping. |
|---|
| What happens to clustering and JMS? | Cluster membership, session replication and WebLogic JMS servers and stores stay as they are. | Session clustering exists but works differently. JMS moves to an external broker such as ActiveMQ Artemis or RabbitMQ. | High-availability profiles replace WebLogic clusters, and messaging runs on the embedded or an external Artemis broker. | Clustering is Hazelcast-based. Which JMS provider to use is a decision for the destinations you have. |
|---|
| Who supports it, and until when? | Oracle. Premier Support: 12.2.x to December 2026, 14.1.x to December 2030. Extended Support, a paid add-on, runs to December 2027 and December 2033. Patches need an Oracle contract. | The Apache project. Support for 9.0 is expected no earlier than 31 March 2027; 10.1 and 11.0 have no end date stated. AceMQ supports Tomcat directly. | WildFly is a community project. JBoss EAP is Red Hat's subscription product, with its dates on Red Hat's policy pages. | Payara Community is open source. Supported editions are sold under the Azul Payara name. |
|---|
| When does it fit? | The application leans on WebLogic features, and you are content with the support position on your release. | Mostly servlets, with transactions and messaging already outside the server. | EJB, JTA and JMS-heavy applications that need a Jakarta EE platform. | Applications that follow the Jakarta EE specifications closely. |
|---|