Java News: Koog 1.0 GA, Endive Wasm Runtime, and Java Framework Releases, 2026-06-06
java

Java News: Koog 1.0 GA, Endive Wasm Runtime, and Java Framework Releases, 2026-06-06

5 min read

Koog 1.0.0 GA: JetBrains' AI Agent Framework Reaches Stable

JetBrains shipped Koog 1.0.0, the first stable release of its open-source Kotlin/Java framework for building AI agents on the JVM. After one year as an incubating project, Koog achieves production-ready API stability with several improvements aimed at teams integrating AI agents into existing Java and Kotlin codebases.

The 1.0 release standardises naming conventions across all Java and Kotlin blocking wrappers, removing the inconsistencies that made type bridging between the two languages awkward. Planner-based agents gain improved persistence and memory performance via a checkpoint/restore mechanism, allowing long-running agents to survive JVM restarts without replaying their full history. HTTP transport is now decoupled from the core framework, giving teams flexibility to swap in their own client implementations for corporate proxies or specialised network configurations.

Koog's agent model is built around graphs of nodes that emit events, which composable pipelines then consume — an architecture that fits naturally with both Spring-managed beans and Quarkus CDI. Teams already using Google ADK, LangChain4j, or A2A can run Koog agents alongside those frameworks rather than replacing them, since Koog deliberately does not own the tool-call dispatch layer.

Read more — InfoQ


Endive: A JVM-Native WebAssembly Runtime Without JNI

Bytecode Alliance introduced Endive, a JVM-native WebAssembly runtime that executes .wasm binaries entirely within the JVM — no JNI bridges, no native libraries, and no platform-specific binaries required. The project is derived from Chicory, which reached its final release at version 1.7.5 in March 2026 before being superseded by Endive's broader scope.

Endive addresses a genuine pain point for Java teams running in restricted environments: existing Wasm runtimes require native code that complicates container builds, cross-compilation, and security sandboxing. A pure-Java Wasm engine can be bundled as a regular JAR dependency, pass the same security audits as the rest of the classpath, and run on any JVM without architecture-specific builds. Teams building plugin systems, sandboxed scripting layers, or portable compute modules will find this particularly compelling.

The project has no formal release yet — Bytecode Alliance has signalled an intent to establish a versioned release process, and Chicory 1.7.5 remains the latest stable artefact for production use. Developers wanting to experiment with Endive should expect an incubation period before any stability guarantees. The introduction to the Java community via the InfoQ roundup marks the project's first public visibility outside the Bytecode Alliance community.

Read more — InfoQ


JEP 538 Extended to Third Preview for JDK 27

JEP 538, PEM Encodings of Cryptographic Objects, will not finalise in JDK 27 as originally planned. Instead it advances to a third preview, incorporating two API refinements prompted by late community review: the PEM record class is reclassified as a regular class to allow future subclassing, and the DEREncodable interface is renamed to BinaryEncodable to better reflect its broader purpose beyond DER-encoded objects.

The extension review was open through June 3, giving implementors an additional cycle to surface integration issues before the API locks. JEP 538 provides an API for encoding and decoding cryptographic keys, certificates, and certificate revocation lists using the Privacy-Enhanced Mail (PEM) transport format — a long-requested capability that currently forces Java developers to reach for third-party libraries or write boilerplate Base64 wrappers. The third preview gives the Java community one more release to confirm the new class hierarchy handles all edge cases before the API becomes permanent.

Read more — InfoQ


Framework Releases: Hazelcast 5.7.0, Quarkus 3.36.0, and Hibernate ORM 7.4.0

Three widely-used Java frameworks shipped point releases this week with updates developers maintaining production systems will want to pick up.

Hazelcast Platform 5.7.0 adds JDK 25 support and graduates dynamic diagnostic logging from beta to GA, enabling runtime log-level changes without a restart or redeployment. The release also improves how mapWithMerging(), mapWithUpdating(), and mapWithEntryProcessor() resolve classes from User Code Namespaces during deserialisation — a fix for a long-standing edge case in multi-classloader environments. Jet backpressure metrics are also enhanced for more accurate monitoring under load.

Quarkus 3.36.0 introduces an experimental Signals extension for loosely coupled component interaction, providing a type-safe publish/subscribe mechanism inside a Quarkus application without requiring an external message broker for in-process coordination. The release also adds OIDC SPIFFE JWT token support for client authentication, enabling deployments in service-mesh environments where workload identity is asserted via SPIFFE/SVID certificates rather than static credentials.

Hibernate ORM 7.4.0 expands its annotation support with @Temporal and @Audited, adds a REFRESH_SESSION option to the CacheMode enumeration so queries can refresh entity state in the persistence context on demand, and introduces official Google Cloud Spanner support covering both the GoogleSQL and PostgreSQL-compatible variants. For teams running Hibernate on Google Cloud, the Spanner dialect removes the need for custom connection configuration.

Read more — InfoQ


Stanislav Lentsov

Written by

Stanislav Lentsov

Software Architect

You May Also Enjoy