-
Fields:
-
encoding
: Encoding used by the Mule message processor. -
name
: Name of your project and Mule app. -
standalone
: Returnstrue
orfalse
. -
workDir
: Working directory for the Mule app. For Studio, this is an Eclipse plugin directory. -
registry
: Map of Mule registry entries.
-
-
Example:
#[app.encoding]
might returnUTF-8
.
Predefined Variables
DataWeave 2.1 is compatible with Mule 4.1. Standard Support for Mule 4.1 ended on November 2, 2020, and this version of Mule will reach its End of Life on November 2, 2022, when Extended Support ends. Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted. MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements. |
DataWeave expressions accept variables that can retrieve values from a variety of Mule Runtime objects. Commonly used variables include attributes
, payload
, and vars
, the main parts of the Mule event.
Variables | Description | Fields and Examples |
---|---|---|
|
The Mule artifact in context. |
|
|
Attributes (metadata) of a Mule Message object ( |
|
|
Provides access to the authentication information. |
|
|
The |
|
|
Data type of the message payload. |
|
|
Error associated with a Mule message object. |
|
|
Deprecated: The name of the current flow. Because flow names are static, this field is deprecated and only available through specific components, such as the Logger. |
|
|
Package ( |
|
|
The Mule instance on which the application is currently running. |
|
|
The body of the current Mule message object ( |
|
|
The operating system on which the Mule instance is running. Exposes information about both the physical server and the JVM on which Mule runs. |
|
|
All variables currently set on the current Mule event being processed. |
|