JDK-7073033 : Do not try to launch FX apps with old JRE
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 7-client
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2011-07-30
  • Updated: 2013-09-12
  • Resolved: 2011-08-24
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
JDK 7 JDK 8
7u2 b03Fixed 8Resolved
Description
Scenario:
   - uninstall all JREs
   - install 5u30
   - install 6u25
   - disable 6u25 in the control panel
   - install FX 2.0

Enable tracing for the browser VM. Open any FX sample.

Observe that we actually try to use 5u30 launch FX. FX itself is not compatible with anything older than 6u10
       and with 5 it will fail miserably as FX classes use newer class format and JVM from JRE5 does not support it

Expected behavior:
  1) do not try to launch with 5.0
  2) make sure applet error callback is called. Then we can hide splash and showm meaningful error.

Comments
EVALUATION Client VM aborted with the check, but server VM should not even try to launch client VM with incompatible JRE.
2011-08-23