With fix to bug 4504166 (performance problem in deploying Java optional packages) we need to make some changes to deploying java extensions in the plugin doc.

Since we only look at the extensions listed in the Extension-List, instead of looking at all the extensions in the extension directory (<jre>/lib/ext) trying to find a match, we need to make sure the user understands that the extension name in the Extension-List needs to be correct.

Changes:
--------------------------------------------------------------------
In Overview 1.MANIFEST of the applet's JAR files

Change sentence to:
If the applet requires Java Extensions, the applet MUST define the
list of Java Extensions it requires and specify the URLs from which to
download the extensions, along with other information about the Java
Extensions in the applet's JAR MANIFEST.

--------------------------------------------------------------------
In Overview 1.MANIFEST of the applet's JAR files
or
Specifying Java Extensions in the Applet

Add sentence:
The extension name in the Extension-List and the prefix of the other
manifest attributes must be a name of the extension JAR file that is installed
in the extension directory ({JRE}/lib/ext). Some Java Extensions consist of several
JAR files. For example optional package Java3D installs the following JAR files
in the extension directory: j3daudio.jar, j3dcore.jar, j3dutils.jar, vecmath.jar.
For these Java Extensions only one of the Java Extensions JAR file names must be
used in the Extension-List and the prefix of the other manifest attributes.
Usually the optional package has a main JAR file and that is the one you
would want to use in the Extension-List and the prefix of the other manifest
attributes.

Here is an example of the applet's manifest using optional package Java 3D.

Extension-List: j3dcore
j3dcore-Extension-Name: javax.media.j3d
j3dcore-Implementation-Vendor-Id: com.sun
j3dcore-Implementation-Version: 1.2.1_03
j3dcore-Implementation-Title: Java 3D Core Runtime Environment
j3dcore-Specification-Title: Java 3D API Specification
j3dcore-Specification-Version: 1.2
j3dcore-Specification-Vendor: Sun Microsystems, Inc
j3dcore-Implementation-URL: http://&lt;some server>/native/java3d-$(os.name)$.jar


--------------------------------------------------------------------
In II. Make the applet JAR file and HTML file

In Extension-List change jai to jai_core
For the prefixes change jai to jai_core-{attribute}

--------------------------------------------------------------------
In II. Make the applet JAR file and HTML file

Where it talks about $(os-name)$ list the OS's that $(os-name)$
can translate to.
SunOS, Linux, Windows-98, Windows-NT, Windows-2000, Windows-Me.

--------------------------------------------------------------------
In Known Limitations

Change sentence
From:
If the Java Extensions consists of several JAR files and is installed through
Java/native installer, only one of the JAR files is required to have the
extensions versioning information. However, for raw extensions installation,
each JAR files must contain the proper extensions versioning information.

To:
If the Java Extension consists of several JAR files and is installed through
a Java or native installer, only one of the JAR files is required to have the
extensions information (i.e. Extension-Name, Specification-Version, etc.). If
you do this you need to make sure that the extension JAR file that has the
information is the one used in the Extension-List (in applet JAR manifest) for
the Java Extension. For raw extensions installation, each JAR files must
contain the proper extension information.

--------------------------------------------------------------------
In Known Limitations

Remove sentence:
If the applet consists of several JAR files, only one of them is required to
have the extensions versioning information if Java Extensions installation is
used. We recommend putting the versioning information in the first JAR specified
in the archive/cache_archive attribute to speed up the extensions download.

--------------------------------------------------------------------
In Known Limitations

Change "Known Limitations" to "Known Limitations and Other Notes"

*****

All changes and additions have been made other than the first -- change of wording in Overview 1. Manifest. Suggested change seemed to say the same thing but had wording problems.

Bug will be closed shortly unless issues are raised.

###@###.### 2002-04-26