-
Bug
-
Resolution: Fixed
-
P3
-
7-client
-
b03
-
generic
-
generic
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2214733 | 8 | Henry Jen | P3 | Resolved | Fixed | b12 |
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.
- 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.
- backported by
-
JDK-2214733 Do not try to launch FX apps with old JRE
-
- Resolved
-