Jakarta Servlet defines a server-side API for handling HTTP requests and responses.
The Release Review Specification Committee Ballot concluded successfully on TBD with the following results.
| Yes | No | Abstain | |
|---|---|---|---|
| Fujitsu | |||
| IBM | |||
| Oracle | |||
| Payara | |||
| Red Hat | |||
| Tomitribe | |||
| EE4J PMC | |||
| Participant Members | |||
| Committer Members |
The Plan Review Specification Committee Ballot concluded successfully on TBD with the following results.
| Yes | No | Abstain | |
|---|---|---|---|
| Fujitsu | |||
| IBM | |||
| Oracle | |||
| Payara | |||
| Red Hat | |||
| Tomitribe | |||
| EE4J PMC | |||
| Participant Members | |||
| Committer Members |
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.