A mapping of key/value pairs, all of whose keys are
The optional interface implemented by ScriptEngines whose methods compile scripts to a form that can be executed repeatedly without recompilation.
The optional interface implemented by ScriptEngines whose methods allow the invocation of procedures in scripts that have previously been executed.
The interface whose implementing classes are used to connect Script Engines with objects, such as scoped Bindings, in hosting applications.
Provides a standard implementation for several of the variants of the
Extended by classes that store results of compilations.
A simple implementation of Bindings backed by a
Simple implementation of ScriptContext.
The scripting API consists of interfaces and classes that define Java TM Scripting Engines and provides a framework for their use in Java applications. This API is intended for use by application programmers who wish to execute programs written in scripting languages in their Java applications. The scripting language programs are usually provided by the end-users of the applications.
The main areas of functionality of
functionality allows the intermediate code generated by the
front-end of a script engine to be stored and executed repeatedly.
This benefits applications that execute the same script multiple
times. These applications can gain efficiency since the engines'
front-ends only need to execute once per script rather than once per
script execution. Note that this functionality is optional and
script engines may choose not to implement it. Callers need to check
for availability of the
interface using an instanceof check.
functionality allows the reuse of intermediate code generated by a
script engine's front-end. Whereas Compilation allows entire scripts
represented by intermediate code to be re-executed, Invocation
functionality allows individual procedures/methods in the scripts to
be re-executed. As in the case with compilation, not all script
engines are required to provide this facility. Caller has to check
Script engine discovery and Metadata: Applications
written to the Scripting API might have specific requirements on
script engines. Some may require a specific scripting language
and/or version while others may require a specific implementation
engine and/or version. Script engines are packaged in a specified
way so that engines can be discovered at runtime and queried for
attributes. The Engine discovery mechanism is based on the Service
discovery mechanism described in the Jar File Specification.
Script engine implementing classes are packaged in jar files that
include a text resource named
resource must include a line for each
that is packaged in the jar file.
getEngineFactories method to get all
discovered using this mechanism.
methods to query attributes about script engine.