| Player software | Java |
|---|---|
| Programming language(s) | Java |
| Application(s) | Application server |
| Status | Active |
| License | Eclipse Public License orGNU General Public License w/Classpath exception |
| Website | jakarta |
| Java platform editions |
|---|
|
Jakarta EE, formerlyJava Platform, Enterprise Edition (Java EE) andJava 2 Platform, Enterprise Edition (J2EE), is a set of specifications, extendingJava SE[1] with specifications for enterprise features such asdistributed computing andweb services.[2] Jakarta EE applications are run onreference runtimes, which can bemicroservices orapplication servers, which handle transactions, security, scalability,concurrency and management of the components they are deploying.
Jakarta EE is defined by itsspecification. The specification definesAPIs (application programming interface) and their interactions. As with otherJava Community Process specifications, providers must meet certain conformance requirements in order to declare their products asJakarta EE compliant.
Examples of contexts in which Jakarta EE referencing runtimes are used are:e-commerce,accounting,bankinginformation systems.
The platform created bySun Microsystems was known asJava 2 Platform, Enterprise Edition orJ2EE from version 1.2, until the name was changed toJava Platform, Enterprise Edition orJava EE in version 1.5.
AfterSun was acquired in 2009, Java EE was maintained byOracle under theJava Community Process. On September 12, 2017,Oracle Corporation announced that it would submit Java EE to theEclipse Foundation.[3] The Eclipse top-level project has been named Eclipse Enterprise for Java (EE4J).[4] The Eclipse Foundation could not agree with Oracle over the use ofjavax and Java trademarks.[5] Oracle owns the trademark for the name "Java" and the platform was renamed from Java EE to Jakarta EE.[6][7] The name refers to the largest city on the island ofJava and also the capital of Indonesia,Jakarta.[8] The name should not be confused with the formerJakarta Project which fostered a number of current and former Java projects at theApache Software Foundation.
| Platform version | Release[9] | Specification | Java SE Support | Important Changes |
|---|---|---|---|---|
| Jakarta EE 11 | 2025-06-26[10] | 11 |
| Data |
| Jakarta EE 10 | 2022-09-22[11] | 10 |
| Removal of deprecated items in Servlet, Faces, CDI and EJB (Entity Beans and Embeddable Container). CDI-Build Time. |
| Jakarta EE 9.1 | 2021-05-25[12] | 9.1 |
| JDK 11 support |
| Jakarta EE 9 | 2020-12-08[13] | 9 | Java SE 8 | API namespace move fromjavax tojakarta |
| Jakarta EE 8 | 2019-09-10[14] | 8 | Java SE 8 | Full compatibility with Java EE 8 |
| Java EE 8 | 2017-08-31 | JSR 366 | Java SE 8 | HTTP/2 and CDI basedSecurity |
| Java EE 7 | 2013-05-28 | JSR 342 | Java SE 7 | WebSocket,JSON andHTML5 support |
| Java EE 6 | 2009-12-10 | JSR 316 | Java SE 6 | CDI managed Beans and REST |
| Java EE 5 | 2006-05-11 | JSR 244 | Java SE 5 | Java annotations andGenerics in Java |
| J2EE 1.4 | 2003-11-11 | JSR 151 | J2SE 1.4 | WS-I interoperable web services[15] |
| J2EE 1.3 | 2001-09-24 | JSR 58 | J2SE 1.3 | Java connector architecture[16] |
| J2EE 1.2 | 1999-12-17 | 1.2 | J2SE 1.2 | Initial specification release |
Jakarta EE includes several specifications that serve different purposes, like generating web pages, reading and writing from a database in a transactional way, and managing distributed queues.
The Jakarta EE APIs include several technologies that extend the functionality of the baseJava SEAPIs, such asJakarta Enterprise Beans,connectors,servlets,Jakarta Server Pages and severalweb service technologies.
In an attempt to limit the footprint of web containers, both in physical and in conceptual terms, the web profile was created, a subset of the Jakarta EE specifications. The Jakarta EE web profile comprises the following:
| Specification | Java EE 6[17] | Java EE 7[18] | Java EE 8[19] Jakarta EE 8[20] | Jakarta EE 9[21] Jakarta EE 9.1[22] | Jakarta EE 10[23] | Jakarta EE 11 |
|---|---|---|---|---|---|---|
| Jakarta Servlet | 3.0 | 3.1 | 4.0 | 5.0 | 6.0 | 6.1 |
| Jakarta Server Pages (JSP) | 2.2 | 2.3 | 2.3 | 3.0 | 3.1 | 4.0 |
| Jakarta Expression Language (EL) | 2.2 | 3.0 | 3.0 | 4.0 | 5.0 | 6.0 |
| Jakarta Debugging Support for Other Languages (JSR-45) | 1.0 | 1.0 | 1.0 | 2.0 | 2.0 | 2.0 |
| Jakarta Standard Tag Library (JSTL) | 1.2 | 1.2 | 1.2 | 2.0 | 3.0 | 3.0 |
| Jakarta Faces | 2.0 | 2.2 | 2.3 | 3.0 | 4.0 | 4.1 |
| Jakarta RESTful Web Services (JAX-RS) | 1.1 | 2.0 | 2.1 | 3.0 | 3.1 | 4.0 |
| Jakarta WebSocket (WebSocket) | — | 1.0 | 1.1 | 2.0 | 2.1 | 2.2 |
| Jakarta JSON Processing (JSON-P) | — | 1.0 | 1.1 | 2.0 | 2.1 | 2.1 |
| Jakarta JSON Binding (JSON-B) | — | — | 1.1 | 2.0 | 3.0 | 3.0 |
| Jakarta Annotations (CA) | 1.1 | 1.2 | 1.3 | 2.0 | 2.1 | 3.0 |
| Jakarta Enterprise Beans (EJB) | 3.1 Lite | 3.2 Lite | 3.2 Lite | 4.0 Lite | 4.0 Lite | 4.0 Lite |
| Jakarta Transactions (JTA) | 1.1 | 1.2 | 1.2 | 2.0 | 2.0 | 2.0 |
| Jakarta Persistence (JPA) | 2.0 | 2.1 | 2.2 | 3.0 | 3.1 | 3.2 |
| JakartaBean Validation | 1.0 | 1.1 | 2.0 | 3.0 | 3.0 | 3.1 |
| Jakarta Managed Beans | 1.0 | 1.0 | 1.0 | 2.0 | — | N/a |
| Jakarta Interceptors | 1.1 | 1.2 | 1.2 | 2.0 | 2.1 | 2.2 |
| JakartaContexts and Dependency Injection (CDI) | 1.0 | 1.1 | 2.0 | 3.0 | 4.0 | 4.1 |
| Jakarta Dependency Injection | 1.0 | 1.0 | 1.0 | 2.0 | 2.0 | 2.0 |
| Jakarta Security | — | — | 1.0 | 2.0 | 3.0 | 4.0 |
| Jakarta Authentication | — | 1.0 | 1.1 | 2.0 | 3.0 | 3.1 |
| Jakarta Concurrency | — | — | — | — | 3.0 | 3.1 |
Although by definition all Jakarta EE implementations provide the same base level of technologies (namely, the Jakarta EE spec and the associated APIs), they can differ considerably with respect to extra features (likeconnectors,clustering,fault tolerance,high availability,security, etc.), installed size,memory footprint, startup time, etc.
| Referencing runtime[24][25][26] | Developer | Jakarta EE 10 Platform | Jakarta EE 9/9.1 Platform Compatible Products | Jakarta EE 9/9.1 Web Profile Compatible Products | Jakarta EE 8 Platform Compatible Products | Jakarta EE 8 Web Profile Compatible Products | Licensing |
|---|---|---|---|---|---|---|---|
| GlassFish | Eclipse | Yes 7.0.0 | Yes 6.0.0/ 6.1.0 | Yes 6.0.0/ 6.1.0 | Yes 5.1.0 | Yes 5.1.0 | Free software |
| Open Liberty | IBM | Yes 22.0.0.13-beta,[27] 23.0.0.3[28] | Yes 21.0.0.12 | Yes 21.0.0.12 | Yes 19.0.0.6, 20.0.0.3 | Yes 19.0.0.6, 20.0.0.3 | Free software |
| WebSphere Liberty | IBM | Yes 23.0.0.3[28] | Yes 21.0.0.12 | Yes 21.0.0.12 | Yes 20.0.0.3 | Yes 20.0.0.3 | Proprietary software |
| WildFly | Red Hat | Yes 27.0.0.Alpha5 | Yes 23.0.1-Preview/25.0.0-Preview | Yes 23.0.1-Preview/25.0.0-Preview | Yes 18.0.0 | Yes 18.0.0 | Free software |
| JBoss EAP | Red Hat | Yes 8.0.0 | No | No | Yes 7.3.0 | Yes 7.3.0 | Free software |
| TomEE | Apache | Yes 10.x | Yes 9.x | Yes 9.x | Yes 8.x | Yes 8.x | Free software |
| Payara Server | Payara Services Limited | Yes 6.2022.1 Alpha 4 | Yes 6.2021.1 Alpha 1 | No | Yes 5.22.0, 5.23.0 | Yes 5.23.0 | Free software |
| Thunisoft Application Server | Beijing Thunisoft Information Technology | No | Yes 3.0 | No | Yes 2.8 | No | Proprietary software |
| JEUS | TmaxSoft | No | No | No | Yes 8.5 | No | Proprietary software |
| InforSuite Application Server | Shandong Cvicse Middleware | No | Yes 11 | No | Yes 10 | No | Proprietary software |
| WebOTX | NEC | Yes 12 | No | No | Yes 11 | No | Proprietary software |
| Referencing runtime | Developer | Java EE 8 certified – Full | Java EE 8 certified – Web | Java EE 7 certified – Full | Java EE 7 certified – Web | Java EE 6 certified – Full Official Oracle page for Java EE Compatibility. | Java EE 6 certified – Web | Java EE 5 certified | J2EE 1.4 certified | Licensing |
|---|---|---|---|---|---|---|---|---|---|---|
| GlassFish server Open Source Edition | Oracle | Yes v5.0[29] | Yes v5.0[29] | Yes v4.x[30] | Yes v4.x[30] | Yes v3.x and upward[31] | Yes v3.x Web Profile | Yes v2.1.x[31] | Free software | |
| Oracle GlassFish Server | Oracle | Yes v3[32] based on the open source GlassFish application server | YesSun Java System Application Server v9.0 | YesSun Java System Application Server v8.2 | Proprietary software | |||||
| Oracle WebLogic Server | Oracle | Yes 14.1.1[33] | Yes 12.2.1[34] | Yes v12c[35] | Yes v10.3.5.0 | Yes v9 | Proprietary software | |||
| WildFly | Red Hat | Yes v14.x[29] | Yes v14.x[29] | Yes v8.1[36] | Yes v8.0.0.Final | Yes v7.1[37] | Yes v6.0[38] and v7.0[39] | Yes v5.1[40][41] | Yes v4.x | Free software |
| JBoss Enterprise Application Platform | Red Hat | Yes v7.2[42] | Yes v7.0[30] | Yes v7.0[30] | Yes v6.0[43] | Yes v5 | Proprietary software | |||
| IBM WebSphere Application Server | IBM | Yes v9.x[29] | Yes v9.x[30] | Yes v8[44] | Yes v7 | Yes | Proprietary software | |||
| IBM WebSphere Application Server Liberty | IBM | Yes v18.0.0.2[45] | Yes v18.0.0.2[45] | Yes v8.5.5.6[46][47] | Yes v8.5.5.6[30] | Yes v8.5.5[48] | Proprietary software | |||
| Open Liberty | IBM | Yes v18.0.0.2 | Yes v18.0.0.2 | Free software | ||||||
| IBM WebSphere Application Server Community Edition | IBM | Yes v3.0 | Yes v2.1 | Proprietary software | ||||||
| Apache Geronimo | Apache | Yes v3.0-beta-1[49][50] | Yes v2.0 | Yes v1.0 | Free software | |||||
| JEUS | TmaxSoft | Yes v8 | Yes v7[51][52] | Yes v6 | Yes v5 | Proprietary software | ||||
| Cosminexus Application Server | Hitachi | Yes v10.0[29] | Yes v9[53] | Proprietary software | ||||||
| Fujitsu Interstage Application Server[54] | Fujitsu | Yes v12.0[29] | Yes v1 Azure/v10.1[55][56] | Yes | Proprietary software | |||||
| WebOTX | NEC | Yes[57] | Yes | Proprietary software | ||||||
| BES Application Server | Baolande | Yes v9.5[30] | ||||||||
| Apache TomEE[58][59] | Apache | No 7 (Java EE 7 like, but not certified[60]) | Yes | Free software | ||||||
| Resin Server | Caucho | Yes v4.0[61] | Yes | Proprietary software | ||||||
| Siwpas | OW2 | Yes v6.0[62] | Free software | |||||||
| JOnAS | OW2 | Yes v5.3 rc1[63] | Yes | Yes | Free software | |||||
| SAP NetWeaver | SAP | Yes v2.x[64] | Yes | Yes | Proprietary software | |||||
| Oracle Containers for Java EE | Oracle | Yes | Proprietary software | |||||||
| Oracle iPlanet Web Server | Oracle | Yes Sun Java System Web Server | Proprietary software | |||||||
| Oracle Application Server 10g | Oracle | Yes | Proprietary software | |||||||
| Pramati Server | Pramati Technologies | Yes v5.0 | Proprietary software | |||||||
| Trifork T4 | Trifork | Yes | Proprietary software | |||||||
| Sybase Enterprise Application Server[65] | Sybase | Yes | Proprietary software |
The code sample shown below demonstrates how various technologies in Java EE 7 are used together to build a web form for editing a user.
In Jakarta EE a (web) UI can be built usingJakarta Servlet,Jakarta Server Pages (JSP), orJakarta Faces (JSF) withFacelets. The example below uses Faces andFacelets. Not explicitly shown is that the input components use the Jakarta EE Bean Validation API under the covers to validate constraints.
<htmlxmlns="http://www.w3.org/1999/xhtml"xmlns:h="http://xmlns.jcp.org/jsf/html"xmlns:f="http://xmlns.jcp.org/jsf/core"><f:metadata><f:viewParamname="user_id"value="#{userEdit.user}"converter="#{userConvertor}"/></f:metadata><h:body><h:messages/><h:form><h:panelGridcolumns="2"><h:outputLabelfor="firstName"value="First name"/><h:inputTextid="firstName"value="#{userEdit.user.firstName}"label="First name"/><h:outputLabelfor="lastName"value="Last name"/><h:inputTextid="lastName"value="#{userEdit.user.lastName}"label="Last name"/><h:commandButtonaction="#{userEdit.saveUser}"value="Save"/></h:panelGrid></h:form></h:body></html>
To assist the view, Jakarta EE uses a concept called a "Backing Bean". The example below usesContexts and Dependency Injection (CDI) andJakarta Enterprise Beans (EJB).
importjava.io.Serializable;importjakarta.inject.Named;importjakarta.faces.view.ViewScoped;importjakarta.inject.Inject;@Named@ViewScopedpublicclassUserEditimplementsSerializable{privatestaticfinallongserialVersionUID=1L;privateUseruser;@InjectprivateUserDAOuserDAO;publicStringsaveUser(){userDAO.save(this.user);addFlashMessage(String.format("User %d saved",this.user.getId()));return"users.xhtml?faces-redirect=true";}publicvoidsetUser(Useruser){this.user=user;}publicUsergetUser(){returnuser;}}
To implement business logic,Jakarta Enterprise Beans (EJB) is the dedicated technology in Jakarta EE. For the actual persistence,JDBC orJakarta Persistence (JPA) can be used. The example below uses EJB and JPA. Not explicitly shown is thatJTA is used under the covers by EJB to control transactional behavior.
importjava.util.List;importjakarta.ejb.Stateless;importjakarta.persistence.EntityManager;importjakarta.persistence.PersistenceContext;importjakarta.persistence.TypedQuery;@StatelesspublicclassUserDAO{@PersistenceContextprivateEntityManagerentityManager;publicvoidsave(Useruser){entityManager.persist(user);}publicvoidupdate(Useruser){entityManager.merge(user);}publicList<User>getAll(){returnentityManager.createNamedQuery("User.getAll",User.class).getResultList();}}
For defining entity/model classes Jakarta EE provides the Jakarta Persistence (JPA), and for expressing constraints on those entities it provides the Bean Validation API. The example below uses both these technologies.
importjakarta.persistence.Entity;importjakarta.persistence.Id;importjakarta.persistence.GeneratedValue;importjakarta.persistence.GenerationType;@EntitypublicclassUser{@Id@GeneratedValue(strategy=IDENTITY)privateIntegerid;@Size(min=2,message="First name too short")privateStringfirstName;@Size(min=2,message="Last name too short")privateStringlastName;publicIntegergetId(){returnid;}publicvoidsetId(Integerid){this.id=id;}publicStringgetFirstName(){returnfirstName;}publicvoidsetFirstName(StringfirstName){this.firstName=firstName;}publicStringgetLastName(){returnlastName;}publicvoidsetLastName(StringlastName){this.lastName=lastName;}}