Hi, I understand the idea of directly accessing script engines (makes perfect sense IMHO).
So why not register the ScriptEngineManager as a service directly ? So you can grab the ScriptEngineManager and just go with it. Regards Felix On 28.04.2010 22:02, Justin Edelson (JIRA) wrote: > Expose the ScriptEngineManager managed by Sling > ----------------------------------------------- > > Key: SLING-1510 > URL: https://issues.apache.org/jira/browse/SLING-1510 > Project: Sling > Issue Type: Improvement > Components: Scripting > Reporter: Justin Edelson > Priority: Trivial > > > I'd like to add a new service interface called ScriptEngineManagerFactory to > scripting.api and have SlingScriptAdapterFactory implement it. This will > allow other infrastucture bundles to use javax.script engines. >
