-
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 expressions accept variables that can retrieve values from a variety of Mule Runtime engine objects. Before you begin, note that DataWeave version 2 is for Mule 4 apps. For a Mule 3 app, refer to the DataWeave version 1 documentation set in the Mule 3.9 documentation. For other Mule versions, you can use the version selector for the Mule Runtime table of contents.
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 the Logger component. |
|
|
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. |
|