[
https://issues.apache.org/jira/browse/SLING-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548184
]
Felix Meschberger commented on SLING-110:
-----------------------------------------
> * Drop dependency on BSF in the API
> ** Does this mean that you want to remove the ScriptEngineManager
> instance from the ScriptResolver classes?
I do not want to drop the BSF dependency completely - in fact this whole issue
is about using BSF :-)
I just do not want the Sling API (in the api project) to have a BSF or Java
Scripting dependency. I think it is not required in the Sling API to have such
a dependency as the ScriptResolver returns a Script and the Script has an eval
method.
The implementation of these interfaces will certainly require Java Scripting
(BSF 3 that is) for the implementation. But from the point of view of the Sling
API, this is an implementation detail.
> * Rename ScriptBindings to SlingBindings and extend HashMap<String, Object>
> instead of implementing Java Scripting Bindings.
> ** I do not understand why we do not want have the binding class implement the
> scripting bindings interface?
If SlingBindings would implement the BIndings interface, this would be the only
reference to Java Scripting in the Sling API. As I intend to have Java
Scripting dependency to be an implementation detail, I think, the
SlingBindings, should not use Java Scripting API.
> Update Script System to be JSR-223 Compatible
> ----------------------------------------------
>
> Key: SLING-110
> URL: https://issues.apache.org/jira/browse/SLING-110
> Project: Sling
> Issue Type: Improvement
> Components: microsling, Scripting
> Affects Versions: 2.0.0
> Reporter: Padraic Hannon
> Attachments: bsf.patch, SLING-110_api.patch
>
>
> Currently sling and microsling use a custom scripting framework. This
> framework should be updated to be jsr-223 compatible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
