-
Bug
-
Resolution: Won't Fix
-
P3
-
None
-
None
section 11.3 of http://docs.oracle.com/javase/8/docs/technotes/guides/deploy/applet_dev_guide.html says:
"Applets can be deployed by hand-coding the applet, object or embed tags with the required parameters. This section describes these parameters. "
however no place in this section (or any other I can find) are all the parameters listed, only examples of some of them are described. Same with the attributes.
of particular example are "archive", "archive_ex", and "cache_archive" (which are not really parameters, but attributes the applet, embed, or object tags)
"archive" is used in example but never defined.
"cache_archive_ex" is never mentioned
"cache_archive" is defined but wrongly:
it says (in section 11.3.7):
"Like the archive attribute in the applet tag, the list of jar files in the cache_archive attribute do not contain the full URL, but are always downloaded from the codebase specified in the embed or object tag."
1.) you can't start a definition with like XXX without first defining XXX.
2.) I believe the jars can be either a fully qualified URL or relative to the codebase.
"Applets can be deployed by hand-coding the applet, object or embed tags with the required parameters. This section describes these parameters. "
however no place in this section (or any other I can find) are all the parameters listed, only examples of some of them are described. Same with the attributes.
of particular example are "archive", "archive_ex", and "cache_archive" (which are not really parameters, but attributes the applet, embed, or object tags)
"archive" is used in example but never defined.
"cache_archive_ex" is never mentioned
"cache_archive" is defined but wrongly:
it says (in section 11.3.7):
"Like the archive attribute in the applet tag, the list of jar files in the cache_archive attribute do not contain the full URL, but are always downloaded from the codebase specified in the embed or object tag."
1.) you can't start a definition with like XXX without first defining XXX.
2.) I believe the jars can be either a fully qualified URL or relative to the codebase.