Key Jakarta EE Q&A: Naming, Governance, Roadmap, and How to Contribute

What is Jakarta EE?

Jakarta EE is described as the future of cloud‑native, lightweight, and traditional enterprise Java applications.

What special meaning does the name “Jakarta EE” have? Why was it chosen?

The early Apache Jakarta project contributed many innovations to the Java ecosystem and helped build a strong open‑source community. According to Wikipedia, the name comes from the Sun Microsystems conference room where the project was discussed. In February 2018, nearly 7,000 community members voted, with over 64% selecting Jakarta EE. After the Jakarta project retired in 2011, the Apache Software Foundation allowed the Eclipse Foundation to reuse the name.

What does the Jakarta EE platform cover?

Jakarta EE is fully compatible with the Java EE 8 platform; all Java EE 8 specifications, reference implementations, and Technology Compatibility Kits (TCKs) have been transferred to the Eclipse Foundation.

What changes occurred in the javax.* namespace?

Jakarta EE 9 introduced the jakarta. namespace, replacing the original javax. namespace in the specifications.

What is the current status of Java EE TCKs?

The Java EE 8 TCKs were donated by Oracle and released under the Eclipse Public License 2.0. They are now open‑source and hosted in the Eclipse Foundation’s GitHub repository, intended as a basis for Jakarta EE 8 compatibility testing.

How does Jakarta EE’s governance model differ from Java EE’s?

The Eclipse Foundation brings 14 years of governance experience, offering an open, vendor‑neutral model that provides a fair competitive environment for all participants.

How is the Jakarta EE specification created?

The Eclipse Foundation has established a new specification process based on its respected development process, with the Jakarta EE Specification Committee tailoring it for Jakarta EE.

How often will new releases of Jakarta EE be delivered?

The schedule is still being defined; no specific timeline is set. The community commits to accelerating innovation while balancing stability, and will gather feedback from developers and enterprise users.

What’s included in the next Eclipse GlassFish release and when?

All information and upcoming releases are available on the Eclipse GlassFish project homepage.

What is the overall future vision for Jakarta EE beyond the current roadmap?

Key focus areas identified by developers and stakeholders include stronger microservice support, deeper cloud‑native integration (Docker, Kubernetes), faster innovation, an active developer community, and production‑grade reference implementations.

What is the relationship between EE4J and Jakarta EE?

Two referenced posts explain the relationship and when to use each name; generally, Jakarta EE is used unless discussing implementations within Eclipse.

Jakarta EE, EE4J and Java EE relationship – https://www.agilejava.eu/2018/03/22/the-relationship-between-jakarta-ee-ee4j-and-java-ee/

When to use Jakarta EE vs. EE4J – https://www.eclipse.org/lists/ee4j-community/msg01403.html

Will Jakarta EE prioritize creating and managing microservices to meet modern enterprise needs?

Yes. The community aims to integrate innovations from the Eclipse MicroProfile and other open‑source projects into new platform versions.

How will Jakarta EE support cloud‑native migration for legacy Java systems?

The community plans tighter integration with cloud‑native technologies (Kubernetes, Docker) and collaboration with OpenJDK and Eclipse OpenJ9 to provide architecture‑level support when JVM enhancements become available.

What are the key points to keep the language and EE platform in sync?

The release cadence is still undefined; once established, efforts will ensure alignment with other communities such as OpenJDK.

Who can use the “Compatible with Jakarta EE” logo and how?

The logo may only be used for Profiles (e.g., Full, Web) and not for individual specifications like Servlet. Open‑source implementations that pass the TCK and meet Eclipse Foundation licensing can claim compatibility. Organizations must meet the membership requirements in the Jakarta EE Trademark License Agreement.

How can one become a Jakarta EE contributor or committer?

Find an interested Jakarta EE project, create an Eclipse Foundation account, and sign the Eclipse Contributor Agreement. After the project team acknowledges your work, a process upgrades you to committer status. Employees of member organizations are covered by their employer’s agreement.

How can I participate in Jakarta EE activities?

Ways to join include contributing pull requests to EE4J projects on GitHub (after signing the Eclipse Contributor Agreement), becoming a committer member of the Eclipse Foundation to vote in board elections, or joining as a software vendor, enterprise, or strategic member to influence the roadmap and governance.

Jakarta EE Trademark Guidelines – https://jakarta.ee/legal/trademark_guidelines/

Official FAQ: https://jakarta.eaworld.io/zh/about/faq/