-
Bug
-
Resolution: Fixed
-
P3
-
6, 7
-
b126
-
generic, x86
-
generic, windows_vista
-
Verified
As a reference jsr-223 script engine, javascript engine based on Mozilla Rhino was added to JDK 6. We used the then current Rhino code (version 1.6R2) implementing JavaScript 1.6 in JDK 6. In the mean time, Rhino code has evolved to version 1.7R3 and now supports JavaScript version 1.8.
We need to update Rhino code in JDK 7 with the code from the latest 1.7R3 version. This is needed because
(a) Rhino now supports JavaScript 1.8
(b) Rhino supports parts of ECMAScript 5 specification
Also, in JDK 6 we had excluded the optional E4X (XML support for javascript - ECMAScript standard ECMA-357). This is because of dependency on Apache XML beans (footprint and security concerns). The 1.7R3 version of Rhino supports E4X using DOM 3 without depending on anything else. So, we may want to support E4X in JDK 7.
We need to update Rhino code in JDK 7 with the code from the latest 1.7R3 version. This is needed because
(a) Rhino now supports JavaScript 1.8
(b) Rhino supports parts of ECMAScript 5 specification
Also, in JDK 6 we had excluded the optional E4X (XML support for javascript - ECMAScript standard ECMA-357). This is because of dependency on Apache XML beans (footprint and security concerns). The 1.7R3 version of Rhino supports E4X using DOM 3 without depending on anything else. So, we may want to support E4X in JDK 7.
- duplicates
-
JDK-6856823 Rhino RegExp parser bugs(javax.script)
- Closed
-
JDK-7009122 [javax.script] Upgrade integrated Rhino JavaScript engine to 1.7 R2
- Closed
- relates to
-
JDK-7051182 Regression: : jconsole scripting demo fails with UndeclaredThrowableException
- Closed
-
JDK-6656850 Update jdk to use 1.6R7 Rhino source.
- Closed
-
JDK-6427783 E4X support is missing from Sun's Mozilla JavaScript implementation
- Closed