Rhino, Nashorn and V2, V3 & Java 1.8

Rod Widdowson rdw at steadingsoftware.com
Wed Jul 23 07:01:24 EDT 2014


> So, in V2 we didn't prepopulate the object? That was what I thought.

Right.
 
> There's also the possibility of making V2 do what V3 does and have it
> create the object, right? Or does that break scripts?

I tried it and it works as far as I can see/guess it won't (shouldn't) break
scripts.  Under jdk8 they will still need to remove the "new
BasicAttribute();" line and under JDK7 this will no longer be needed.

Plus of course they would need to update to a (yet to be released) IdP.
This is why I prefer the workaround of adding the static connector.  Also,
there is a remote chance that it might break existing scripts and so I'm not
sure I'd want to speculatively fix this.  I'm (very) persuadable tho'.  

Or we could provide a plugin with a different definition type, but that
feels like overkill.

[The ecma plugin code from Sun]
> We'd probably want to at least peruse it.

Right.
 
> In other words, I think this is probably viable, particularly since it
> isn't "active" by default and is designed as a bridge for people.

OK.  I'll take an AI to skim the code we need to compile, and to compile it
and sign it and downloaded jars and put them somewhere.

I'll also write up a wiki page to show people the two ways to make JDK8 work
with IdPV2 (and indeed v3).

R



More information about the dev mailing list