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

SUGGESTED FIX
Don't try to launch JRE cannot run JavaFX, not even try to install JavaFX if suitable JRE doesn't exist.
When no qualified JRE can be started, set the applet status to ERROR. This will call onError handler in JavaScript if 'java_status_events' parameter is set to true.
http://sa.us.oracle.com/projects/deployment_data/7-client/7073033.0