Comments on: Compilation Struggles with Java 6 ScriptEngine, JavaScript, and Maven http://www.innovationontherun.com/compilation-struggles-with-java-6-scriptengine-javascript-and-maven/ Ruminations about innovation and software by Rob Di Marco Tue, 06 Apr 2010 15:52:14 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Frank http://www.innovationontherun.com/compilation-struggles-with-java-6-scriptengine-javascript-and-maven/comment-page-1/#comment-398 Frank Tue, 02 Mar 2010 22:15:01 +0000 http://www.innovationontherun.com/compilation-struggles-with-java-6-scriptengine-javascript-and-maven/#comment-398 Thanks, I had this problem while using Ant. The solution is similar, simply specify the "bootclasspath" attribute of the Javac task. Thanks, I had this problem while using Ant. The solution is similar, simply specify the “bootclasspath” attribute of the Javac task.

]]> By: hari http://www.innovationontherun.com/compilation-struggles-with-java-6-scriptengine-javascript-and-maven/comment-page-1/#comment-77 hari Tue, 16 Oct 2007 09:14:56 +0000 http://www.innovationontherun.com/compilation-struggles-with-java-6-scriptengine-javascript-and-maven/#comment-77 it helped me a lot in completing my task it helped me a lot in completing my task

]]> By: Tom McQueeney http://www.innovationontherun.com/compilation-struggles-with-java-6-scriptengine-javascript-and-maven/comment-page-1/#comment-22 Tom McQueeney Wed, 08 Aug 2007 17:29:41 +0000 http://www.innovationontherun.com/compilation-struggles-with-java-6-scriptengine-javascript-and-maven/#comment-22 Rob, I know what you're experiencing as far as being able to consistently share Java objects with a script interpreter. Two possible solutions. First, embed Rhino directly using the Rhino ScriptEngine implementation. That way, you're dependent at build time on the Mozilla js.jar rather than the Sun rt.jar. I posted a more-detailed explanation on my reply to your comment on my blog, http://mcqueeney.com/roller/page/tom?entry=returning_from_ruby_or_javascript The second technique I've used to avoid adding rt.jar to a build classpath is to use Class.forName trickery. Code the "sun.xxx.yyy.Zzz" class as a string in Class.forName and cast the new instance to a generic super type that isn't in rt.jar. It sounds like this technique might not work for you, short of casting the instance to an Object, if the NativeArray class can't be cast somehow to a java.lang.reflect.Array type or equivalent. Good luck. -Tom Rob,

I know what you’re experiencing as far as being able to consistently share Java objects with a script interpreter.

Two possible solutions. First, embed Rhino directly using the Rhino ScriptEngine implementation. That way, you’re dependent at build time on the Mozilla js.jar rather than the Sun rt.jar. I posted a more-detailed explanation on my reply to your comment on my blog, http://mcqueeney.com/roller/page/tom?entry=returning_from_ruby_or_javascript

The second technique I’ve used to avoid adding rt.jar to a build classpath is to use Class.forName trickery. Code the “sun.xxx.yyy.Zzz” class as a string in Class.forName and cast the new instance to a generic super type that isn’t in rt.jar. It sounds like this technique might not work for you, short of casting the instance to an Object, if the NativeArray class can’t be cast somehow to a java.lang.reflect.Array type or equivalent.

Good luck.

-Tom

]]> By: DZone - New links http://www.innovationontherun.com/compilation-struggles-with-java-6-scriptengine-javascript-and-maven/comment-page-1/#comment-20 DZone - New links Wed, 08 Aug 2007 05:35:36 +0000 http://www.innovationontherun.com/compilation-struggles-with-java-6-scriptengine-javascript-and-maven/#comment-20 <!--%kramer-ref-pre%-->[...] commentsSaveShare Tags: tools, windows 1 [...]<!--%kramer-ref-post%--> [...] commentsSaveShare Tags: tools, windows 1 [...]

]]>