You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Justin Edelson (JIRA)" <ji...@apache.org> on 2011/09/12 17:40:10 UTC

[jira] [Resolved] (SLING-2210) A Script Engine should be able to declare itself as compatible with another script engine

     [ https://issues.apache.org/jira/browse/SLING-2210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Edelson resolved SLING-2210.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: Scripting Core 2.0.20
         Assignee: Justin Edelson

support for compatible.javax.script.name property added in r1169804

> A Script Engine should be able to declare itself as compatible with another script engine
> -----------------------------------------------------------------------------------------
>
>                 Key: SLING-2210
>                 URL: https://issues.apache.org/jira/browse/SLING-2210
>             Project: Sling
>          Issue Type: Improvement
>          Components: Scripting
>            Reporter: Justin Edelson
>            Assignee: Justin Edelson
>             Fix For: Scripting Core 2.0.20
>
>
> A good use case for this is the GSP script engine. Any BindingsValuesProvider which apply to the Groovy script engine should also apply to the GSP script engine. But it shouldn't be (only) the responibility of the BindingsValuesProvider implementor to know all of the possible script engines which can accept the bindings. Rather, the GSP script engine should be able to say "I'm compatible with the Groovy script engine, so give me any bindings you would give to a groovy script". 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira