|
Joe Pluta wrote: > > Found it in the FAQ. > > http://faq.midrange.com/data/cache/282.html > > Very nice FAQ, by the way. Now it's a business decision. Do I really > want to include all of that in every program? Even though it's already > written, my concern is that the interface may change on a subsequent > release (like the change where you cannot start more than one JVM in a > job). > I don't think the actual interface to the JNI functions will ever change, but by using the a service program with RPG wrappers for the JNI functions, you can isolate your RPG programs from any interface change. (As far as I know, Sun hasn't changed the object management JNI functions since JDK 1.1 of Java. They did change the invocation API, but not since JDK 1.2, and the change was upward compatible assuming you had JDK 1.1 available.) I suppose a big change like one-JVM-per-job could affect you, but hopefully that kind of change won't happen very often. If it did, it would probably affect you whether or not you were doing object cleanup in your RPG programs.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.