Jakartaee 12 Milestone 2

Jakarta EE 12 Milestone 2 unifies querying across Persistence, Data, and NoSQL via Jakarta Query and embraces Java 21 to deliver a more modern, integrated enterprise Java platform. This TensorBlue analysis is based on reporting and source material from InfoQ (https://www.infoq.com/articles/jakartaee-12-milestone-2/).

What Happened

InfoQ Homepage Articles Jakarta EE 12 Milestone 2: Advent of the Data Age along with Consistency and Configuration

Jakarta EE 12 Milestone 2: Advent of the Data Age along with Consistency and Configuration

Jakarta EE 12 will focus on integration, modernization, consistency and configuration, and improved developer productivity.

Jakarta Query, the new specification in the Jakarta EE Platform, will serve as a unified language for the persistence layer. It will incorporate the Jakarta Persistence Query Language and the Jakarta Data Query Language in one central specification.

The updated versions of Jakarta Data, Jakarta Persistence and Jakarta NoSQL will provide integrations with Jakarta Query.

Jakarta NoSQL provides a new Query interface, similar to its counterpart in Jakarta Persistence, to dynamically set parameters and return a single result as a List, Stream, or Optional.

A new specification, Jakarta Agentic AI, has passed its creation review and will ultimately provide a set of vendor-neutral APIs designed to simplify, standardize, and streamline the process of building, deploying, and operating AI agents on Jakarta EE runtimes.

After the release of Jakarta EE 11 in June 2025, work on Jakarta EE 12 had been well underway, a release poised to deliver improved integrations and alignment with its predecessor.

The second of four milestone releases of Jakarta EE 12 is sc

Implications for Product and Engineering Teams

For TensorBlue readers, the useful question is not just what happened, but how this changes product architecture, engineering priorities, AI delivery, observability, team workflows, or executive decision-making.

• Review whether this changes your AI roadmap, platform architecture, or engineering operating model.
• Identify the specific workflow, reliability, governance, or developer-productivity lesson that applies to your organization.
• Convert the lesson into a small production experiment with measurable quality, latency, cost, adoption, or risk metrics.
• Document source assumptions clearly so teams do not overgeneralize from incomplete public information.

TensorBlue Takeaway

The practical opportunity is to turn this signal into a concrete implementation decision: better AI systems, stronger product instrumentation, more reliable automation, and clearer technical governance. Teams that connect public technology shifts to their own delivery systems will move faster without adding unnecessary complexity.