Re: Is there a way to reference the engine from a linker?
Hi, Dynalink and its pluggable linkers are independent of Nashorn. If you want to access the current engine, you've to arrange to pass it. Thanks, -Sundar On 16/03/18, 12:32 AM, Paulo Lopes wrote: Hi, I'm writing a guarded linker to allow custom casting from JSObject to Vertx custom types. So far so good, the basic tests seem to work but I think I'm writing too much boiler plate code as I need in many times to have an intermediate conversion from JSObject to Map or List. So I know that in the engine I could call Java.asJSONCompatible() but I don't see how I could get a reference to the engine in the linker. Could anyone see a way or let me know if there is a open API to do this? Thanks! Paulo
Is there a way to reference the engine from a linker?
Hi, I'm writing a guarded linker to allow custom casting from JSObject to Vertx custom types. So far so good, the basic tests seem to work but I think I'm writing too much boiler plate code as I need in many times to have an intermediate conversion from JSObject to Map or List. So I know that in the engine I could call Java.asJSONCompatible() but I don't see how I could get a reference to the engine in the linker. Could anyone see a way or let me know if there is a open API to do this? Thanks! Paulo
Re: RFR: 8199443: Nashorn multithread bottleneck with "use strict"
+1 > On Mar 15, 2018, at 10:30 AM, Hannes Wallnöfer> wrote: > > Please review: > > Bug: https://bugs.openjdk.java.net/browse/JDK-8199443 > Webrev: http://cr.openjdk.java.net/~hannesw/8199443/webrev/ > > If we make sure the property maps for strict functions and arguments are set > up correctly (they weren’t before) we can skip setting the property in > ScriptObject#initUserAccessors. > > Thanks, > Hannes > >
RFR: 8199443: Nashorn multithread bottleneck with "use strict"
Please review: Bug: https://bugs.openjdk.java.net/browse/JDK-8199443 Webrev: http://cr.openjdk.java.net/~hannesw/8199443/webrev/ If we make sure the property maps for strict functions and arguments are set up correctly (they weren’t before) we can skip setting the property in ScriptObject#initUserAccessors. Thanks, Hannes