stephen mallette created TINKERPOP-1095:
-------------------------------------------

             Summary: Determine if a custom ScriptContext is required
                 Key: TINKERPOP-1095
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1095
             Project: TinkerPop
          Issue Type: Improvement
          Components: groovy
    Affects Versions: 3.1.0-incubating
            Reporter: stephen mallette
            Assignee: stephen mallette
            Priority: Critical
             Fix For: 3.2.0-incubating


The current {{ScriptContext}} in use with the {{ScriptEngine}} is the 
{{SimpleScriptContext}}.  It doesnt' allow for additional scopes which might be 
useful when dealing with the {{ScriptEnginePluginAcceptor}} which allows 
plugins to inject "global" bindings into the a {{ScriptEngine}} instance (e.g. 
the "hdfs" object with the hadoop plugin).

We currently inject this into the {{GLOBAL_SCOPE}} of the {{ScriptEngine}} 
which at the moment doesn't seem to conflict with anything, but I wonder if 
more separation is required.

Another alternative would be to manage these types of "globals" with new 
methods on the {{DependencyManager}} interface.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to