ScriptContext is the current mechanism used in the platform and first party modules for two purposes:
- To provide "implicit" values like the default DB connection, project name, etc to executing scripts.
- To decorate executing scripts with extra contextual information, such as a description to show on the gateway web page, the location for the tag reference tracker, etc.
Currently, ScriptContext uses a 'flat' thread local map for storage of arbitrary values. My question is, do any of your modules take advantage of this ability to set arbitrary values on ScriptContext? This would only apply in any event if you were executing user authored Jython in your own execution "manager", which doesn't apply to the vast majority of modules.