Java News Roundup May 2026: JEPs for JDK 27, Azul Payara Community, WildFly, LangChain4j, OpenXava, and Google ADK

Java News Roundup May 2026: JEPs for JDK 27, Azul Payara Community, WildFly, LangChain4j, OpenXava, and Google ADK

InfoQ’s May 11, 2026 Java roundup highlights a set of strategic moves shaping the Java platform and its surrounding ecosystems. Four JEPs targeting JDK 27 advance through review, with potential implications for default runtime behavior, memory layout, and vector-accelerated workloads. At the same time, vendor-led moves—Azul’s Payara branding, and WildFly tooling—alongside maintenance releases from Micronaut, LangChain4j, OpenXava, and Google ADK—signal an ecosystem increasingly oriented toward cloud-native deployments and AI-enabled development. For engineering leaders, the signal is clear: platform evolution is becoming more intentional about defaults, security, and integration with AI tooling, while tooling and distribution strategies are converging to improve developer velocity and production reliability. The original reporting comes from InfoQ’s Java news roundup, and deeper details live on the respective project pages.

The rebrand is part of bringing Azul Payara Community properly into the Azul portfolio alongside Azul Zulu (OpenJDK), Azul Prime, Intelligence Cloud and Azul Payara’s commercial offering. It's the same open-source project with a new home in the broader Azul ecosystem.

Dominika Tasarz-Sochacka, Senior Developer Advocate, Payara Community, Jakarta EE & Foojay.io at Azul

• JEP 523: Make G1 the default Garbage Collector in all environments for JDK 27; review expected to conclude May 19, 2026.
• JEP 534: Compact Object Headers by Default; default object header layout to the pre-existing compact header design; review expected to conclude May 19, 2026.
• JEP 537: Vector API (Twelfth Incubator); continued incubation with runtime-optimized vector code paths; review expected to conclude May 19, 2026.
• JEP 538: PEM Encodings of Cryptographic Objects; API for PEM encoding/decoding of keys, certificates, and CRLs; changes include class and interface renames and reclassifications.
• macOS/x64 port maintenance ends with JDK 27 per Apple’s platform shift; ongoing maintenance requests are noted but limited.
• Build 22 of the JDK 27 early-access line released, with fixes and notes in the release notes.
• Azul Payara Community branding follows a rebrand for Payara Platform Community; Jakarta EE 11 support and descriptor updates in May 2026 release.
• Micronaut Framework 4.10.14; Netty 4.2.13 dependency upgrade addressing CVEs; maintenance and bug fixes.

Beyond the JEPs, the roundup notes concrete product-level moves with potential workflow impact. The Vector API’s twelfth incubator could accelerate data-intensive Java workloads, but teams should anticipate an incubation period and plan compatibility testing against current code paths. PEM encodings are a pragmatic enhancement for cryptographic material exchange, but will require updates to tooling and PKI pipelines to align with the new encoding semantics. The macOS/x64 port ending maintenance poses a porting and scheduling challenge for teams relying on that platform, while the Build 22 EA notes offer a snapshot of ongoing JDK 27 stability and bug fixes. For operators and cloud teams, the announcement about WildFly’s wado CLI and the LangChain4j 1.15.0 release highlights a push toward container-friendly tooling and AI-enabled Java services.

On the product-side branding and ecosystem alignment, Azul Payara Community’s rebrand centralizes the open-source Payara effort within Azul’s broader portfolio. The May 2026 Payara 7 updates emphasize Jakarta EE 11 compatibility and streamlined deployment descriptors, signaling a tighter integration with Azul’s OpenJDK and commercial offerings. Micronaut’s maintenance release reinforces a continued commitment to security through Netty upgrades, while OpenXava and Google ADK updates showcase ongoing maturation of lightweight Java development and AI-assisted tooling. Collectively, these moves underscore a practical path for engineering teams: build with a stable core, adopt AI-oriented tooling where it improves developer velocity, and plan migrations that anticipate default-behavior changes in the JVM.