Various custom configuration elements support a common content model used to supply JSR-223 scripts inside other object configurations. Where applicable, the specific configuration elements that share this content model will link to this page. These include the following documentation pages:
This feature is new in V3.4 and is a supplement to the older supported approach of defining scripted beans in native Spring files and referring to the beans by reference.
Configuration elements that contain scripts are of type
ScriptType, which is a type used across a number of namespaces. The specific namespace will depend on where the element shows up in your configuration.
The following sections describe the attributes and child elements of an element of type
An element of type
An element of type
The script may be stored in a local file (with
Each element of type
ScriptType provides relevant script context, that is, one or more input objects (in the general sense) to be utilized by the script. For specific details, consult the individual configuration element pages listed above.
The following example illustrates the use of a CDATA section
<Script> <![CDATA[ // script goes here ]]> </Script>
For additional examples of scripts, consult the individual configuration element pages listed above.
Default Script Engine
ECMAScript for XML (E4X)
ECMAScript 5.1 (June 2011)
ECMAScript 5.1 (plus some features of ECMAScript 2015 aka ECMAScript 6)
Since Java 7 reached end-of-life on April 2015, we assume Java 8 or above, which implements Nashorn.
An introduction to Nashorn from Oracle:
If you’re still using Rhino, the sooner you migrate to Nashorn, the better. That said, many of the sample scripts (which are quite simple) will run under both Rhino and Nashorn.
|Consult the Rhino Migration Guide for helpful advice.|
Since Nashorn is included with Java 8 (and later), the sample scripts aim to conform to ECMAScript 5.1. In particular, the scripts avoid features introduced in ECMAScript 6 (also known as ECMAScript 2015) for compatibility.
|Language features introduced in ECMAScript 2015 (aka ECMAScript 6) are intentionally not used in the sample scripts for compatibility reasons. This includes |