- The Bean Scripting Framework does not provide an API to precompile, cache and reuse scripts. Because of this, each execution of the ScriptingAction will go through the compile step again. Please keep this in mind while evaluating your performance requirements.
- When including BeanShell scripts in your application, Red Hat advises you should use a .beanshell extension instead of .bsh, otherwise the JBoss BSHDeployer might pick it up.
Table 13.14. ScriptingAction Properties
Path (on classpath) to script.
Allow scripts within the message.
Optional script language (overrides extension deduction).
Table 13.15. ScriptingAction Processor Script Binding Variables
Utility for message payload (MessagePayloadProxy)
The action configuration (ConfigTree)
The ScriptingAction's static Log4J logger (Logger)
<action name="process" class="org.jboss.soa.esb.scripting.ScriptingAction"> <property name="script" value="/scripts/myscript.beanshell"/> </action>