[
https://issues.apache.org/jira/browse/SLING-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12545668
]
hannonpi edited comment on SLING-110 at 11/27/07 4:10 PM:
----------------------------------------------------------------
I am still unsure if I like the fact that SlingScript has a getScriptEngine()
method, it seems that the script resolver should handle this. However, I am
wary of introducing such a change as it feels like a very fundamental change.
Also, depending on the progress of BSF I can remove some of our script engines
as BSF engines come online.
Note: I did update getScriptEngine() to return javax.script.ScriptEngine.
was (Author: hannonpi):
I am still unsure if I like the fact that SlingScript has a
getScriptEngine() method, it seems that the script resolver should handle this.
However, I am wary of introducing such a change as it feels like a very
fundamental change. Also, depending on the progress of BSF I can remove some of
our script engines as BSF engines come online.
> 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
>
>
> 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.
