JEP 534: Compact Object Headers by Default
JEP 534, "Compact Object Headers by Default," has been elevated to Candidate status in the OpenJDK enhancement proposal process. The JEP proposes making the compact header layout introduced in JEP 519 — which shipped in JDK 25 — the default object header layout in the HotSpot JVM rather than an opt-in flag.
Compact object headers reduce the per-object metadata overhead in the JVM heap. By shrinking the header from 16 bytes to 8 bytes on 64-bit platforms, heap-intensive workloads can see reduced memory footprint and improved CPU cache efficiency. Applications with millions of small objects — common in data pipelines, ORM-heavy apps, and collection-intensive code — stand to benefit most.
The Candidate status means the JEP has passed initial vetting and is being considered for targeting in a future JDK release. If accepted for JDK 27, it would mean compact headers become opt-out rather than opt-in, significantly broadening coverage without requiring developer changes.
Read more — InfoQ
JEP 533: Structured Concurrency Seventh Preview
JEP 533 brings a seventh preview of Structured Concurrency to the JDK. After completing two incubator rounds in JDK 19 and JDK 20, followed by six preview rounds spanning JDK 21 through JDK 26, this preview introduces minor API refinements while signaling that the feature is close to finalization.
Structured Concurrency treats a group of related tasks as a single unit of work. When the enclosing scope exits — either normally or via exception — all subtasks are automatically cancelled and awaited, eliminating the common pitfall of leaked threads. The API centres on StructuredTaskScope and its two built-in policies: fail-fast on the first failure, or continue until all subtasks complete.
The seventh preview refines error handling and cancellation semantics, improving reliability and observability compared to working directly with ExecutorService. The extended preview cadence reflects the team's deliberate approach to ensuring the API is correct before it becomes a permanent language feature. Developers can provide feedback through the OpenJDK mailing lists or the Java Bug Database.
Read more — InfoQ
Jakarta EE 12 Milestone Timeline Established
The Jakarta EE 12 release has a concrete multi-milestone schedule running through Q1 2027. Milestone 4, covering April through mid-May 2026, delivers RESTful Web Services 5.0-M1, CDI 5.0, JSON Processing 2.2-M1, and JSON Binding 3.1-M1. Subsequent milestones continue through the year, with a Core Profile release targeted at Milestone 7 in Q4 2026 and full Platform TCK finalization at Milestone 10 in March 2027.
Jakarta EE 12 is the next major revision of the enterprise Java platform following Jakarta EE 11. The specification work is coordinated through the Eclipse Foundation's Jakarta EE Working Group and spans multiple component specifications including Servlet, REST, CDI, Persistence, and Security. Each milestone allows adopting implementations such as Open Liberty, GlassFish, and WildFly to align their development against stable in-progress specs.
For Java developers building enterprise applications, the practical implication is that Jakarta EE 12 tooling and framework support will arrive incrementally. Teams running on Jakarta EE 10 or 11 can begin evaluating preview releases against existing codebases once compatible framework versions ship later in 2026.
Read more — InfoQ
Apache Camel 4.19.0: Spring Boot 4.0, Azure Functions, Hybrid Cryptography
Apache Camel 4.19.0 is available with several integration-focused additions. New components include Azure Functions (event-driven processing on Microsoft Azure), Groovy JSON (templated message transformation), and a Spring AI Image component for AI-powered image generation pipelines. Hybrid cryptography support has been added to the Crypto component, allowing mixed symmetric/asymmetric encryption in routes.
The most significant compatibility improvement is Spring Boot 4.0 support. Camel applications relying on Spring Boot can now use the 4.0.x line directly, benefiting from Spring Framework 7 and its improved virtual thread support, without requiring compatibility shims or version downgrades. This alignment is especially relevant for teams migrating Spring Boot services to Java 21+ with virtual-thread executors.
Camel 4.19.0 also ships with the usual set of dependency upgrades, bug fixes, and component-level improvements. Teams using Camel's extensive library of 350+ connectors to build event-driven microservices should upgrade to pick up the Spring Boot 4.0 alignment and the new hybrid cryptography capabilities.
Read more — InfoQ
Links & Sources
You May Also Enjoy
