Please note, this is a STATIC archive of website from 03 Nov 2016, does not collect or store any user information, there is no "phishing" involved.

Note: The global java object has been removed in Gecko 16.0, so this page is out of date. You should still be able to use the Java plugin's scripting functionality, see LiveConnect for the pointers.

Note bug 834918 about click-to-play effect on Java plugins in chrome and bug 775301.

If you are in need of calling Java code from within a Firefox extension, you can make use of LiveConnect. LiveConnect gives your extension's JavaScript code (linked from or contained in XUL code) access to 2 objects: java and Packages (note that per this thread, although the new documentation for the LiveConnect reimplementation states that these globals will be deprecated (in the context of applets), "Firefox and the Java Plug-In will continue to support the global java/Packages keywords, in particular in the context of Firefox extensions."). These 2 objects let you make use of the standard JDK classes, e.g.,

var aJavaList = new java.util.LinkedList();

If you want to load your own JARs, then you can create your own Java class loader. 

The following technique only works in JavaScript code linked from or contained in XUL files. If you wish to call Java code from within JavaScript code that implements some XPCOM components, at this time, you need a different technique (refer to the complete Java Firefox Extension). A good reason for calling Java from within an XPCOM component rather than from XUL is to maintain a singleton (some singular Java object) across all Firefox windows. If you call Java from XUL, then each Firefox window will have its own class loader and hence its own "singleton".

The following approach is taken from the extension XqUSEme  (note you must use the latest version, currently still in the sandbox, as prior versions only worked with LiveConnect before Java 6 update 11) which borrows some of the code of the Java Firefox Extension in order to grant full privileges to Java within a Firefox extension, but it is easier to understand and doesn't require creation of a XPCOM component. [NOTE: A simpler Hello World version than that below is now available at ]

For privileges, the basic procedure is:

  1. Download and include within your extension (you can also build your own from the source files at )
  2. Build and add references leading to this JAR and all other JARs in your extension within an array of's, pass to to get a class loader, and finally pass the classloader and array to a function which gives the necessary privileges:


// This function will be called to give the necessary privileges to your JAR files
// However, the policy never comes into play, because 
//    (1) adding permissions doesn't add to the policy itself, and 
//    (2) addURL alone does not set the grant codeBase
function policyAdd (loader, urls) {
    try {
        //If have trouble with the policy try changing it to 
        var str = '';
        var policyClass = java.lang.Class.forName(
        var policy = policyClass.newInstance();
        for (var j=0; j < urls.length; j++) {
    }catch(e) {
//Get extension folder installation path... (this works in firefox 3.x, for firefox 4.x use  AddonManager.getAddonByID)
var extensionPath = Components.classes[";1"].
            getInstallLocation("test@yoursite"). // guid of extension

//The path logic would work if we include em:unpack for ff 4.x, for ff 3.x since things are unpacked by default things work

// Get path to the JAR files (the following assumes your JARs are within a
// directory called "java" at the root of your extension's folder hierarchy)
// You must add this utilities (classloader) JAR to give your extension full privileges
var extensionUrl = "file:///" + extensionPath.path.replace(/\\/g,"/");
var classLoaderJarpath = extensionUrl + "/java/javaFirefoxExtensionUtils.jar";
// Add the paths for all the other JAR files that you will be using
var myJarpath = extensionUrl + "/java/TestJava.jar"; 
// seems you don't actually have to replace the backslashes as they work as well

var urlArray = []; // Build a regular JavaScript array (LiveConnect will auto-convert to a Java array)
urlArray[0] = new;
urlArray[1] = new;
var cl =;
//Set security policies using the above policyAdd() function
policyAdd(cl, urlArray);


Now you can begin using LiveConnect, including referencing the classes in your JARs. Be aware that if you have added a namespace within your classes (via "package"), you will need to reference the namespace as well.

var aClass = java.lang.Class.forName("org.mozilla.developer.HelloWorld", true, cl);
var aStaticMethod = aClass.getMethod("getGreeting", []);
var greeting = aStaticMethod.invoke(null, []);

Another, perhaps simpler approach is as follows:

var myClass = loader.loadClass('com.example.myClass'); // use the same loader from above
var myObj = myClass.newInstance();
var binval = myObj.myMethod(arg1, arg2); // Pass whatever arguments you need (they'll be auto-converted to Java form, taking into account the LiveConnect conversion rules)


For more complex cases, in which you need to call a specific constructor with arguments, you will need reflection. The following is a somewhat simplified snippet from XqUSEme:

var reflect = java.lang.reflect;
// Build an array of the class types which are expected by our constructor (in this case, and a class from another JAR we loaded, com.sleepycat.db.EnvironmentConfig)
var paramtypes = reflect.Array.newInstance(java.lang.Class, 2); // 2nd argument should indicate the number of items in following array
paramtypes[0] =;
var envconfigClass = loader.loadClass('com.sleepycat.db.EnvironmentConfig');
paramtypes[1] = envconfigClass;
// Get the constructor
var constructor = envClass.getConstructor(paramtypes);
// Now that we have the constructor with the right parameter types, we can build the specific arguments we wish to pass to it
var arglist = reflect.Array.newInstance(java.lang.Object, 2); // 2nd argument should indicate the number of items in the following array
var mydir = new; // a file URL
arglist[0] = mydir;
var envconfig = envconfigClass.newInstance();
arglist[1] = envconfig;
// Call our constructor with our arguments
var env = constructor.newInstance(arglist);

Be aware that LiveConnect, while now actively supported by Sun has only recently been reimplemented for use in Mozilla, so there may still be some bugs (though many prior LiveConnect bugs, such as try-catch not catching Java exceptions, the failure of auto-converting JavaScript arrays properly, etc., have now been fixed). One example seems to be the fact that the "java" global is not immediately available if the extension operates in a sidebar (using setTimeout solved it at least). I've had problems with stability in the latest XqUSEme when testing in Firefox 3.5b4, especially apparently on Linux (I haven't so far been able to find any workarounds/incompatibilities, but everything is working in Firefox 3.0.10.). I've also experienced crashes in referencing the 'java' global within the XUL Editor of the Extension Developer's Extension which seems to point to some stability problem.

See also

Document Tags and Contributors

 Last updated by: kscarfone,