Jakarta EE Web Profile 11 Has Been Released

A bit later than originally planned, version 11 of the Jakarta EE Web Profile—maintained by the Eclipse Foundation—has officially arrived, bringing major improvements over previous releases.

The Jakarta EE Web Profile is a subset of the full Jakarta EE Platform, tailored specifically for modern web application developers. It leaves out enterprise-focused APIs to reduce resource usage, offering a lightweight alternative for those who only need web technologies. This makes it a middle ground between basic servlet containers and the full Jakarta EE platform.

Despite its lighter footprint, the Web Profile includes a wide range of technologies. It supports presentation and state management (via Jakarta Faces and Jakarta Pages), business logic (through Jakarta Enterprise Beans Lite), and transaction handling (using Jakarta Transactions). It also includes Jakarta Persistence, which simplifies data storage and access.

New Features in Jakarta EE 11 Web Profile

Jakarta EE 11 introduces several improvements and new specifications aimed at modernizing enterprise Java development.

One of the key additions is Jakarta Data, a new specification that provides a high-level API for easier database access. Similar to Spring Data, Jakarta Data allows developers to perform database operations using repository interfaces: 

@Repository
public interface Garage extends BasicRepository<Car, Long> {

  List<Car> findByType(CarType type);

  Optional<Car> findByName(String name);

}

Jakarta EE 11 is based on Java SE 17 and 21, supporting modern Java features such as records and virtual threads. Beyond the updated Java versions, several core specifications have also been enhanced.

  • Jakarta Persistence now has better support for date/time handling and more powerful JPQL features.

  • Jakarta Concurrency introduces annotations like @Schedule and @MaxConcurrency, and adds support for virtual threads to improve thread safety.

  • Jakarta Security improves support for JWT, adds multiple authentication mechanisms, and introduces an in-memory identity store.

These updates continue the trend of aligning specifications more closely with Jakarta Contexts and Dependency Injection (CDI), creating a more consistent programming model across the platform.

Steve Miller, CEO of Payara, described this release as Jakarta's first major step forward in taking full advantage of Java’s latest capabilities. He emphasized that unlike earlier versions—mostly focused on namespace changes and minor refinements—this release represents a significant evolution.

Currently, the new version is supported by the Eclipse GlassFish container, which was also used during the development process. However, updated versions of other popular Jakarta EE implementations—Open Liberty, WildFly, and Payara—are expected to follow soon, enabling support for applications built with the new Web Profile. 

Share this post
Google Introduces the Agent2Agent (A2A) Open Source Protocol
In a recent speech, Jensen Huang (CEO of NVIDIA) divided the evolution of artificial intelligence into several phases and called the current phase the era of Agentic AI. Although he mainly focused on the next phase of the physical AI era, we should not forget that the Agentic AI era also started only this year, so its fully developed form has not yet been seen. The recent announcement by Google of the open source Agent2Agent protocol gives us a hint of what this more advanced form might look like. The protocol is designed to bridge the gap between AI agents created on different platforms, frameworks, and by various vendors, enabling smooth communication and collaboration.
New Standard Lock File Format for Python Package Management
With the adoption of PEP 751, the Python development community has introduced the pylock.toml format, a uniform and secure solution for managing dependencies. This change addresses a long-standing issue: there was no official standard to ensure that package versions and dependencies were handled consistently across different environments.
Babylon.js 8.0 Has Arrived
After a year of intense development, Microsoft has finally unveiled Babylon.js version 8.0. This new release brings several advanced features that enable faster, more visually appealing, and interactive web experiences. IBL shadows create more realistic environment lighting, while area lights allow for simple yet effective 2D lighting effects. In addition, the Node Render Graph—introduced in its alpha stage—gives developers full control over the rendering process, and the new Lightweight Viewer and WGSL Core Engine shaders help reduce development time and boost performance.
Ten Times Faster After Rewriting the TypeScript Engine in Go
The TypeScript team has tried several times to rewrite the original JavaScript engine in a different programming language, but so far these attempts have not produced the desired results. Recently, however, they announced a breakthrough by rewriting it in Go.