Player software | Java |
---|---|
Programming language(s) | Java |
Application(s) | Application server |
Status | Active |
License | Eclipse Public License or GNU General Public License w/Classpath exception |
Website | jakarta |
Java platform editions |
---|
|
Jakarta EE, formerly Java Platform, Enterprise Edition (Java EE) and Java 2 Platform, Enterprise Edition (J2EE), is a set of specifications, extending Java SE [1] with specifications for enterprise features such as distributed computing and web services. [2] Jakarta EE applications are run on reference runtimes, which can be microservices or application servers, which handle transactions, security, scalability, concurrency and management of the components they are deploying.
Jakarta EE is defined by its specification. The specification defines APIs (application programming interface) and their interactions. As with other Java Community Process specifications, providers must meet certain conformance requirements in order to declare their products as Jakarta EE compliant.
Examples of contexts in which Jakarta EE referencing runtimes are used are: e-commerce, accounting, banking information systems.
The platform was known as Java 2 Platform, Enterprise Edition or J2EE from version 1.2, until the name was changed to Java Platform, Enterprise Edition or Java EE in version 1.5.
Java EE was maintained by Oracle under the Java Community Process. On September 12, 2017, Oracle Corporation announced that it would submit Java EE to the Eclipse 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 of javax 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 of Java and also the capital of Indonesia, Jakarta. [8] The name should not be confused with the former Jakarta Project which fostered a number of current and former Java projects at the Apache Software Foundation.
Platform version | Release [9] | Specification | Java SE Support | Important Changes |
---|---|---|---|---|
Jakarta EE 11 | Planned for June/July 2024 | 11 | Java SE 21 | Data |
Jakarta EE 10 | 2022-09-22 [10] | 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 [11] | 9.1 |
| JDK 11 support |
Jakarta EE 9 | 2020-12-08 [12] | 9 | Java SE 8 | API namespace move from javax to jakarta |
Jakarta EE 8 | 2019-09-10 [13] | 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 based Security |
Java EE 7 | 2013-05-28 | JSR 342 | Java SE 7 | WebSocket, JSON and HTML5 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 and Generics in Java |
J2EE 1.4 | 2003-11-11 | JSR 151 | J2SE 1.4 | WS-I interoperable web services [14] |
J2EE 1.3 | 2001-09-24 | JSR 58 | J2SE 1.3 | Java connector architecture [15] |
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, managing distributed queues.
The Jakarta EE APIs include several technologies that extend the functionality of the base Java SE APIs, such as Jakarta Enterprise Beans, connectors, servlets, Jakarta Server Pages and several web 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 [16] | Java EE 7 [17] | Java EE 8 [18] Jakarta EE 8 [19] | Jakarta EE 9 [20] Jakarta EE 9.1 [21] | Jakarta EE 10 [22] |
---|---|---|---|---|---|
Jakarta Servlet | 3.0 | 3.1 | 4.0 | 5.0 | 6.0 |
Jakarta Server Pages (JSP) | 2.2 | 2.3 | 2.3 | 3.0 | 3.1 |
Jakarta Expression Language (EL) | 2.2 | 3.0 | 3.0 | 4.0 | 5.0 |
Jakarta Debugging Support for Other Languages (JSR-45) | 1.0 | 1.0 | 1.0 | 2.0 | 2.0 |
Jakarta Standard Tag Library (JSTL) | 1.2 | 1.2 | 1.2 | 2.0 | 3.0 |
Jakarta Faces | 2.0 | 2.2 | 2.3 | 3.0 | 4.0 |
Jakarta RESTful Web Services (JAX-RS) | 1.1 | 2.0 | 2.1 | 3.0 | 3.1 |
Jakarta WebSocket (WebSocket) | — | 1.0 | 1.1 | 2.0 | 2.1 |
Jakarta JSON Processing (JSON-P) | — | 1.0 | 1.1 | 2.0 | 2.1 |
Jakarta JSON Binding (JSON-B) | — | — | 1.1 | 2.0 | 3.0 |
Jakarta Annotations (CA) | 1.1 | 1.2 | 1.3 | 2.0 | 2.1 |
Jakarta Enterprise Beans (EJB) | 3.1 Lite | 3.2 Lite | 3.2 Lite | 4.0 Lite | 4.0 Lite |
Jakarta Transactions (JTA) | 1.1 | 1.2 | 1.2 | 2.0 | 2.0 |
Jakarta Persistence (JPA) | 2.0 | 2.1 | 2.2 | 3.0 | 3.1 |
Jakarta Bean Validation | 1.0 | 1.1 | 2.0 | 3.0 | 3.0 |
Jakarta Managed Beans | 1.0 | 1.0 | 1.0 | 2.0 | — |
Jakarta Interceptors | 1.1 | 1.2 | 1.2 | 2.0 | 2.1 |
Jakarta Contexts and Dependency Injection (CDI) | 1.0 | 1.1 | 2.0 | 3.0 | 4.0 |
Jakarta Dependency Injection | 1.0 | 1.0 | 1.0 | 2.0 | 2.0 |
Jakarta Security | — | — | 1.0 | 2.0 | 3.0 |
Jakarta Authentication | — | 1.0 | 1.1 | 2.0 | 3.0 |
Jakarta Concurrency | — | — | — | — | 3.0 |
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 (like connectors, clustering, fault tolerance, high availability, security, etc.), installed size, memory footprint, startup time, etc.
Referencing runtime [23] [24] [25] | 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, [26] 23.0.0.3 [27] | 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 [27] | 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 | No | No | No | Yes 7.3.0 | Yes 7.3.0 | Free software |
TomEE | Apache | No | No | Yes 9.0.0-M7 [28] | No | Yes 8.0.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 |
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 | Yes Sun Java System Application Server v9.0 | Yes Sun 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 using Jakarta Servlet, Jakarta Server Pages (JSP), or Jakarta Faces (JSF) with Facelets. The example below uses Faces and Facelets. 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 uses Contexts and Dependency Injection (CDI) and Jakarta Enterprise Beans (EJB).
@Named@ViewScopedpublicclassUserEdit{privateUseruser;@InjectprivateUserDAOuserDAO;publicStringsaveUser(){userDAO.save(this.user);addFlashMessage("User "+this.user.getId()+" saved");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 or Jakarta Persistence (JPA) can be used. The example below uses EJB and JPA. Not explicitly shown is that JTA is used under the covers by EJB to control transactional behavior.
@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.
@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;}}
OSGi is an open specification and open source project under the Eclipse Foundation.
Jakarta Enterprise Beans is one of several Java APIs for modular construction of enterprise software. EJB is a server-side software component that encapsulates business logic of an application. An EJB web container provides a runtime environment for web related software components, including computer security, Java servlet lifecycle management, transaction processing, and other web services. The EJB specification is a subset of the Java EE specification.
An application server is a server that hosts applications or software that delivers a business application through a communication protocol. For a typical web application, the application server sits behind the web servers.
A web container is the component of a web server that interacts with Jakarta Servlets. A web container is responsible for managing the lifecycle of servlets, mapping a URL to a particular servlet and ensuring that the URL requester has the correct access-rights. A web container handles requests to servlets, Jakarta Server Pages (JSP) files, and other types of files that include server-side code. The Web container creates servlet instances, loads and unloads servlets, creates and manages request and response objects, and performs other servlet-management tasks. A web container implements the web component contract of the Jakarta EE architecture. This architecture specifies a runtime environment for additional web components, including security, concurrency, lifecycle management, transaction, deployment, and other services.
Apache Tomcat is a free and open-source implementation of the Jakarta Servlet, Jakarta Expression Language, and WebSocket technologies. It provides a "pure Java" HTTP web server environment in which Java code can also run. Thus it is a Java web application server, although not a full JEE application server.
NetBeans is an integrated development environment (IDE) for Java. NetBeans allows applications to be developed from a set of modular software components called modules. NetBeans runs on Windows, macOS, Linux and Solaris. In addition to Java development, it has extensions for other languages like PHP, C, C++, HTML5, and JavaScript. Applications based on NetBeans, including the NetBeans IDE, can be extended by third party developers.
WebObjects is a discontinued Java web application server and a server-based web application framework originally developed by NeXT Software, Inc.
Jakarta Faces, formerly Jakarta Server Faces and JavaServer Faces (JSF) is a Java specification for building component-based user interfaces for web applications. It was formalized as a standard through the Java Community Process as part of the Java Platform, Enterprise Edition. It is an MVC web framework that simplifies the construction of user interfaces (UI) for server-based applications by using reusable UI components in a page.
Java Management Extensions (JMX) is a Java technology that supplies tools for managing and monitoring applications, system objects, devices and service-oriented networks. Those resources are represented by objects called MBeans. In the API, classes can be dynamically loaded and instantiated. Managing and monitoring applications can be designed and developed using the Java Dynamic Management Kit.
Apache Beehive is a discontinued Java Application Framework that was designed to simplify the development of Java EE-based applications. It makes use of various open-source projects at Apache, such as XMLBeans. Apache Beehive uses Java 5, including JSR-175, a facility for annotating fields, methods, and classes so that they can be treated in special ways by runtime tools. It builds on the framework developed for BEA Systems WebLogic Workshop for its 8.1 series. BEA later decided to donate the code to Apache.
GlassFish is an open-source Jakarta EE platform application server project started by Sun Microsystems, then sponsored by Oracle Corporation, and now living at the Eclipse Foundation and supported by OmniFish, Fujitsu and Payara. The supported version under Oracle was called Oracle GlassFish Server. GlassFish is free software and was initially dual-licensed under two free software licences: the Common Development and Distribution License (CDDL) and the GNU General Public License (GPL) with the Classpath exception. After having been transferred to Eclipse, GlassFish remained dual-licensed, but the CDDL license was replaced by the Eclipse Public License (EPL).
The Jakarta XML Web Services is a Jakarta EE API for creating web services, particularly SOAP services. JAX-WS is one of the Java XML programming APIs.
EasyBeans is an open-source Enterprise JavaBeans (EJB) container hosted by the OW2 Consortium. The License used by EasyBeans is the LGPL. EasyBeans is the EJB 3.0 container of the JOnAS application server.
Jakarta Persistence, also known as JPA is a Jakarta EE application programming interface specification that describes the management of relational data in enterprise Java applications.
OpenJPA is an open source implementation of the Java Persistence API specification. It is an object-relational mapping (ORM) solution for the Java language, which simplifies storing objects in databases. It is open-source software distributed under the Apache License 2.0.
EclipseLink is the open source Eclipse Persistence Services Project from the Eclipse Foundation. The software provides an extensible framework that allows Java developers to interact with various data services, including databases, web services, Object XML mapping (OXM), and enterprise information systems (EIS). EclipseLink supports a number of persistence standards including:
The JBoss Enterprise Application Platform is a subscription-based/open-source Java EE-based application server runtime platform used for building, deploying, and hosting highly-transactional Java applications and services developed and maintained by Red Hat. The JBoss Enterprise Application Platform is part of Red Hat's Enterprise Middleware portfolio of software. Because it is Java-based, the JBoss application server operates across platforms; it is usable on any operating system that supports Java. JBoss Enterprise Application Platform was originally called JBoss and was developed by the eponymous company JBoss, acquired by Red Hat in 2006.
Apache TomEE is the Enterprise Edition of Apache Tomcat that combines several Java enterprise projects including Apache OpenEJB, Apache OpenWebBeans, Apache OpenJPA, Apache MyFaces and others. In October 2011, the project obtained certification by Oracle Corporation as a compatible implementation of the Java EE 6 Web Profile.
WildFly, formerly known as JBoss AS, or simply JBoss, is an application server written by JBoss, now developed by Red Hat. WildFly is written in Java and implements the Java Platform, Enterprise Edition specification. It runs on multiple platforms.
{{cite web}}
: |author=
has generic name (help)