The OJI changes have "landed" in the main mozilla sources, and are now being built by default. Look for the OJI API headers in mozilla/modules/plugin/public and mozilla/modules/oji/public. (8/10/98)

The Open JVM Integration project (OJI) is working to extend the browser to allow Java virtual machines to be plugged into Mozilla. At a minimum, OJI will allow the applet tag to work showing Java applets on the page. However we're also striving to provide the full feature set found with Netscape's Java virtual machine in previous releases of the browser including LiveConnect (integration with JavaScript), Composer plug-ins, etc. Most of the OJI project involves extending the existing Plug-in API to define what we're calling the Open JVM Plug-in API. Although some of these are JVM-specific much of the changes are of general interest to plug-in developers.

Our strategy for developing the Open JVM Plug-in API is to enlist the help of third-party JVM providers and the mozilla.org community by periodically posting our source code to mozilla.org and by actively inviting partners to join us in the design and development process. We've set up the netscape.dev.java.open-java news group for discussions. Currently we're working with JavaSoft, Apple and others to make their Java plug-ins be more full featured replacements to the Netscape JVM. We plan to have our partner's JVMs be available at the same time 5.0 is released.

What does this mean for end-users? Several things:

applets, LiveConnect, and Composer plug-ins running in Mozilla,
a choice of Java virtual machines in Communicator 5.0,
backward compatibility with previous Communicator releases,
a chance to migrate to JVMs supporting Java 1.2 and future versions.

For Java developers, this means:

ability to write Java code depending on newer versions of Java and AWT,
backward compatibility for Java code between Communicator releases,
choice of JVMs when deploying Java-based browser applications.

And for Java VM providers:

a vehicle for delivering their Java virtual machine to the web user community,
opportunity to continue to enhance Java support in Mozilla and Communicator.

How can you help? For now we're looking for people who can help review the code we've developed so far, and are willing to work with us to improve things. This includes JVM providers, as well as general plug-in developers. In the future, we'll need people to help us with testing and verification. The code now is primarily located in the following directories:

mozilla/modules/plugin
mozilla/modules/oji

The Open JVM Plug-in API depend on the XP-COM object model which is described in Extending Mozilla. Be sure to read that first, and stay tuned for more documentation and updated headers in the future.

We welcome your comments. Please direct them to netscape.dev.java.open-java or netscape.public.mozilla.general.