United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-6627840 Deployment Toolkit updates for new Java Plug-In, add isPlugin2()
JDK-6627840 : Deployment Toolkit updates for new Java Plug-In, add isPlugin2()

Details
Type:
Enhancement
Submit Date:
2007-11-09
Status:
Closed
Updated Date:
2010-09-08
Project Name:
JDK
Resolved Date:
2008-06-13
Component:
deploy
OS:
generic
Sub-Component:
plugin
CPU:
generic
Priority:
P3
Resolution:
Fixed
Affected Versions:
6u10
Fixed Versions:
6u10 (b12)

Related Reports
Backport:

Sub Tasks

Description
The DT needs to be updated to add support for the new Java Plug-In. Known issues at this time:

1. Support for per-applet JVM command-line arguments via "java_arguments" parameter.
2. May need updates for JRE version selection for individual applets. Don't know exactly how this is handled, or whether the backward compatibility mechanisms in 6606284 combined with whatever DT currently does will suffice. Direct support for the "java_version" parameter would be preferable.
3. The detection mechanism should be augmented if possible to indicate that the new Java Plug-In is available.
4. In the context of the new Java Plug-In the concept of the "browser Java version" is obsolete and needs to be reconsidered.

There may be other issues.

                                    

Comments
EVALUATION

1. Support for per-applet JVM command-line arguments via "java_arguments" parameter.
 - all applet parameters are already able to be specified in DT javascript calls.
2. May need updates for JRE version selection for individual applets. Don't know exactly how this is handled, or whether the backward compatibility mechanisms in 6606284 combined with whatever DT currently does will suffice. Direct support for the "java_version" parameter would be preferable.
 - no new functionality needed here in DT, DT can install latest or any older JRE, or the latest in any family, and can do similar detection.
3. The detection mechanism should be augmented if possible to indicate that the new Java Plug-In is available.
 - This sounds like a real new requirement.  Even if new plugin is default, old plugin will be selectable, or old browsers will trigger old plugin.  Need a javascript method to detect which will be used.
4. In the context of the new Java Plug-In the concept of the "browser Java version" is obsolete and needs to be reconsidered.
 - This is not really exposed at present in DT.
                                     
2007-12-12
EVALUATION

I think we have 2 new requirements here.
1.) need to have javascript to determine if java is enabled in the browser.
2.) need to have javascipt to determine if new or old plugin support is enabled.
these might be combined into one method that returns an enumerated value such as
NO_JAVA, MSVM_JAVA, SUN_JAVA_1, SUN_JAVA_2
                                     
2008-01-07
EVALUATION

adding javascript and plugin method to identify if the new plugin is enabled in the browser:
deployJava.isPlugin2().
                                     
2008-01-26



Hardware and Software, Engineered to Work Together