Jakarta EE 11 Web Profile released, enabled by Eclipse GlassFish

The Jakarta EE 11 Web Profile has officially been released on March 30, 2025 — bringing a cleaner, more modern baseline to the Jakarta EE platform, with strong alignment to recent Java versions, improved modularity, and the removal of legacy specifications. Although it comes later than planned, due to unexpected challenges in refactoring the Jakarta EE TCK (compatibility kit), this release marks a key shift toward a more cloud-native, developer-focused platform — and we’re proud to say that Eclipse GlassFish was the first implementation to pass the Jakarta EE 11 Web Profile TCK and enable the specification’s final approval. Key Technical Changes in Jakarta EE 11 Web Profile Jakarta EE 11 Web Profile delivers an updated and streamlined set of specifications designed for lightweight, server-side Java applications. Major technical highlights include: Modern Java compatibility: Baseline raised to support newer Java LTS versions, including records (Java 17 supported, Java 21 recommended) CDI as a central integration model: Even deeper CDI integration across multiple specs Jakarta Data 1.0: A new spec in Jakarta EE; sets the stage for data access innovation Several specifications updated: Persistence 3.2 – Java SE Records as embeddable classes, more functions in queries, Instant and Year support for date/time fields, and many more Concurrency 3.1 – Support for Java Virtual Threads and Flow API Jakarta Security 4.0 – Choosing from multiple authentication mechanisms, In-memory identity store (for testing) Expression Language 6.0 – Support Java Records and Optional, new length property for arrays And many others, with bigger or smaller changes (see the table below) Deprecation cleanup: Removal of some EJB features, JAXB support, and Jakarta Faces Managed Beans GlassFish: The first compatible implementation for Jakarta EE 11 Web Profile GlassFish, maintained in the Eclipse EE4J top-level project, was the ratifying compatible implementation (CI) used to verify the Jakarta EE 11 Web Profile TCK and ensure compliance. As the first runtime to pass the full TCK, GlassFish played a critical role in finalizing the Jakarta EE 11 Web Profile specification: ✅ Full TCK compliance for Jakarta EE 11 Web Profile

Apr 11, 2025 - 18:44
 0
Jakarta EE 11 Web Profile released, enabled by Eclipse GlassFish

The Jakarta EE 11 Web Profile has officially been released on March 30, 2025 — bringing a cleaner, more modern baseline to the Jakarta EE platform, with strong alignment to recent Java versions, improved modularity, and the removal of legacy specifications.

Although it comes later than planned, due to unexpected challenges in refactoring the Jakarta EE TCK (compatibility kit), this release marks a key shift toward a more cloud-native, developer-focused platform — and we’re proud to say that Eclipse GlassFish was the first implementation to pass the Jakarta EE 11 Web Profile TCK and enable the specification’s final approval.

Key Technical Changes in Jakarta EE 11 Web Profile

Jakarta EE 11 Web Profile delivers an updated and streamlined set of specifications designed for lightweight, server-side Java applications. Major technical highlights include:

  • Modern Java compatibility: Baseline raised to support newer Java LTS versions, including records (Java 17 supported, Java 21 recommended)
  • CDI as a central integration model: Even deeper CDI integration across multiple specs
  • Jakarta Data 1.0: A new spec in Jakarta EE; sets the stage for data access innovation
  • Several specifications updated:
    • Persistence 3.2 – Java SE Records as embeddable classes, more functions in queries, Instant and Year support for date/time fields, and many more
    • Concurrency 3.1 – Support for Java Virtual Threads and Flow API
    • Jakarta Security 4.0 – Choosing from multiple authentication mechanisms, In-memory identity store (for testing)
    • Expression Language 6.0 – Support Java Records and Optional, new length property for arrays
    • And many others, with bigger or smaller changes (see the table below)
  • Deprecation cleanup: Removal of some EJB features, JAXB support, and Jakarta Faces Managed Beans

Full specification list for Jakarta EE 11 Web Profile

GlassFish: The first compatible implementation for Jakarta EE 11 Web Profile

GlassFish, maintained in the Eclipse EE4J top-level project, was the ratifying compatible implementation (CI) used to verify the Jakarta EE 11 Web Profile TCK and ensure compliance.

As the first runtime to pass the full TCK, GlassFish played a critical role in finalizing the Jakarta EE 11 Web Profile specification:

✅ Full TCK compliance for Jakarta EE 11 Web Profile