Java and SNA: A case study

By Matt MacKinnon, Adam King, David Kaminsky
2003-05-24

Diversion: Native Calls and Applets

There is one drawback to implementing native methods: They can't be called from applets. If the reader were to download our library, write an applet that used it, and then try to run the applet on (for example) a Netscape browser, he would trigger a security exception.

The reason is simple: Applets are not permitted to make native calls. ("delete *.*" is a native call--do you want arbitrary applets issuing that?) However, in an intranet, certain applets will be trusted, at least sufficiently trusted to call another networking protocol. We expect that browser manufactures will implement more flexible applet-security policies. Until then, SNA applications will have to be run as applications.

Tutorial Pages:
» Java and SNA: A case study
» The Java/CPI-C API
» Classic Transaction #1: The Pipe
» Classic Transaction #5: The Database Update
» Native Calls
» Diversion: Native Calls and Applets
» Performance
» CPIC Calls That Have Been Implemented
» Conclusions
» Footnotes

First published by IBM DeveloperWorks

Related Tutorials:
» All about JAXP, Part 1
» Make Database Queries Without the Database
» Load List Values for Improved Efficiency
» 2 Ways To Implement Session Tracking
» A Simple Way to Read an XML File in Java
» Develop Aspect-Oriented Java Applications with Eclipse and AJDT