Migrating the Scripting Component
The <scripting> component in Mule 3 is replaced with a new <scripting> module. This new module is pretty similar in functionality, with just some syntax changes:
Mule 3 Example: Scripting
<flow name="greedy">
<choice>
<when expression="#[flowVars['currency'] == 'USD']">
<scripting:component>
<scripting:script file="greedy.groovy">
<property key="currency" value="USD"/>
</scripting:script>
</scripting:component>
</when>
<when expression="#[flowVars['currency'] == 'GBP']">
<scripting:component>
<scripting:script file="greedy.py">
<property key="currency" value="GBP"/>
</scripting:script>
</scripting:component>
</when>
</choice>
</flow>+
Mule 4 Example: Scripting
<flow name="greedy">
<scripting:execute engine="groovy">
<scripting:code>${file::greedy.groovy}</scripting:code>
<scripting:parameters>
#[{currency: vars.currency}]
</scripting:parameters>
</scripting:execute>
</flow>As you can see, the main difference here is that now you can use DataWeave to generate the input parameters.
Accessing Variables from the Script
The previous example uses a variable to show how to pass parameters into the script, it’s best to keep the script decoupled from the rest of the flow, so that changes to the Mule applications don’t require changes to the script.
However, you can still access the variables from the script using the vars keyword. For example:
Mule 4 Example: Accessing variables directly
<flow name="greedy">
<scripting:execute engine="groovy">
<scripting:code>return "currency is " + vars.currency</scripting:code>
</scripting:execute>
</flow>To use the Scripting Module, simply add it to your application using the Studio palette or add the following dependency in your pom.xml file:
<dependency>
<groupId>org.mule.modules</groupId>
<artifactId>mule-scripting-module</artifactId>
<version>1.1.0</version> <!-- or newer -->
<classifier>mule-plugin</classifier>
</dependency>