One step closer to reality

Java EE 8 Proposed Final Draft is here

Java EE 8

© Shutterstock / Stock Design

Java EE 8 is one step closer to reality. The drafts of the Java EE 8 Platform and Web Profile specification docs that should be submitted to the JCP for Proposed Final Draft have been published. Read on to find out what’s new.

Linda DeMichiel, Specification Lead for the Java EE Platform, announced in a message on the new platform that the drafts of the Java EE 8 Platform and Web Profile specification documents that they plan to submit to the JCP for Proposed Final Draft have been uploaded to the project documents area.

She explained that the changes are “quite minimal” — mostly to sync with updates in the Java Security API— and revealed that they are “not anticipating much further in the way of updates to the Platform spec, other than what might be needed to reflect any further updates to Java EE Security.”

Changes in Java EE 8

“Java EE 8 introduces the JSON Binding API (JSON-B) for mapping between JSON text and Java objects, building on the JSON Processing API (JSON-P) introduced in Java EE 7,” according to the draft. “The JSON Processing API itself is updated to reflect additional JSON standards. Servlet undergoes major enhancement with the addition of support for the new HTTP/2 protocol. JAX-RS adds support for server-sent events and, building on concurrency facilities added in Java SE 8, a reactive client API. The new Java EE Security API provides enhanced support for authentication and authorization in web modules, and also introduces APIs for access to identity stores. The Bean Validation facility is updated to reflect enhancements made in Java SE 8 and to extend the range of validated objects. While the focus of CDI in this release is to extend its scope beyond Java EE with the introduction of bootstrapping API, CDI also includes enhancements for event processing and alignment on Java SE features.”

Head on over to the project documents area to read the Proposed Final Draft for Java EE 8.

Plans for future versions

The draft also includes the plans for future versions of this specification.


“Many of the APIs that make up the Java EE platform include an SPI layer that allows service providers or other system level components to be plugged in. This specification does not describe the execution environment for all such service providers, nor the packaging and deployment requirements for all service providers. However, the Java EE Connector Architecture does define the requirements for certain types of service providers called resource adapters, and the Java Authorization Contract for Containers defines requirements for security service providers. Future versions of this specification will more fully define the Java EE SPI.”

Changes in Proposed Final Draft

EE.B.4.1 Additional Requirements:

  • Updated Chapter EE.3, “Security,” to reflect requirements of the Java EE Security API

EE.B.4.2 Editorial Changes:

  • Corrected version of Batch to 1.0.
  • Added clarification regarding TLS support in “Section EE.7.2.1, “Internet and Web Protocols.
  • Updated “Related Documents.”
  • Added reference to project.

SEE ALSO: Java EE 8 community survey results are here

If you want to read more about the scope of Java EE8 and the roadmap for Java EE 8 and Java EE 9, check out Reza Rahman’s SlideShare presentation.

Java EE 8 release date

No word has been said on the final release date.

However, the final release seems to be slated for the second half of this year.

JSR 366: Java Platform, Enterprise Edition 8 (Java EE 8) Specification. Source:

July was supposed to be a month packed with releases —both Java 9 and Java EE 8— but now that Java 9 has been delayed to late September, will Java EE 8 share the same fate?

The update to the original proposal seems to indicate that both will arrive in the second half of 2017.

What do you think?


Inline Feedbacks
View all comments