[Bug 179] javascript script support through rhino should not be on bootclasspath

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=179


hannes at helma.at changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hannes at helma.at




------- Comment #2 from hannes at helma.at  2008-12-04 13:55 -------
I've thought about this a bit, and I think the only reasonable way to fix it
(short of repackaging rhino with the jvm like Sun does) is to have the
RhinoScriptEngine implementation bundled with the Rhino classes instead of the
jre library. If rhino.jar is loaded though a custom classloader and the
ScriptEngine sits on the jvm side, it has to go through reflection API for each
interaction with Rhino, which is painful to say the least. If, OTOH, the
ScriptEngine(Factory) is loaded by the same classloader as rhino.jar all that
is needed are a few lines of class loading and casting.

Bundling a ScriptEngine implementation with rhino would have a number of other
advantages, like allowing people to use a more cutting edge Rhino version than
the one bundled with the jvm (maybe using alternative name/mimetype/extensions
to avoid clashes with Sun's internal rhino engine). 

The easy way to get there would be to import the openjdk rhinoengine code into
rhino, but I doubt the GPLed code is compatible with Rhino's MPL1.1/GPL2 dual
license. As an alternative, implementing a ScriptEngine withing Rhino looks
like a viable alternative. 


-- 
Configure bugmail: http://icedtea.classpath.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.