Standard transformer
Transforms messages by executing a SpEL expression or Groovy script on each incoming message.
While all other transformers have very specific uses, this component is extremely flexible. The downside is that this transformer can be harder to use because it involves scripting.
Allows you to define custom script variable bindings. This attribute isn't mutually exclusive with variables setting (see the basic tab) and all variables will be merged to one map.
The variables
payload
and headers
are always automatically available, even if you do not manually specify any variables. Since these two variables already give you access to all information in the message from your Groovy script, the main use-case for custom variables is probably to pass property values to the script.
All custom non-ref variables will be passed as a value of type String
to the Groovy script. If required, you can easily convert the data type using the Groovy as
keyword. For example: variableName as Integer
.
_id
Channel where output messages should be sent after (successfully) processing the input message.
You can select the nullChannel
here to silently drop the output messages.
Required
_id
Channel where output messages should be sent after (successfully) processing the input message.
You can select the nullChannel
here to silently drop the output messages.
Required
_id
Channel to consume the input messages from.
Required
_id
Channel to consume the input messages from.
Required