JDK 28 JEPs Advance: Simple JSON API, Strict Field Initialization, and More
Four JEPs moved forward toward JDK 28 this week, giving the earliest signal yet of what the September 2026 release will contain. JEP 540, Simple JSON API (Incubator), was promoted from JEP Draft to Candidate status. It defines a built-in API for parsing and generating JSON documents that implements RFC 8259, without requiring an external library, and formally supersedes the earlier JEP 198 proposal from years ago. For teams currently pulling in Jackson or Gson purely for lightweight JSON handling in small services or command-line tools, this closes a long-standing gap in the standard library.
JEP 539, Strict Field Initialization (Preview), was elevated from Candidate to Proposed to Target. It requires that object fields be initialized before they can be read, closing off a long-standing JVM loophole where partially-constructed objects could leak default values such as 0 or null to other threads or callers during construction. The JEP notes the feature is available for use by compilers that emit class files, meaning tooling authors will need to adapt bytecode generation to the new invariant.
JEP 401, Value Objects (Preview), also advanced from Candidate to Proposed to Target for JDK 28. Value objects are a language construct made up entirely of final fields with no object identity — two value objects are considered equal solely based on the values of their fields, unlocking JVM-level optimizations like flattened field layout and reduced heap indirection for classes that don't need identity semantics.
Separately, JEP 541, Deprecate the macOS/x64 Port for Removal, was elevated to Candidate status. Oracle is signaling the end of x64 macOS builds now that Apple no longer supports the architecture on current hardware, giving teams still running Java on Intel Macs a heads-up to plan a migration path to Apple Silicon builds.
Read more — InfoQ
Embabel 1.0, Azul Payara 7.2.0, and Helidon 4.5.1 Reach General Availability
Embabel, an agent platform for the JVM, shipped its 1.0 GA release, promoting several previously experimental APIs — including the TokenCountEstimator interface — to stable status. The release adds improved observability by exposing MCP server health through Spring Boot Actuator endpoints and integrates support for the Z.ai GLM model family, making it easier to build and monitor JVM-native agentic applications alongside existing Spring Boot infrastructure.
Azul shipped Payara 7.2.0 across three editions: Community 7.2026.7, Enterprise 6.40.0, and Enterprise 5.89.0. The Jakarta EE application server release adds backwards compatibility for defining implicit CDI beans, supports version-pinning of deployment descriptors, and patches CVE-2024-9342 — teams running Payara in production should prioritize the upgrade for the security fix alone.
Helidon 4.5.1 also reached GA with a notably security-focused changelog: the microservices framework now requires authentication by default for GraphQL requests, strips cookies and authorization headers on cross-origin redirects, and encrypts OIDC access-token cookies by default. Teams running Helidon services that rely on GraphQL or OIDC login flows should review these changes before upgrading, since the new defaults are stricter than prior releases and could change existing request behavior.
Read more — InfoQ
Links & Sources
You May Also Enjoy
