[jira] Commented: (SLING-1510) Expose the ScriptEngineManager managed by Sling

["Justin Edelson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863947#action_12863947 ] 

Justin Edelson commented on SLING-1510:
---------------------------------------

Felix said:
> 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. 

(and then I neglected to respond for a week)

My response:
I did this because this class already used was a lazy creation factory. I've reimplemented it so that the ScriptEngineManager isn't lazily created and registered directly as a service.


> 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
>            Assignee: Justin Edelson
>            Priority: Minor
>             Fix For: Scripting Core 2.0.12, Scripting API 2.1.2
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.