Lines Matching refs:Java

2 JNI (Java Native Interface) is the mechanism that enables Java code to call
3 native functions, and native code to call Java functions.
5  * Native code calls into Java using apis from `<jni.h>`, which basically mirror
6    Java's reflection APIs.
7  * Java code calls native functions by declaring body-less functions with the
8   `native` keyword, and then calling them as normal Java functions.
14 `jni_generator` uses regular expressions to parse .Java files, so don't do
26 Generally Java->Native calls are exported from the shared library and lazily
35 ### Exposing Java Methods
37 Java methods just need to be annotated with `@CalledByNative`. The generated
43 not be `#included` by multiple sources. If there are Java functions that need to
47 ### Calling Java -> Native
72    depend on the location of the `generate_jni` BUILD rule that lists your Java
81 #### Java  subsubsection
120 // Notice that unlike Java, function names are capitalized in C++.
219 ### Calling Native -> Java
229 ### Java Objects and Garbage Collection
231 All pointers to Java objects must be registered with JNI in order to prevent
253 If a Java object "owns" a native one, store the pointer via