Jakarta EE 10: What Decision

Makers Need to Know

The Payara® Platform - Production-Ready,

Cloud Native and Aggressively Compatible. Fact Sheet
 Jakarta EE 10: What Decision Makers Need to Know

Contents
Introduction 1
How Did We Get Here? 2
What’s In Jakarta EE 10 3
Removing the Old 3
Consistency is Key 3
Use With the Newest Versions of JDK & Related Technologies 3
Migrating to Jakarta EE 10 4
Future of Jakarta EE 5
Pick Payara For Jakarta EE 10? 5
Payara Advantages When Moving to Jakarta EE 10 6
 Jakarta EE 10: What Decision Makers Need to Know

Introduction
Jakarta EE 10 is the latest release of the Jakarta EE
platform. Start here with this blog for an easy-to-
understand guide to Jakarta EE.

Jakarta EE 10 is an incredibly important release.

This is because it is the first release after the
migration of Java EE from Oracle to the Eclipse
Foundation that actually delivers new features for
future applications.

The release of Jakarta EE 10 demonstrates that the future of

Jakarta EE is assured. It proves that delivering industry-wide
standard APIs through an independent open source foundation
is a successful approach.

With Jakarta EE 10, major industry vendors, Jakarta EE users

and the wider developer community have come together and
delivered a new and exciting platform which is open source
and independent. Any organisation building modern Java
based Enterprise applications should look at using the Jakarta
EE 10 platform as it delivers a set of vendor independent,
standard APIs that can be used to build applications for many
architectures; from a monolith through to microservices; from
intelligent edge devices through to global scale multi and
hybrid-cloud infrastructures.

1
 Jakarta EE 10: What Decision Makers Need to Know

How Did We Get Here?

Jakarta EE 10's roots go way back to 1999 when Sun Microsystems launched J2EE (Java 2 Enterprise
Edition) as a platform for building "Enterprise" applications with the Java programming language.
J2EE introduced APIs needed for building applications that integrate with other components of an
organisation's enterprise architecture including transactional databases, messaging systems, security
services, naming directories and mail services. J2EE underwent a major revision in 2006 to intro-
duce modern annotation programming techniques that removed the need for complex deployment
descriptors. It was renamed “Java EE”.

In 2017, Oracle donated Java EE to the Eclipse Foundation as an independent steward that could
help develop the APIs further to ensure vendor neutrality and open source rules of engagement.
Since then, the Eclipse Foundation worked with the community of vendors, users and developers
to release Jakarta EE 8, which was functionally equivalent to Java EE 8 but released with new open
licensing. It also released Jakarta EE 9, which was functionally equivalent to Jakarta EE 8 but in the
new "jakarta" API namespace. Finally, with the release of Jakarta EE 10, the community has come
together to deliver new capabilities for development.

2
 Jakarta EE 10: What Decision Makers Need to Know

What’s In Jakarta EE 10
The key words for Jakarta EE 10 are Simplicity, Modernization and Lightweight.

Removing the Old Consistency is Key

The Jakarta EE platform has been simplified. In addition, more consistency has been intro-
Due to the long history of Jakarta EE and the duced into the platform to enable APIs to work
level of backwards compatibility and stability it better together and deliver a simpler experience
has delivered for enterprise application devel- for developers. The standard compatibility test
opers, Jakarta EE had a lot of old APIs remaining suites required for implementations to run to
in the platform. With Jakarta EE 10, the API and guarantee API compliance have also been sim-
platform developers have taken the opportunity plified, which lowers the bar in complexity for
to remove a lot of old deprecated features and future innovative runtimes like Payara Micro to
APIs. This makes it easier to use for developers become certified.
and maintainers of the APIs, as well as making
it easier for new runtimes to become compliant
with the API standards.

Use With the Newest Versions of JDK & Related Technologies

Many of the APIs have been modernized to use with the latest Java technology. Jakarta EE 10
APIs use Java 11 as a baseline for source code compatibility and enable implementations like the
Payara Platform to run and certify on JDK 17, the latest Java LTS version. APIs have also evolved
to support modern infrastructure, the latest protocols and security technologies, for exam-
ple OAuth.

3
 Jakarta EE 10: What Decision Makers Need to Know

You Don’t Have to Choose Between Jakarta EE

and GraalVM
Jakarta EE 10, with the removal of a number of deprecated specifications
and APIs, is inherently smaller and more lightweight than its predecessors.
With simplification and better coherence across APIs, it is also more
lightweight when developing applications and understanding all the
capabilities of the platform for building Enterprise applications.

Jakarta EE 10 also introduces the Core Profile which is a small subset

of the full platform APIs, which acts as a foundation for building RESTful
microservices. Core Profile brings APIs for REST, JSON processing
and dependency injection into a small subset. This enables small
microservices focused runtimes that want to use GraalVM to build native
Java microservices to be created and certified as
Jakarta EE compatible. Core Profile will likely form
the foundation of the forthcoming MicroProfile 6
release.

Start here with this blog for an easy-to-understand

guide to MicroProfile.

Migrating to
Jakarta EE 10
If you are migrating old Jakarta EE or Java EE applications from a previous
version of Java EE or Jakarta EE, then there are some breaking changes
to contend with.

First and foremost, if you are migrating from Jakarta EE 8/Java EE 8 or

below, there is the namespace change. When migrating the APIs from
Oracle to the Eclipse Foundation, the top level package namespace
for all the APIs was changed from javax to jakarta to reflect the
change in stewardship of the APIs. Migrating to the new namespace is
simply a matter of changing all imports of javax APIs to use the new
jakarta namespace.

Second, with the simplification and modernization of the Jakarta EE 10

APIs, it is possible that an old application uses old, deprecated APIs.
These applications will require manual code changes to move them to
new APIs.

4
 Jakarta EE 10: What Decision Makers Need to Know

If you are thinking of migrating to Jakarta EE from other frameworks that target Enterprise appli-
cation development in Java, you can take advantage of the longevity and vendor independence of
Jakarta EE. You will find APIs available for all the capabilities required of any modern Enterprise
application. In fact, many other frameworks use directly or "wrap" underlying Jakarta EE APIs as
they are foundational. You will also find that Jakarta EE runtimes support all the deployment models
you are familiar with from uber-JAR, through to remote server deployment, and container packaging
for container services and Kubernetes.

Future of Jakarta EE
With Jakarta EE 10, the Jakarta EE community have demonstrated that further development and
evolution of Java EE APIs through an open source foundation is both possible and productive.

With the support of the majority of major Java industry vendors and the developer community,
Jakarta EE will now start to develop at pace with regular releases delivering further enhancements
and new APIs. We expect to see further consistency and coherence to take place across the set of
current Jakarta EE APIs, to deliver increases in developer productivity.

New APIs will be introduced, with a number of APIs already proposed. These include Jakarta Config
to standardise access to sources of application configuration; Jakarta RPC to standardise vendor
gRPC support; Jakarta NoSQL to standardise access to NoSQL databases and Jakarta Data to sim-
plify data access for applications that don't need Jakarta Persistence. In addition, existing APIs
will gain new features and be upgraded to support the latest Java JDKs and future protocols and
technologies in the industry. Finally, with the introduction of Core Profile Jakarta EE, runtimes will
continue to innovate and support deployment targets ranging from AWS Lambda through to hyper-
scale hybrid cloud deployments.

Pick Payara For Jakarta EE 10?

Payara provides stable, supported runtime software based on Jakarta EE and MicroProfile standards.
Try for free, buy for your mission-critical applications.

Derived from GlassFish, Payara Server is its easy and optimal replacement and a powerful alternative
to JBoss EAP, WildFly, WebSphere and more.

Payara Server Enterprise is designed for mission critical production systems in any environment: on
premise, in the cloud, or hybrid.

Payara Micro is an alternative to the likes of Quarkus, Helidon and OpenLiberty.

5
 Jakarta EE 10: What Decision Makers Need to Know

Payara Advantages When Moving to Jakarta EE 10

The latest version of Payara Server is Payara Platform Version 6: Payara 6 Community and Payara 6
Enterprise. It is designed as a Jakarta EE 10 compatible platform, released in alignment with Jakarta
EE 10’s launch.

Jakarta EE 10 is exciting, but getting there will take work. Here is how Payara can help ease the
process for you:
• Payara 6 Community allows you to try using Jakarta EE 10 straightaway, in our platform for
innovation and development.
• Payara 6 Enterprise, designed for mission-critical applications, will provide tools to
automate the namespace change.
• Payara will provide migration guides with clear examples of how to move from old APIs that
are not included in Jakarta EE 10.
• If your team is composed of software engineers and you lack server experts, you will
benefit from having the Payara engineers on hand during this significant move. Rather than
hiring new team members, save net costs by entering into a Payara Enterprise contract and
gaining the help of our engineers as and when you need them.
• Our team were key to the development of Jakarta EE 10 – we are Strategic Members of the
Jakarta EE Working Group at the Eclipse Foundation. So with a Payara Enterprise contact,
you can take advantage of Jakarta EE 10 features whilst getting support directly from those
who built it.
• There is no limit to the number of tickets you can raise during our support contract. Our
engineers are Jakarta EE experts and have knowledge your team may not have.
Not only will you be able to use Jakarta EE 10 and take advantage of its features almost immediately
with Payara, but you will be more secure during the process with a Payara Enterprise contract.

Speak to one of our Team here to enquire about Payara Enterprise

  
[email protected] UK: +44 800 538 5490 www.payara.fish
Intl: +1 888 239 8941

Payara Services Ltd 2022 All Rights Reserved. Registered in England and Wales; Registration Number 09998946
Registered Office: Malvern Hills Science Park, Geraldine Road, Malvern, United Kingdom, WR14 3SZ