Skip to main content
  • Edit my account
  • Manage Cookies

Jakarta Servlet 6.0

Jakarta Servlet defines a server-side API for handling HTTP requests and responses.

New features, enhancements or additions

  • Issue 18 Clarify the decoding and normalization of URI paths
  • Issue 37 Update Cookie class, related classes and the specification to remove references to FC 2109 and to replace them with RFC 6265
  • Issue 105 Clarify the behaviour of getRealPath(String)
  • Issue 175 Provide generic attribute support to cookies, including session cookies, to provide support for additional attributes such as the SameSite attribute
  • Issue 201 Add a module-info.java to support using the Servlet API in a modular environment as per the Java module system and the Jakarta EE 10 recommendations
  • Issue 272 Remove the recommendation that Servlet containers should include an X-Powered-Byheader
  • Issue 365 Correct the list of valid orderings for example 2 in Section 8.2.2, “Ordering of web.xml and webfragment.xml”
  • Issue 368 Clarify the behaviour of getRemoteAddress()
  • Issue 377 Clarify the behaviour of setCharacterEncoding(null) and similar calls
  • Issue 407 Add new methods to obtain unique identifiers for the current request and/or associated connection
  • Issue 411 Relax the requirements set out in Section 6.2.2, “Wrapping Requests and Responses” and allow the container to wrap Requests and Responses to meet the requirements of implementing the RequestDispatcher functionality.
  • Issue 416 Remove the restriction on programatically added listeners calling some ServletContext getter methods
  • Issue 418
  • Add a new method getErrorOnELNotFound() to JspPropertyGroupDescriptor to align with changes in the Jakarta Pages 3.1 specification.
  • Clarify the Javadoc for ServletRequest.isAsyncStarted() to align it with the specification text
  • Update the Javadoc to clarify the scheduling implications when ServletInputStream.isReady() or ServletOutputStream.isReady() return false

Removals, deprecations or backwards incompatible changes

  • Issue 225 Deprecated wrapped response handling in the doHead method in favour of container implementation of HEAD method behavior
  • Remove API classes and methods that were deprecated in Servlet 5.0 and earlier. This includes removing the SingleThreadModel and HttpSessionContext interfaces and the HttpUtils class as well as various deprecated methods

Minimum Java SE Version

Java SE 11 or higher

Details

Compatible Implementations

Ballots

Release Review

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

Plan Review

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.

Platform and Profile Specifications

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.

Individual Specifications

Each individual specification describes a standardized way of implementing a particular aspect of an enterprise Java application.

Back to the top