Jakarta Concurrency provides a specification for using concurrency from application components without compromising container integrity while still preserving the Jakarta EE platform’s fundamental benefits.
Jakarta Concurrency 3.0 will target the Jakarta EE 10 platform release.
Jakarta Concurrency 3.0 will aim to contain.
Features identified by the community on GitHub tagged with 3.0 see 3.0 Milestone (github.com)
Bug Fixes as they arise during the release cycle
Documentation clean up as identified during the release cycle
Any updates required to meet the Java version requirements of Jakarta EE 10
Any requirements identified by other specifications or the Jakarta EE 10 platform projects during the release cycle.
The Specification Committee Ballot concluded successfully on 2021-05-21 with the following results:
| Representative | Representative for: | Vote |
|---|---|---|
| Kenji Kazumura | Fujitsu | +1 |
| Dan Bandera, Kevin Sutter | IBM | +1 |
| Ed Bratt, Dmitry Kornilov | Oracle | +1 |
| Andrew Pielage, Matt Gill | Payara | +1 |
| Scott Stark, Mark Little | Red Hat | +1 |
| David Blevins, Jean-Louis Monteiro | Tomitribe | +1 |
| Ivar Grimstad | EE4J PMC | +1 |
| Marcelo Ancelmo, Martijn Verburg | Participant Members | +1 |
| Werner Keil | Committer Members | +1 |
| Dr. Jun Qian | Enterprise Members | +1 |
| Total | 10 |
The ballot was held over the jakarta.ee-spec mailing list
Click on the specifications below to access the specification document, Javadoc, Technology Compatibility Kit (TCK), and compatible implementation for each release of the specification.
The Jakarta EE Platform and Profile specifications are the umbrella specifications for the individual specifications. The Jakarta EE Platform includes most of the individual specifications, while the Profile specifications include the individual specifications for developing web platforms and microservices architectures.
Each individual specification describes a standardized way of implementing a particular aspect of an enterprise Java application.