Re: Call system API from Java

On 2/24/20 10:44 AM, Pete Helgren wrote:
> There really isn't any particular reason, it just seems like "native" is the 
> better way to go, especially if I can 1) Learn something new and 2) If the 
> effort isn't a whole lot more than using JT400.

IMO, JNI should be avoided unless absolutely necessary.  It's not portable and 
relatively few developers understand it (TBH, I am clueless when it comes to JNI).

Using standard JT400 mechanisms ensures portability and has a significantly 
higher chance that "Developer-Next" will be able to figure it out.

david

-- 
IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding in the American Diabetes Association's Tour de Cure to raise money 
for diabetes research, education, advocacy, and awareness.  You can make a 
tax-deductible donation to my ride by visiting https://mideml.diabetessucks.net.

You can see where my donations come from by visiting my interactive donation map 
... https://mideml.diabetessucks.net/map (it's a geeky thing).

I may have diabetes, but diabetes doesn't have me!
-- 
This is the Java Programming on and around the IBM i (JAVA400-L) mailing list
To post a message email: [email protected]
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/java400-l
or email: JAVA400-L-request-+hD5IHI5Xscn3HwCXmMcX9BPR1lH4CV8@public.gmane.org
Before posting, please take a moment to review the archives
at https://archive.midrange.com/java400-l.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com