Jakarta EE 9 Milestone 1: What the Shift to jakarta.* Means for Java Developers

Jakarta EE 9 Milestone 1 marks the official transition from the javax.* namespace to jakarta.*, delivering a fully updated API set, reduced legacy specs, and new reference implementations, while aiming to lower entry barriers, accelerate releases, and provide a stable platform for developers to begin migration.

21CTO
21CTO
21CTO
Jakarta EE 9 Milestone 1: What the Shift to jakarta.* Means for Java Developers

Jakarta EE 9 Milestone 1 Released

Jakarta EE 9 Milestone 1, the first milestone before the release candidate, officially transitions the platform from the javax.* namespace to jakarta.*. This change is driven by Oracle’s decision to retain rights to the original namespace.

The milestone updates all APIs to use the new jakarta.* package names, removes deprecated specifications from Jakarta EE 8, and provides new reference implementations such as Jersey, Tyrus, and Yasson. GlassFish 6.0.0‑M1 is also available for deploying applications on the new namespace.

Key Objectives

Lower barriers for new vendors and implementations to achieve compatibility.

Accelerate version releases to serve as a platform for future innovation.

Offer developers a stable platform using the new namespace.

What the Milestone Includes

Removal of old, optional, or deprecated specifications from Jakarta EE 8 to reduce API count.

Provision of all Jakarta EE 9 APIs under the jakarta.* namespace.

Migration of extensive specification documentation to the Eclipse Foundation with updated namespace references.

Availability of the Jakarta EE 9 TCK for the new namespace.

Release of compatible implementations, including Jersey, Tyrus, Yasson, and GlassFish 6.0.0‑M1.

Developers can now experiment with the new namespace, begin migrating applications, frameworks, and tools, and benefit from a more streamlined set of APIs that underpin many modern Java frameworks.

For full specifications, visit https://jakarta.ee/specifications/platform/9 .

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

jakarta-eeJava EE migrationEnterprise JavaNamespace change
21CTO
Written by

21CTO

21CTO (21CTO.com) offers developers community, training, and services, making it your go‑to learning and service platform.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.