Java primitives should be disabled on JS objects when --no-java is used

[Sundararajan Athijegannathan]

[just fixing title so that nashorn-dev archive's list is readable in future]

-Sundar

On 10/17/2016 9:47 PM, Hannes Wallnöfer wrote:
> In fact there's https://bugs.openjdk.java.net/browse/JDK-8157723, which was filed by you and waiting for me. I actually dug it up earlier today. The fix you suggested seems to be working, so it looks like we should do this.
>
> Hannes
>
>
>> Am 17.10.2016 um 17:27 schrieb Attila Szegedi <szegedia at gmail.com>:
>>
>>> On 17 Oct 2016, at 03:21, Hannes Wallnöfer <hannes.wallnoefer at oracle.com> wrote:
>>>
>>> Hi Esben,
>>>
>>>
>>>> Am 17.10.2016 um 09:11 schrieb Esben Andreasen <esben at esbena.dk>:
>>>>
>>>> A.
>>>> Where can I read about such non-ECMA-standard features in Nashorn?
>>>>
>>> https://wiki.openjdk.java.net/display/Nashorn/Nashorn+extensions
>>>
>>> I don’t think the string methods from java.lang.String are contained in that page because, as Attila said, it is a side effect of using java.lang.String as JS string representation and transparently exposing Java methods to scripts.
>> I was thinking that maybe we shoud switch off Java methods on Nashorn primitives with --no-java. A quick test shows we don’t do that now.
>>
>> Attila.