Re: jdk.nashorn.api.scripting.ScriptUtils.wrap

2015-11-09 Thread Kockert, Timo
Since attachments are automatically removed, I created a repository on GitHub: https://github.com/hzpz/nashorn-examples >Hi Sundar, > >thanks for the quick reply! > > > >I attached a small Maven project with two tests. Both tests work fine with >JDK8u60. Both will fail with JDK8u31, the metho

Re: jdk.nashorn.api.scripting.ScriptUtils.wrap

2015-11-09 Thread Kockert, Timo
Hi Sundar, thanks for the quick reply! I attached a small Maven project with two tests. Both tests work fine with JDK8u60. Both will fail with JDK8u31, the method selection test will also fail with newer JDKs up to JDK8u51. The behavior demonstrated by the mapping test was the reason we used

jdk.nashorn.api.scripting.ScriptUtils.wrap

2015-11-09 Thread Kockert, Timo
Hello everyone, on October 7th, Richard Evans posted to this mailing list (with the same subject as me): "Sometime after jdk1.8u32 this method changed to take an internal jdk.nashorn.internal.runtime.ScriptObject argument. This means that code compiled with 1.8u20 will not work with later rel

Re: jdk.nashorn.api.scripting.ScriptUtils.wrap

2015-11-09 Thread Sundararajan Athijegannathan
The ScriptUtils methods are supposed to be called only from *scripts* - which the javadoc comments makes it very clear. Why do you call it from Java? When calling from script, the particular static type of method parameters should not make any difference. Besides, when crossing Javascript to j

jdk.nashorn.api.scripting.ScriptUtils.wrap

2015-10-07 Thread Richard Evans
Sometime after jdk1.8u32 this method changed to take an internal jdk.nashorn.internal.runtime.ScriptObject argument. This means that code compiled with 1.8u20 will not work with later releases, and vice versa. Was this change intentional? Is this API now fixed for all future jdk1.8 and 1.9