This chapter includes the following topics:
Every new or patch release of Java Plug-in uniquely identifies
CLSID, MIME type and other
resources.This allows multiple JRE versions to be deployed in the
There is a unique CLSID for every new or patch version of Java
CLSID is used in the
with Internet Explorer running on Windows.) If you want a minimum
version of Java Plug-in to be used, then specify this unique
CLSID in the
OBJECT tag. The
CLSID is stored in the registry in:
In general the CLSID looks as follows:
patch version are all
4-digit hexadecimal numbers.
For example, the CLSID for Java Plug-in 6 is as follows:
and you would find this in the registry:
Note that CLSID is also stored in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Code Store Database\Distribution Units\
There is a unique MIME type and
NP*.dll for every
new or patch version of Java Plug-in. MIME type identifies the type
or version of the Java executable to be loaded and initialized by
Java Plug-in. It is specified with the element type in the
EMBED tag with supported Mozilla browsers and with
<PARAM name="type"> in the
OBJECT tag for Internet Explorer. If you want to use a
minimum version of Java Plug-in with supported Mozilla browsers,
specify the unique MIME type in the
MIME type will be supported by an
In general MIME types look like this:
version includes the major, minor and
patch version numbers.
MIME types are supported in the file
NPJPI<modified version number>.dll
For Java Plug-in 1.6.0, the unique MIME type would be:
and it would be supported in the file:
in supported Mozillas
There is a unique Java Plug-in registry key for every new or patch version of Java Plug-in. The main Java Plug-in registry key is as follows:
HKEY_LOCAL_MACHINE\Software\JavaSoft\Java Plug-in\<version number>
where the <version number> includes the major, minor and the patch version numbers.
For Java Plug-in 1.6.0 you will find the following in your registry:
The property file is now named
deployment.properties. It is located in the following
<User Application Data Folder>\Sun\Java\Deployment
<User Application Data Folder> is an
application data folder specific to the user.
As an example, for a user
testuser on a Windows XP
system, the value of
<User Application Data
Folder> would be
The deployment.properties file is used by version 1.6.0. The
<User Application Data Folder> is
obtained from the Win32 API function call
The default location for trace and log files is
Application Data Folder>\Sun\Java\Deployment\log
<User Application Data Folder> is as
javaplugin.outputfiles.path can be
used to override the default location for the trace and log files.
For more information refer to the tracing and logging section in
There is a unique Java Control Panel for every new or patch
release. In 1.6.0, the filename for the Control Panel is
Only the latest installed version of the Java Control Panel is available from the Windows Control Panel.
There are unique registry keys for every new or patch release of the JRE/JDK. These registry keys are located as follows:
HKEY_LOCAL_MACHINE\Software\JavaSoft\Java Runtime Environment\<version number>
HKEY_LOCAL_MACHINE\Software\JavaSoft\Java Development Kit\<version number>
<version number> includes
the major, minor and the patch version numbers; e.g.,
These keys allow Java Plug-in to locate the proper version of the JRE.
Mutliple JRE versions can be installed on Windows platform. With
multiple JRE's applets using MIME type
will work with Mozilla browsers only if you enable the following
To invoke Java Control Panel for a specific version of the JRE
browse to the
<JRE_HOME>/bin directory of that
version and run javacpl.exe.
Multiple versions of the JRE can be run in different browser sessions. However, multiple versions cannot be run in the same browser session. Should this be attempted, the user is warned and the attempt will fail.
Copyright © 1993, 2011, Oracle and/or its affiliates. All rights reserved.