TornadoVM 6.0 Replaces JNI with the Foreign Function & Memory API
TornadoVM, the GPU/FPGA acceleration framework for Java, shipped version 6.0.0 with a significant internal rewrite. The project replaced its Java Native Interface (JNI) bindings with the modern Foreign Function & Memory (FFM) API, which was finalized as JEP 454 back in JDK 22 and has matured into the standard way for JVM libraries to talk to native code without the boilerplate and safety pitfalls of JNI.
The release also eliminates TornadoVM's experimental dependency on JVMCI (the JVM Compiler Interface), moving instead to a combination of reflection, ASM bytecode manipulation, and the sun.misc.Unsafe layer. This reduces TornadoVM's coupling to internal JVM compiler APIs that can shift between releases, which should make the project easier to keep current as new JDK versions ship.
On the hardware side, TornadoVM 6.0 expands CUDA backend support across JDK 21, 25, 26, and 27 — meaning teams running GPU-accelerated Java workloads (image processing, numerical simulation, ML inference kernels written in Java) aren't locked into a single JDK line to get CUDA acceleration.
Alongside TornadoVM, this release wave brought Micronaut Framework 5.1.3 (built on Micronaut Core 5.1.13, with patch updates spanning SQL libraries, Micrometer, OpenAPI/Swagger, OpenSearch, Email, Reactor, Data, and AWS integrations) and a matching GraalVM Development Kit 5.1.3, which now supports generating and building Micronaut applications targeting JDK 25 through the GDK Launcher and CLI tooling.
Read more — InfoQ
JHipster 9.3.0 Adds Full Spring Boot 4 Support, LangChain4j Goes Reactive
JHipster 9.3.0 landed with full support for Spring Boot 4, Jackson 3, and Angular 22 — closing the gap for teams generating full-stack Spring applications who have been waiting to move off the Spring Boot 3 / Jackson 2 baseline. Reactive JHipster applications are now built with Vite instead of the previous webpack-based tooling, and the generator's Testcontainers integration tests consistently use the @ServiceConnection annotation, cutting down on manual container wiring in generated test code.
Separately, LangChain4j 1.20.0 introduced experimental non-blocking and reactive support, returning CompletableFuture<T> and Flow.Publisher<T> from its APIs instead of forcing callers into synchronous blocking calls — a meaningful change for anyone wiring LLM calls into reactive Spring WebFlux or Vert.x pipelines. The release also adds opt-in support for Jackson 3's JSON SPI.
Rounding out the same release wave: Java Operator SDK 5.6.0 introduced a new InformerPool interface that lets multiple controllers and event sources share informers rather than each maintaining its own, and relocated EventRecorder configuration to ConfigurationService.eventRecorder(). JReleaser 1.26.0 improved Snapcraft support with a new platforms node in generated snapcraft.yml files (deprecating the old runOn() method in favor of buildFor()). The Kotlin Toolchain hit 0.12.0 with expanded multiplatform library publishing and the ability to run WebAssembly apps via kotlin run. And Yupiik Fusion 1.1.0 added a JsonSchemaService implementing the Draft 2020-12 JSON Schema spec.
Read more — InfoQ
Links & Sources
You May Also Enjoy
