Felix Meschberger wrote:
The ScriptEngine.eval method already is defined to return an Object. We
just would have to forward this value.
Yepp.
b) We need a convention to pass the method name and the method
parameters to the script engine
c) Check for the new info mentioned in b) and if available don't execute
the whole script, but just the single method.
The problem with calling a method (or function) is that there will
probably not be a script file to be "compiled" and a method called on it
but rather some already existing functions or objects in the
ScriptEngine scope on which we call a function or method....
Probably we need to enter the arena of direct ScriptEngine use here ??
I assume you mean javax.script.ScriptEngine? And javax.script.Invocable?
I am not in favor of defining special hacks into e.g. the SlingBindings
object to support this.
Yes, I agree - I'm wondering if it makes more sense to shrink our
scripting layer (we have own bindings objects etc) and start direcly
using the javax.script stuff?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
