| Java Native Interface |
Article Index for Java |
Website Links For Java |
Information AboutJava Native Interface |
| CATEGORIES ABOUT JAVA NATIVE INTERFACE | |
| java platform | |
|
The JNI is used to write native methods to handle situations when an application cannot be written entirely in the Java programming language such as when the standard Java Class Library does not support the platform-specific features or program library. It is also used to modify an existing application, written in another programming language, to be accessible to Java applications. Many of the standard library classes depend on the JNI to provide functionality to the developer and the user, e.g. I/O file reading and sound capabilities. Including performance- and platform-sensitive API implementations in the standard library allows all Java applications to access this functionality in a safe and platform-independent manner. Before resorting to using the JNI, developers should make sure the functionality is not already provided in the standard libraries. The JNI framework lets a native method utilize Java Objects in the same way that Java code uses these objects. A native method can create Java objects and then inspect and use these objects to perform its tasks. A native method can also inspect and use objects created by Java application code. JNI is sometimes referred to as the "escape valve" for Java developers because it allows them to add functionality to their Java Application that the Java API can't provide. It can be used to interface with code written in other languages, like C++. It is also used for time-critical calculations or operations like solving complicated mathematical equations, since native code can be faster than JVM code. The JNI is not trivial and requires a considerable effort to learn, and some people recommend that only advanced programmers should use the JNI. However, the capability for Java to communicate with C++ and assembly removes any limitations on what function Java programs can perform. Programmers considering using the JNI should be aware that # as mentioned before, the JNI is not an easy API to learn; # only applications and signed applets can invoke the JNI; # an application that relies on JNI loses the platform portability Java offers (a workaround is to write a separate implementation of the JNI code for each platform and have Java detect the Operating System and load the correct one at runtime); # there is no garbage collection for the JNI side (JNI code must do explicit deallocation); # error checking is a MUST or it has the potential to crash the JNI side and the JVM . HOW THE JNI WORKS In JNI, native functions are implemented in a separate .c or .cpp files. (C++ provides a slightly cleaner interface with JNI.) When the JVM invokes the function, it passes a JNIEnv pointer, a jobject pointer, and any Java arguments declared by the Java method. A JNI function may look like this:JNIEXPORT void JNICALL Java_ClassName_MethodName
{ //Implement Native Method Here } The '' env'' pointer is a structure that contains the interface to the JVM. It includes all of the functions necessary to interact with the JVM and to work with Java objects. Example JNI functions are converting native arrays to/from Java arrays, converting native strings to/from Java strings, instantiating objects, throwing exceptions, etc. Basically, anything that Java code can do can be done using JNIEnv, albeit with considerably less ease.For example, the following converts a Java string to a native string:
{ //Get the native string from javaString
//Do something with the nativeString //DON'T FORGET THIS LINE!!! env->ReleaseStringUTFChars(javaString, nativeString); }
{ //Get the native string from javaString
//Do something with the nativeString //DON'T FORGET THIS LINE!!!
}
Native Data Type s can be mapped to/from Java data types. For compound types such as objects, Array s and String s the native code must explicitly convert the data by calling methods in the JNIEnv.MAPPING TYPES The following table shows the mapping of types between Java and native code. In addition, the signature "L fully-qualified-class ;" would mean the class uniquely specified by that name; e.g., the signature "Ljava/lang/String;" refers to the class java.lang.String. Also, prefixing [ to the signature makes the array of that type; for example, [I means the int array type.Here, these types are interchangeable. You can use jint where you normally use an int, and vice-versa, without any Typecast ing required.
JNIEXPORT void JNICALL Java_ClassName_MethodName
{ printf("%s", javaString); }
JNIEXPORT void JNICALL Java_ClassName_MethodName
{ //Get the native string from javaString
printf("%s", nativeString); //DON'T FORGET THIS LINE!!! env->ReleaseStringUTFChars(env,javaString, nativeString); } This is similar with Java arrays, as illustrated in the example below that takes the sum of all the elements in an array.
JNIEXPORT jint JNICALL
{ int i, sum = 0; for (i = 0; i < 10; i++) { sum += arr {Link without Title} ; } return sum; }
JNIEXPORT jint JNICALL
{ jint buf {Link without Title} ; jint i, sum = 0; env->GetIntArrayRegion(arr, 0, 10, buf); for (i = 0; i < 10; i++) { sum += buf {Link without Title} ; } return sum; } Of course, there is much more to it than this. Look for links below for more information. In each native call JNIEnv argument is only valid during the call. To use the argument outside the call you need to use AttachCurrentThread and DetachCurrentThread, like so:
// do stuff
-- NATIVE AWT PAINTING Not only can native code interface with Java, it can also draw on a Java , which is possible with the Java AWT Native Interface . The process is almost the same, with just a few changes. The Java AWT Native Interface is only available since J2SE 1.3. MICROSOFT'S RNI Microsoft's implementation of a Java Virtual Machine has a similar mechanism for calling native Windows code from Java, called the Raw Native Interface ('''RNI'''). SEE ALSO
EXTERNAL LINKS
> |
|
|