I will conclude by saying that you should avoid JNI as much as possible (yes you read right, AVOID it). Let your Java code be pure Java. A JNI call made to a native programming language is very slow. JNI is also not compatible with Java applets. Don't use JNI just for the heck of it; use it when it's really required, maybe to perform some extremely low level hardware programming where speed can make or break your application.
I really hope you learnt a thing or two about JNI from this article. Stay tuned for part 2 of this article in which we will further explore some advanced aspects of JNI.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |