[
https://issues.apache.org/jira/browse/SLING-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-2229.
-----------------------------------
> Create Sling implementation fo the JSR 223 ScriptEngineManager
> --------------------------------------------------------------
>
> Key: SLING-2229
> URL: https://issues.apache.org/jira/browse/SLING-2229
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Affects Versions: Scripting API 2.1.2
> Reporter: Felix Meschberger
> Assignee: Justin Edelson
> Fix For: Scripting API 2.1.4
>
> Attachments: SLING-2229.patch
>
>
> Currently we are using the Livetribe implementation of the JSR 223 API to
> have a consistent implementation on Java 5 platforms (not including JSR-223)
> and Java 6 platforms (including JSR-223). We do this by exporting the JSR-223
> API from the scripting api bundle and not through the system bundle.
> The Livetribe implementation has some issues, though:
> * According to the spec it scans the class path for implementations
> * It contains a slight API deviation from the Java 6 implementation:
> get/setGlobalContext instead of get/setBindings
> To fix this, we implement our own ScriptEngineManager based on the Livetribe
> implementation:
> - without the class loader scanning
> - adding the get/setBIndings methods
> - marking the get/setGlobalContext methods deprecated
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
