13.5.5. ScriptingAction

Class org.jboss.soa.esb.actions.scripting.ScriptingAction
Executes a script using the Bean Scripting Framework, receiving the message, payloadProxy, action configuration and logger as variable input.
  1. 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.
  2. 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
Property Description Required
script
Path (on classpath) to script.
supportMessageBasedScripting
Allow scripts within the message.
language
Optional script language (overrides extension deduction).
No
Table 13.15. ScriptingAction Processor Script Binding Variables
Variable Description
message
The Message
payloadProxy
Utility for message payload (MessagePayloadProxy)
config
The action configuration (ConfigTree)
logger
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>
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.