The Mozilla
Organization
At A Glance
Feedback
Get Involved
Newsgroups
License Terms
Newsbot
Developer Docs
Roadmap
Projects
Ports
Module Owners
Hacking
Get the Source
Build It
Testing
Download
Bugzilla
Bug Writing
Tools
View Source
Tree Status
New Checkins
Submit A Bug
FAQ
Search

open jvm integration

Contact: Ed Burns (edburns@acm.org)
Last Updated: 29 August 1999;

Latest Status

also check the mozilla.org status update page for more information
  • Applets are up and running on WinNT and Mac. UNIX support is stuck waiting for the Java Plugin implementation. If anyone is interested in writing an OJI plugin, see the document Introduction to OJI Internals. This document is an introduction to the topic of what Mozilla requires of an OJI plugin.
  • Mac users! For information on how to get MRJ working in your 4x version of Communicator, go here (3.22.99)

The Open JVM Integration project (OJI) is working to extend the browser to allow Java virtual machines to be plugged into Mozilla. OJI will allow the applet and object tags to show Java applets on a page and support LiveConnect (the bridge between Java and JavaScript). 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.public.mozilla.oji 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 and LiveConnect 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 XPCOM 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.public.mozilla.oji or netscape.public.mozilla.general.

Copyright © 1998-1999 The Mozilla Organization.
Last modified October 9, 1999.