created on | September 5, 2022 |
In Jakarta, the words Api and Architecture are not used in the naming of technologies. Thus, the naming is more concise and consistent than in the Java EE and J2EE versions. I omit the beginning Jakarta of each name of a technology, i.e. Jakarta Persistence is listed under Persistence.
In Jakarta EE 8, Java Authorization Contract for Containers (JACC) was renamed to Jakarta Authorization and Java Authentication Service Provider Interface for Containers (JASPIC) was renamed to Jakarta Authentictaion.
The list of technologies for the full platform specification is given in section 9.7., Full Jakarta™ EE Product Requirements of eachs version’s specification document. In Jakarta, the technologies are no longer grouped into their area of application as is was the case for Java EE versions. For Jakarta EE 8 to Jakarta EE 9.1, the order of technologies in the list was somewhat arbitrary. In the specification document for Jakarta EE 10 the technologies are listed in alphabetical order, which I find most convenient.
The technologies for the Jakarta EE Web Profile and Jakarta EE Core Profile (the latter introduced in Jakarta EE 10) are listed in a specification document for each version. Those documents are merely an addendum to the corresponding full platform’s specification document.
Technologies supported by the Jakarta E Web Profile are marked with the orange capital letter ‘W’ icon . Technologies supported by the Jakarta E Core Profile are marked with the green capital letter ‘C’ icon .
Where the specification for a technology was updated, the version number is marked with the upward arrow icon .
Optional technologies are marked with the filter icon in the list, at the Jakarta EE version where the technology was made optional.
Removed technologies are marked with the trashcan icon in the list, at the Jakarta EE version where the technology was removed.
Jakarta EE 8 *02 |
Jakarta EE 9 | Jakarta EE 9.1 | Jakarta EE 10 | |
---|---|---|---|---|
release date | 2019-08-26 | 2020-11-20 | 2021-05-21 | 2022-09-13 |
Java SE versions supported | 8 | 8 | 8 / 11 | 11 / 17 |
Jakarta EE Platform Specification | ||||
technologies | ||||
Activation | *81 | |||
Annotations | ||||
Authentication | ||||
Authorization | ||||
Batch | ||||
Bean Validation | ||||
Concurrency | ||||
Connectors | ||||
Contexts and Dependency Injection | ||||
Debugging Support for Other Languages | ||||
Dependency Injection | ||||
Enterprise Beans *03 *04 | ||||
Expression Language | ||||
Enterprise Web Services | ||||
Interceptors | ||||
JSON Binding | ||||
JSON Processing | ||||
Management | ||||
Managed Beans | ||||
Messaging | ||||
Persistence | ||||
RESTful Web Services | ||||
Security | ||||
Servlet | ||||
Server Faces | ||||
Server Pages | ||||
Standard Tag Library | ||||
Transactions | ||||
Web Services Metadata | ||||
WebSocket | ||||
optional technologies | Jakarta EE 8 | Jakarta EE 9 | Jakarta EE 9.1 | Jakarta EE 10 |
Deployment | ||||
Enterprise Beans 2.x API group | ||||
Enterprise Beans entity and QL *01 | ? *10-2 | |||
Jakarta XML RPC | ||||
Jakarta XML Registries | ||||
Jakarta Enterprise Web Services | ||||
Jakarta Web Services Metadata | ? *10-3 | |||
SOAP with Attachments | ||||
XML Web Services | ||||
XML Binding | ||||
removed technologies | ||||
Deployment | ||||
Enterprise Beans entity and QL *01 | ? *10-2 | |||
Management | ||||
XML RPC | ||||
XML Registries |
*01: the full term for the technology is Jakarta Enterprise Beans 3.2 and earlier entity beans and associated Jakarta Enterprise Beans QL.
*02: Jakarta EE 8 has no API changes compared to Java EE 8. Release was done to ease the transition
from Java EE to Jakarta EE. The only.
chnages involve changes in the namespace, where javax. packages have been renamed to jakarta.
*03: Except for Jakarta Enterprise Beans entity beans and associated Jakarta Enterprise Beans QL, which have been made optional.
*04: Jakarta EE Web Profile only supports Enterprise Beans Lite
*81: see link Jakarta Enterprise Beans, Optional Features 4.0 Specification Document on the
specification download page.
*82: The Specification for Jakarta EE 8 does not list Jakarta Activation but the is a reference
to to the JavaBean Activation Framework (JAF), which states that JAF is included in Java SE 9:
" The Java EE 8 Platform specification, dated July 31st, 2017, references JavaBeans™ Activation Framework Specification Version 1.1 in appendix EE.C Related Documents. A Maintenance Release of the JavaBeans™ Activation Framework was created and released in the JCP as version 1.2 dated July 2017. JavaBeans Activation Framework 1.2 adds support for, and is included in, Java SE 9, and is the version contributed to Eclipse."
Jakarta EE Platform 9 Specification Document, Appendix B.2.1. Activation 1.1 vs 1.2
*10-1: Jakarta Annotations was renamed to Jakarta Common Annotations
*10-2: The specification document for Jakarta EE 10 lists enterprise entity beans and associated
QL as both optional and removed in section 9.7. Full Jakarta™ EE Product Requirements
*10-3: The specification document for Jakarta EE 10 does not mention Jakarta Web Services Metadata
The Jakarta EE Web Profile versions support Enterprise Beans Lite.
The Jakarta EE Core versions support CDI Lite.
The following feature are optional in Jakarta EE Core: