Home on Jakarta® EE: The New Home of Cloud Native Java

How to Build a RESTful Web Service Using Jakarta EE

webdev@eclipse-foundation.org (Eclipse Foundation) — Fri, 22 Sep 2023 00:00:00 +0000

This guide shows you how to use Jakarta EE to make a
RESTful web service.

To create a RESTful web service using Jakarta EE, we will begin by
summarizing what we want to build.

We will build a service that will accept an HTTP GET¹
request at http://localhost:8080/restfulservice/hello.

It will respond with the following JSON payload, as the following listing
shows:

{"text": "Hello from Jakarta EE"}

We can then further customize and improve it according to our needs.

Getting Started with Jakarta EE: A Comprehensive Beginner's Guide to the Get Started

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 21 Oct 2025 00:00:00 +0000

As a new Java developer or a student preparing for a career in enterprise
software, understanding Jakarta EE is essential. Evolving from Java EE, it
provides a reliable platform with APIs for building scalable, secure, and
portable applications. Jakarta EE is used across industries such as banking,
e-commerce, healthcare, and government.

What is Jakarta EE and Why It Matters

Jakarta EE is a set of specifications used for building
Java products and frameworks for building large-scale enterprise applications.
It powers systems like banks, e-commerce sites, and corporate platforms. It
builds on Java SE with additional APIs for web development, database access,
messaging, and security. If your goal is to create production-grade Java
applications, Jakarta EE provides the tools and standards to get there.

How to Secure a RESTful Web Service Using Jakarta EE

webdev@eclipse-foundation.org (Eclipse Foundation) — Fri, 29 Sep 2023 00:00:00 +0000

This guide shows you how to secure a rest endpoint using
Jakarta Authentication.

As we delve into securing RESTful web services, let’s first define a basic
scenario that we will be working with throughout this article.

We are constructing a service that will accept an HTTP GET request at
http://localhost:8080/jakartaee-hello-world/rest/hello. In
response to this request, our service will return a JSON payload, as shown in
the following example:

How to store and retrieve data using Jakarta Persistence of Jakarta EE

webdev@eclipse-foundation.org (Eclipse Foundation) — Fri, 22 Sep 2023 00:00:00 +0000

This guide shows you how to store and retrieve data using
Jakarta Persistence.

We will first begin by summarizing what we want to build. Next, we build a
RESTful web service that can consume data, store
it in a database using Jakarta Persistence, and serve it as a REST endpoint.
For those unfamiliar with RESTful web services, we recommend reading our
previous article.

We will build an application that handles coffee product data. The service will
consume a JSON payload containing the product’s ID, name, and price. Here’s an
example of the JSON payload:

10 ways to accelerate your career with Jakarta EE

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 10 Nov 2025 00:00:00 +0000

This article explores ten reasons to get involved in open source, highlighting how contributions to the Java standards for enterprise applications, Jakarta EE, can help you grow professionally while shaping the future of the software industry.

What's Up with Open Standard Enterprise Java and AI?

webdev@eclipse-foundation.org (Eclipse Foundation) — Thu, 02 Oct 2025 12:00:00 +0000

Enterprise Java has always been about standards—about providing a foundation that’s stable, interoperable, and vendor-neutral. If you’ve been around since the days of Servlets, EJBs, and JPA, you know that Jakarta EE’s approach is to standardize what’s proven, not chase every shiny new thing. That’s why mission-critical systems still rely on Jakarta EE’s backbone, and why customers look to the platform for direction and leadership. The Eclipse Foundation’s stewardship and open process help to reinforce this.

Beyond the Hype: 10 Reasons Jakarta EE is Still the Smartest Choice

webdev@eclipse-foundation.org (Eclipse Foundation) — Thu, 31 Jul 2025 00:00:00 +0000

In this article, I will talk about why Jakarta EE is the best technology investment for you as a Software Architect, C-level, and Senior Engineer as well.

Jakarta NoSQL and Jakarta Persistence Explained

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 29 Apr 2025 00:00:00 +0000

Abstract

The Jakarta EE ecosystem offers specifications for building database backend
applications using relational and/or NoSQL databases. The Jakarta Persistence
specification, with a rich history dating back almost 20 years, has been a
staple in the Java community for writing relational database applications. The
Jakarta NoSQL specification, with a short history dating back to 2020, provides
comprehensive support for all four types of NoSQL databases.

Introduction

The Jakarta EE ecosystem offers specifications for building database backend
applications using relational and/or NoSQL databases. The Jakarta Persistence
specification, with a rich history dating back almost 20 years, has been a
staple in the Java community for writing relational database applications. The
Jakarta NoSQL specification, with a short history
dating back to 2020, provides comprehensive support for all four types of NoSQL
databases.

Jakarta NoSQL 1.0 Final Released: Bridging Java and NoSQL with Standards

webdev@eclipse-foundation.org (Eclipse Foundation) — Wed, 26 Mar 2025 00:00:00 +0000

We’re thrilled to announce the final release of Jakarta NoSQL 1.0, a brand-new specification designed to bring standardization, productivity, and portability to NoSQL integration in the Java ecosystem.

This release marks a significant step in the Jakarta EE platform by introducing the first-ever NoSQL specification. Whether you’re working with document, key-value, column, or graph databases, Jakarta NoSQL is built to streamline your development experience.

Why Jakarta NoSQL?

Jakarta NoSQL was created to make it easier and more productive for developers to work with NoSQL databases while staying fully within the Jakarta EE programming model. It brings:

Key Takeaways from the Cloud Native Java Survey

webdev@eclipse-foundation.org (Shabnam Mayel) — Thu, 27 Feb 2025 00:00:00 +0000

The Jakarta EE Working Group conducted the first-ever Cloud Native Java
Survey between July 11, 2024 and August 23, 2024 to gather insights on
popular Java SE versions, Jakarta EE, and MicroProfile usage. The results from
over 170 respondents left us with a number of important takeaways about the
adoption of enterprise Java technologies, developer priorities, and more. Here
are the key findings.

Java EE/Jakarta EE Adoption

Jakarta EE 8 & Java EE 8 remain the most widely used versions.
Jakarta EE 10 adoption is growing as developers skip EE 9/9.1, which were
transitional.
A notable portion still relies on legacy Java EE versions (e.g., EE 6,
released 15 years ago).

MicroProfile Adoption

A majority do not use MicroProfile.
Those who do mostly run newer versions (MicroProfile 6 aligns with
Jakarta EE 10).
Some developers remain on older MicroProfile releases, indicating slow
migration.

Java SE Versions

Java SE 17 is the most used version.
Almost half of developers are already on Java SE 21.
Java SE 8 and 11 still have significant usage, despite being outdated.

Popular Java Runtimes

Spring Boot, Tomcat, Quarkus, and WildFly dominate the landscape.
GlassFish, JBoss EAP, Payara, and Open Liberty also have strong adoption.
Jetty, TomEE, and WebSphere hold niche market shares.
Helidon and some Asian runtimes have limited traction (~5% adoption).

Popular Jakarta EE APIs

Jakarta REST (JAX-RS), CDI, and JPA are the most widely used.
JSON, Servlet, and EJB also see strong adoption.
JSF, JSP, and JMS usage is declining as JavaScript frameworks and alternative
messaging solutions gain traction.

MicroProfile APIs

Config, OpenAPI, and REST Client lead usage.
Health, Metrics, and JWT are commonly used for cloud native applications.
GraphQL, OpenTracing, and Reactive Messaging see limited adoption.

Developer Priorities for Jakarta EE & MicroProfile

Adapting to Java SE innovations (e.g., Virtual Threads, Project CRaC, Project Leyden).
Enhanced Kubernetes support (e.g., integration with Kubernetes Secrets).
Deprecating legacy features like EJB, favoring CDI-based alternatives.
New features, including:
- Jakarta Messaging Lite for modern cloud use cases.
- CDI-based replacements for EJB Message-Driven Beans, @Schedule, and @RolesAllowed.
- A standard API for server management.

Other Key Insights

The majority still use the Jakarta EE platform.
Most developers combine Jakarta EE and MicroProfile, though some use Jakarta
EE alone.
JSON over HTTP (REST) dominates API usage; XML and SOAP are declining, while
OpenAPI is widely used.

The Jakarta EE Working Group thanks all participants and will use these
insights to guide future improvements.

2024 Cloud Native Java Survey Findings

shabnam.mayel@eclipse-foundation.org (Shabnam Mayel) — Tue, 11 Feb 2025 00:00:00 +0000

In 2024, the Jakarta EE Working Group launched a brand new effort named the
“Cloud Native Java Survey.” This blog, authored by the Jakarta EE Marketing
Committee, summarizes the key insights from the survey.
You may already be aware of the annual Jakarta EE Developer Survey,
also organized by the working group. While the Developer Survey provides a
broad view of the ecosystem and Java trends, the Cloud Native Java Survey dives
deeper into technical details, encompassing both Jakarta EE and MicroProfile.
The survey was conducted between July 11, 2024 and August 23, 2024.

Change Log

webdev@eclipse-foundation.org (Eclipse Foundation) — Fri, 12 Apr 2024 00:00:00 +0000

Batch 2.1 Change Log

Become a Sponsor | Jakarta EE

webdev@eclipse-foundation.org (Eclipse Foundation) — Wed, 03 Apr 2024 00:00:00 +0000

Become a sponsor of the Jakarta EE Working Group and

Empower the Future of Enterprise Java

Your organisation will play a pivotal role in shaping the future of open source enterprise Java and ensuring the continued growth and success of the global Java community.

By joining our sponsorship program:

Your
Support

will help us maintain and expand our initiatives.

Jakarta Concurrency Explained

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 12 Mar 2024 00:00:00 +0000

Application performance can make or break a user’s experience.
Applications that provide a consistent experience and perform well are
more likely to benefit user productivity. The Jakarta Concurrency
specification targets application performance and usability by providing
a standard API for developing concurrent application processes without
compromising container integrity. It is not recommended to utilize
traditional Java SE threads or timers within a Jakarta EE container
because use of threads or timers may cause reliability issues and
unexpected results. Jakarta Concurrency provides an API that does not
intrude on container integrity, but rather, uses services that are
managed by the container and matches the functionality provided by the
Java SE Concurrency Utilities.

Jakarta Contexts Dependency Injection Explained

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 12 Mar 2024 00:00:00 +0000

Jakarta Dependency Injection provides the ability to make
use of contextual objects in an application with maximum
reusability, testability, and maintainability. This
specification provides a means for developers to easily
obtain objects throughout classes within an application
without the requirement to use constructors, factories, or
service locators.

Jakarta Contexts and Dependency Injection, Jakarta CDI for
short, is one of the paramount specifications of the
Jakarta EE Platform, as it contains a number of powerful
complimentary services that are utilized across a majority
of Jakarta EE applications. Jakarta CDI has been known as
the “glue” for the Jakarta EE Platform because one of the
most significant features is the enablement of contextual
objects to be made available for use throughout other
classes and views within an application. The specification
makes use of the Jakarta Dependency Injection specification
to provide this capability, but Jakarta CDI also provides a
number of other features beyond dependency injection
including scope assignment, generation of preconfigured
objects, qualification, initiating code when events occur,
to mention a few.

Jakarta EE Platform

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 12 Mar 2024 00:00:00 +0000

The Jakarta EE Platform enables developers to produce
lightweight, cloud native applications while providing
maximum developer productivity. Now featuring multiple
profiles geared towards producing microservices or full
stack applications, the Platform provides flexibility for
developing applications of all sizes. The Platform is
composed of a number of specifications, each targeting
specific areas in application architecture. This modular
approach allows the specifications to evolve under
different expert groups and timelines, while the platform
enables each to work together in harmony.

Jakarta Persistence Explained

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 12 Mar 2024 00:00:00 +0000

Enterprise applications typically require persistence for data storage. The
specification is foundational for many technologies since relational databases
are widely used within the industry. The Jakarta Persistence specification,
also known as Jakarta Persistence API (JPA), encompasses a number of APIs that
facilitate the creation, reading, updating, and deletion of data within data
stores. The specification provides an Entity Manager API which is used to
facilitate the lifecycle of entities within an application. The Query and
TypedQuery APIs are used to retrieve data utilizing both static and dynamic
queries. The Metamodel API enables the ability to obtain metadata regarding
managed entities and persistence objects. Lastly, the Criteria API provides a
means for defining queries through the use of object based query objects to
perform strongly-typed queries.

Jakarta RESTful Web Services Explained

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 12 Mar 2024 00:00:00 +0000

Jakarta REST is the solution for development of building Representational State
Transfer web services on the Jakarta EE Platform. The specification is easy to
learn, and it enables one to construct powerful REST APIs and it also includes
APIs for working with web services as a client. As such, this specification
is key to the development of microservices and cloud based applications, and it
is part of the Jakarta EE Web Profile as well as the full platform.

Jakarta Security, Jakarta Authorization, and Jakarta Authentication Explained

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 12 Mar 2024 00:00:00 +0000

Security is a major component of application development. Jakarta EE provides
the robust Jakarta Security specification that when paired with the Jakarta
Authentication and Jakarta Authorization specifications, provides APIs that
deliver end-to-end security. There are a large number of application processes
that require security measures, and these specifications provide the ability to
do so in a straightforward manner using annotations and minimal XML
configurations. Jakarta EE compliant containers and deployment environments
adhere to the constructs of the Authentication and Authorization policies to
ensure that applications can be secured in a standard way and deployed across a
number of different environments.

Jakarta Servlet, Jakarta Faces and Jakarta Server Pages Explained

webdev@eclipse-foundation.org (Eclipse Foundation) — Thu, 22 Feb 2024 00:00:00 +0000

The Jakarta EE Platform offers a number of APIs that can be used to create web
based user interfaces. The most mature and perhaps most well known is the
Jakarta Servlet specification. Jakarta Servlet was first released in 1996, and
it enables Java developers to create web pages containing dynamic web content
using pure Java. The specification has changed much over the years and it is
able to interact with modern technologies and comply with the modern era of web
technologies with features such as HTTP/2. Jakarta Server Pages (JSP) was
first released in 1999, and it enables developers to create web based user
interfaces using a mixture of HTML markup and special Jakarta Servlet tags.
JSP enables easy creation of dynamic web views, and it has also made great
progressions over the years to position it for standard model-view-controller
development. Model-View-Controller development specifies clear separation of
view code from business logic, and in the early years of JSP it was common to
see business logic intermixed with HTML code. To that end, Jakarta Faces was
initially released in 2004, and it provides the ability to develop web based
user interfaces with XML for the view and a corresponding Java class to contain
the business logic for the view. This specification has adapted over the years
to continue as a relevant web based user interface API for modern times.

Jakarta EE Specification Versioning, Change, and Deprecation Process 1.0

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 10 Oct 2023 00:00:00 +0000

Content

Goals

It is the desire of the Jakarta EE specification projects to be able to make backwards incompatible changes to new
versions of Jakarta EE specifications. The goal of this document is to enable that outcome while also providing
guidance so that users can be aware of when backwards incompatible changes have occurred. The high-level framework in
which this document is written:

How to Start with Servlets Using Jakarta EE 10

webdev@eclipse-foundation.org (Eclipse Foundation) — Fri, 22 Sep 2023 00:00:00 +0000

This guide aims to walk you through the process of building a simple Servlet
application using Jakarta Servlet. We’ll start
by outlining what we aim to achieve and then step-by-step guide you through
setting up your environment, writing code, and deploying the Servlet
application. If you’re new to Servlets or Jakarta EE, this guide should be a
great starting point.

We’ll develop an application that accomplishes the following:

Presents a form asking the user to select their coffee preferences (e.g.,
black, latte, cold brew).
Stores these preferences in a session.
Dynamically generates a “Coffee Dashboard,” displaying personalized coffee
recommendations.

Jakarta EE Specification Process

webdev@eclipse-foundation.org (Eclipse Foundation) — Wed, 31 Aug 2022 13:00:00 -0400

The Jakarta EE Specification Process (JESP) is concerned with the Specification Process as it applies to Specification Projects operating under the purview of the Jakarta EE Working Group.

The Jakarta EE Specification Committee hereby adopts the Eclipse Foundation Specification Process v1.3 (EFSP) as the Jakarta EE Specification Process with the following modifications:

Any modification to or revision of this Jakarta EE Specification Process, including the adoption of a new version of the EFSP, must be approved by a Super-majority of the Specification Committee, including a Super-majority of the Strategic Members of the Jakarta EE Working Group, in addition to any other ballot requirements set forth in the EFSP.

javax to jakarta namespace ecosystem progress

martijn@londonjavacommunity.co.uk (Martijn Verburg) — Wed, 31 Aug 2022 09:00:00 +0000

Changes to this document must be approved by a simple majority vote of
the Jakarta EE specification committee, conducted via the public Jakarta
EE Specification Committee (jakarta.ee-spec@eclipse.org) mailing list.

This is a public document.

Specification Committee

The Jakarta EE Specification Committee is responsible for implementing
the Eclipse Foundation Specification Process (EFSP) for all
Specification Projects (as that term is defined by the EFSP) under the
purview of the Jakarta EE Working Group. This includes the adaptation of
the EFSP for Jakarta which is referred to as the Jakarta EE
Specification Process (JESP).

Proper use of the Jakarta® Brand by Eclipse Projects

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 03 Mar 2020 13:10:00 -0400

A critical aspect of managing a brand is avoiding confusion as to what the brand represents, what expectations should we expect to be met when something is labeled with that brand. It is important to clearly delineate what we mean when we label something “Jakarta”, that is, when we use “Jakarta” as a modifier/adjective to an object/noun (e.g., “Jakarta® Faces Specification”), and managing how it is used in the project space is part of this. Careful use of the name will help the community better understand what is directly represented by the Jakarta brand and what is not.

Adopt a Spec

webdev@eclipse-foundation.org (Eclipse Foundation) — Sat, 01 Feb 2020 16:09:45 -0400

This program is intended to encourage JUG leaders and members to get involved by adopting a Jakarta EE Specification. The objective is to increase developer level participation in the evolution of the Jakarta EE Specification.

Adopters

How JUG leaders can help:

Ensure that the topic of the adopted Jakarta EE Specification is consistently discussed, e.g. dedicate a portion of the existing JUG meetups to the discussions related to the adopted Specification, arrange monthly calls with all representatives of JUGs that are running the program in their groups.

Oracle/JCP Acronym Guidelines

webdev@eclipse-foundation.org (Eclipse Foundation) — Wed, 26 Jun 2019 16:10:38 -0400

Guidelines for the use of existing Oracle/JCP Acronyms. Supplement to the Eclipse Foundation Guidelines for Eclipse Logos & Trademarks Policy

Version 1.0 - June 26, 2019

The goal of these guidelines is to avoid confusion and ensure that the developer community can easily identify whether a Jakarta EE project, specification, test suite, or other related item originates from Oracle/JCP or from the Eclipse/Jakarta EE process.

The list of Oracle/JCP acronyms appears at the bottom of this document.

Contribute

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 02 Apr 2019 11:10:38 -0400

Why contribute to Jakarta EE

Grow your network and opportunities.

Open source is one of the best ways to meet and collaborate with Java mentors, community experts, and future employers. Many careers have taken off because someone’s contributions caught the proper attention.

Future-proof your career.

Jakarta EE is not “old Java EE.” It’s actively evolving to meet cloud native demands, including microservices, containers, and Kubernetes integration. Contributing means staying ahead of the curve, learning directly from experts, and keeping your skills sharp.

Mentorship

webdev@eclipse-foundation.org (Eclipse Foundation) — Tue, 02 Apr 2019 11:10:38 -0400

The power of Jakarta EE goes far beyond its specifications and code, it relies on contributors. The Jakarta EE Community Mentor Program helps new contributors get started quickly and confidently. Open source can be complex, but you don't have to navigate it alone. A mentor shares knowledge, avoids common pitfalls, and guides you step by step, from your first contribution to making a meaningful impact.

Mailing Lists

webdev@eclipse-foundation.org (Eclipse Foundation) — Sun, 03 Mar 2019 10:00:00 -0400

Jakarta EE Community	The list is used for updates & connecting with everyone in the ecosystem
Jakarta EE Working Group	The list is used for discussions on topics relevant to Jakarta EE Working Group Members; tackling tasks & working with each other
Jakarta EE Platform	The list is used for technical discussions on topics related to a platform for hosting Jakarta EE Applications
Jakarta EE Technology Compatibility Kits	The list is used for technical discussions on Jakarta EE Technology Compatibility Kits
Jakarta EE Specifications	The list is used for discussions on evolution of Jakarta EE specifications
JakartaEE Spec Project Leadership discussions	JakartaEE Spec Project Leadership discussions
Jakarta EE Marketing	This list is used for discussions on marketing, collateral, branding, devrel, jakartaone and activities related to enhancing the Jakarta EE brand with community collaboration.
Jakarta EE Examples	The list is used for discussions on documentation, samples, tutorials of APIs
Jakarta Activation	The list is used for technical discussions related to standardizing services for MIME type data Access
Jakarta Annotations	The list is used for technical discussions related to declarative style annotations for common semantic concepts
Jakarta Authentication	The list is used for technical discussions related to low-level container SPI for authentication mechanisms
Jakarta Authorization	The list is used for technical discussions related to low-level SPI for authorization modules, which are repositories of permissions
Jakarta Batch	The list is used for technical discussions related to API plus an XML-based batch job specification language
Jakarta Bean Validation	The list is used for technical discussions related to object-level constraint declaration and validation facility.
Jakarta Concurrency	The list is used for technical discussions related to API for application-level concurrency that integrates with the container
Jakarta Config	Jakarta Config project developer discussions
Jakarta Connectors	The list is used for technical discussions related to the architecture connecting applications to enterprise info systems
Jakarta Context and Dependency Injection	The list is used for technical discussions related to declarative dependency injection and supportive services
Jakarta Enterprise Beans	The list is used for technical discussions related to deployment APIs for assembled Jakarta EE applications
Jakarta Expression Language	The list is used for technical discussions related to expression language for Java applications
Jakarta Interceptors	The list is used for technical discussions related to defining means of interposing on business methods
Jakarta JSON Binding	The list is used for technical discussions related to binding framework for converting POJO to/from JSON docs
Jakarta JSON Processing	The list is used for technical discussions related to parsing, generating, transforming and query JSON docs
Jakarta Mail	The list is used for technical discussions related to a framework to build mail and messaging applications
Jakarta Messaging	The list is used for technical discussions related to Jakarta Messaging. Messaging via loosely coupled reliable async services
Jakarta MVC	The list is used for technical discussions related to standardizing the action-based model-view-controller pattern
Jakarta NoSQL	The list is used for technical discussions related to creating applications with NoSQL databases
Jakarta Persistence	The list is used for technical discussions related to management of persistence and object / relational mapping
Jakarta RESTful Web Services	The list is used for technical discussions related to development of web services following the REST pattern
Jakarta Security	The list is used for technical discussions related to standards for creating secure Jakarta EE applications
Jakarta Server Faces	The list is used for technical discussions related to Jakarta Server Faces used for building user interfaces for web apps
Jakarta Server Pages	The list is used for technical discussions related to defining templates engine for web applications
Jakarta Servlet	The list is used for technical discussions related to Jakarta Servlets; handles HTTP requests and responses
Jakarta Standard Tag Library	The list is used for technical discussions related to tags to simplify the JSP development
Jakarta Transactions	The list is used for technical discussions related to handling transactions consistent with X/Open XA-Specs
Jakarta Websocket	The list is used for technical discussions related to API for Server and Client endpoints for Websocket protocol
Jakarta XML Web Services	The list is used for technical discussions related to means for XML-based Web Services based on SOAP

Members

webdev@eclipse-foundation.org (Eclipse Foundation) — Thu, 28 Feb 2019 16:09:45 -0400

Jakarta EE Community Cards

webdev@eclipse-foundation.org (Eclipse Foundation) — Wed, 27 Feb 2019 16:10:38 -0400

Share your participation in the Jakarta EE community with these social media cards!

Save the card you want and share it on the social media platform of your choice.

Remember to use the hashtag #JakartaEE

webdev@eclipse-foundation.org (Eclipse Foundation) — Mon, 04 Jun 2018 10:00:58 -0400

Jakarta EE Newsletters Archives

2020

2019

2018

FAQ

webdev@eclipse-foundation.org (Eclipse Foundation) — Sat, 07 Apr 2018 16:09:45 -0400

Frequently Asked Questions

What is Jakarta EE?

Jakarta EE is the future for cloud-native, light-weight, and traditional enterprise Java applications

Java EE technologies contributed by Oracle are being used to create the new Jakarta EE platform
The Eclipse Foundation is the home of Cloud Native Java open innovation
The Jakarta EE Working Group is focused on modernizing Java EE technologies and governance processes to be more open and community-based

Jakarta EE Trademark Guidelines

webdev@eclipse-foundation.org (Eclipse Foundation) — Thu, 05 Apr 2018 16:10:38 -0400

Supplement to the Eclipse Foundation Guidelines for Eclipse Logos & Trademarks Policy for Jakarta EE Marks

Version 1.2 - March 12, 2020

This document supplements the Eclipse Foundation Guidelines for Eclipse Logos & Trademarks Policy (this Supplement, together with the Eclipse Foundation Guidelines for Eclipse Logos & Trademarks Policy, collectively, the “Policy”) to address the permitted usage of the Jakarta EE Marks (as defined below). The Jakarta EE marks include, but are not limited to, the following names and/or logos: Jakarta EE, Jakarta EE Working Group, Jakarta EE Member, and Jakarta EE Compatible, (collectively the “Jakarta EE Marks”). The full guidelines on the usage of the Jakarta EE Marks are described in the Jakarta EE Brand Usage Handbook. Use of the Jakarta EE Marks must at all times conform to the Policy.