Jakarta EE 11 Example Applications

Introduction

This repository complements the presentations, Getting Started with Jakarta EE 11 and What’s New in Jakarta EE 12, A Developer’s Guide to Jakarta EE 11 and Jakarta EE 11: Going Beyond the Era of Java EE

Getting Started with Jakarta EE 11 and What’s New in Jakarta EE 12 has been presented at these conferences and webinars:

• Dublin Java Users Group, September 25, 2025

• Jakarta Tech Talk, June 25, 2025

• SouJava 30Y #Celebration Week (Day One), June 16, 2025

A Developer’s Guide to Jakarta EE 11 has been presented at these conferences and webinars:

• Devnexus 2025, March 5, 2025

• jChampions 2025, January 24, 2025

• JakartaOne 2024, December 3, 2024

• Jakarta Tech Talk, August 14, 2024

Jakarta EE 11: Going Beyond the Era of Java EE has been presented at these conferences and webinars:

• Devnexus 2024, April 11, 2024.

• Payara Virtual Conference, December 14, 2023

• Jakarta Tech Talk, December 13, 2023

• JCON World, November 21, 2023

• Philly Java Users Group, November 15, 2023

Example Applications

Each folder contains a demonstration of a Jakarta EE specification:

• Jakarta Concurrency

• Jakarta Data

• Jakarta Mail

• Jakarta NoSQL

• Jakarta RESTful Web Services

• Jakarta Security

• Jakarta Servlet

• Jakarta Validation

There is also an example of the new MicroProfile JWT Bridge specification. Introduced in the Summer of 2023, this specification is still a work-in-progress. It has already been decided that this new specification will be maintained in the MicroProfile set of standalone specifications, and was originally anticipated to be included in MicroProfile 7.0, released on June 19, 2024.

Documentation

Please refer to the corresponding README.adoc files under each project.

Corresponding documentation for each Jakarta EE specification may be found under the spec directory and will be automatically be generated upon executing mvn clean package.

Naming Conventions Used in This Repository

For each demo application, there is an effort to provide a consistent set of naming conventions. While things may be slightly different in some demo applications, these are:

• <specficationName>App.java

• <specificationName>Application.java

• <specificationName>Resource.java

• <specficationName>Service.java

The root endpoint will match the name of each folder

• http://localhost:8080/<specificationName>;