The Java environment in which Java class files are executed is a subsystem with its own policies. C/C++ on the other hand being a legacy language is likely to have its own set of policies.
What I am trying to say is when you use JNI on a mammoth scale, you are going to have problems. You lose your write once run anywhere advantage of java as your C code may produce unexpected problems on another machine. It may also be slow because your code is entering a whole new different environment, security policies may throw an error anytime and there lots more areas where errors can occur.
I said this in part 1 and I say it again: use JNI only when you really need to.
| 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. |
Java 
/ 37 
Interacting With C From Java With JNI: Part 1/2
