A proposal to protect the standing of Java Native Interface (JNI) as a normal solution to interoperate with native code is transferring ahead within the Java neighborhood.
Initially created in Could 2023 and up to date on July 16, the JDK enhancement proposal (JEP), referred to as “Put together to Limit the Use of JNI,” is slated for JDK 24, which might not going arrive till March 2025. The proposal requires warnings about makes use of of JNI and adjusting the Overseas Operate & Reminiscence (FFM) API to difficulty warnings in a constant method. These warnings are supposed to arrange builders for a future launch that disallows interoperation with native code by default, whether or not through JNI or the FFM API. As of that launch, builders should explicitly allow the usage of JNI and the FFM at startup.
As well as, the plan would align the usage of JNI and the FFM API in order that library maintainers can migrate from one to the opposite with out requiring builders to vary any command-line choices. Non-goals embrace deprecating JNI or eradicating JNI from the Java platform and limiting conduct of native code referred to as through JNI. For instance, the entire native JNI capabilities would stay usable by native code.
