Free tools Windows power users keep installed
One-click scans. No signup required.
Jakarta EE 12 is still under development, not generally available. Its data-access direction centers on two evolving specifications: Jakarta Data 1.1, with repository-based APIs and more expressive query construction, and Jakarta Persistence 4.0, a major revision that describes new query and entity-management features. Both specify Java SE 21 or higher as the minimum. The “M2” in the title refers to a dated Jakarta Persistence 4.0-M2 draft—not a milestone release of the whole Jakarta EE 12 platform.
What’s new in Jakarta EE 12?
The official Jakarta EE release overview labels EE 12 “under development.” Its platform page sets Java SE 21 or higher as the minimum and lists changes across the Core Profile, Web Profile, and Platform specifications. In the Web Profile lineup, the data-related specifications include Jakarta Data 1.1 and Jakarta Persistence 4.0.
The platform page also describes updates to Enterprise Beans, Mail, Activation, Batch, and Connectors. It says EE 12 components no longer use Java SecurityManager in their APIs. These are development-page descriptions, not a statement that EE 12 has shipped or that every listed change is final.
Jakarta EE 11, the previous platform release, was announced generally available on June 26, 2025. That announcement said work on EE 12 was underway and targeted for 2026; that was a planning target at the time, not confirmation of a release date or of general availability now. See the EE 11 release announcement.
Recommended Free Tools
#1 Best Overall
What is Jakarta Data 1.1?
Jakarta Data describes a way to work with data through ordinary Java entity objects and repository interfaces whose methods perform operations. As the Jakarta Data 1.1 specification page puts it, “Jakarta Data simplifies data access by allowing you to represent data with simple Java objects (entities), and define interfaces (repositories) with methods that perform operations on it.”
More expressive repository queries
The development page highlights fluent query construction using a metamodel, reusable restrictions, conditional filters, ordering, and projection results represented by Java records. Together, these features aim to let application code describe data operations through repository APIs rather than tying every operation to hand-written persistence-provider code. The page presents these as specification work in progress, not guaranteed behavior in a released EE 12 implementation.
Rank #2
Integration points that remain conditional
Two items on the page are explicitly dependent on other decisions: configuration through Jakarta Config depends on that specification being released and included in EE 12; a possible move of Jakarta Data Query Language to Jakarta Query depends on acceptance and inclusion. Neither should be treated as settled EE 12 behavior until those conditions are met.
What is changing in Jakarta Persistence 4.0?
The Jakarta Persistence 4.0 page presents the work as a major revision, with a minimum Java SE version of 21 or higher. Its development descriptions connect several changes to broader query support and Jakarta Data integration. They are proposals and milestone details; check the actual specification and implementation before relying on them in production.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Detached entities and static queries
The page lists EntityAgent and PersistenceAgent for working with detached entities. It also describes method-level @JakartaQuery, @NativeQuery, and @QueryOptions for static queries and Jakarta Data integration. These features point toward more standard ways to express queries and manage entity workflows, but their final form should be verified against the released specification.
Native-query typing and API cleanup
The proposed API changes include making createNativeQuery() return TypedQuery, removing SecurityManager use, clarifying the entity-name format, and removing deprecated basic-type support for Byte[] and Character[]. The page also describes deprecating various query operations and older APIs. Applications that depend on affected signatures or legacy types should wait for the final specification and assess source compatibility before upgrading.
What does “M2” mean here?
It means Jakarta Persistence 4.0-M2, not Jakarta EE 12-M2. The surfaced Persistence 4.0-M2 document is explicitly marked DRAFT and dated April 22, 2026. Its introduction describes an object-relational mapping facility for Java applications using a Java domain model with relational databases.
The M2 draft’s feature summary mentions EntityAgent, programmatic result-set mappings, static queries, entity-graph and stored-procedure enhancements, and lifecycle events, with support for Jakarta Data usage as a goal. It is a historical milestone: the current Persistence overview lists M4 documents. The M2 draft is useful for understanding development at that point, but it is not the latest milestone or proof of final release behavior.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errorsBest Value
What does Jakarta EE 12 require, and should teams adopt it yet?
The stated platform minimum is Java SE 21 or higher; the Jakarta Data 1.1 and Persistence 4.0 pages give the same minimum. For planning an application or migration, distinguish the platform’s development status from a component’s draft status and confirm that the exact APIs your application needs are supported by a released, compatible runtime.
- Check the platform status. Start with the release overview and platform page for current development status, scope, and Java baseline.
- Check component artifacts. Review the Jakarta Data and Persistence pages for the specification documents, Javadocs, and TCK artifacts available for the versions you intend to use.
- Verify runtime compatibility. The specification catalogue explains that individual specification pages provide compatible implementation information. The EE 12 pages cited here do not establish a complete compatible-runtime matrix, so do not infer compatibility from a vendor’s general Jakarta EE support claim.
- Assess API and source impact. Compare your code’s Java SE baseline and use of Persistence query APIs, deprecated operations, and legacy basic types with the final specification and the runtime’s supported version before upgrading.
Until a compatible implementation and final component specifications are verified for your use case, treat EE 12 as a direction for evaluation rather than a production-ready platform recommendation.
Why the data changes matter
Jakarta Data’s repository abstraction and Persistence’s planned query and entity-management work address related layers: repositories provide a higher-level way to express data operations, while Persistence supplies the object-relational mapping and query machinery that can support them. The connection is the reason the pair is notable for enterprise Java data access; it does not mean every proposed integration is already settled or available.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
