<error-handler name="securityHandler"> <on-error-continue type="SECURITY"> <!-- general error handling for all SECURITY errors --> <choice> <when expression="#[Mule::causedBy(error, 'HTTP:UNAUTHORIZED')]"> <!-- specific error handling only for HTTP:UNAUTHORIZED errors --> </when> <when expression="#[Mule::causedBy('HTTP:FORBIDDEN')]"> <!-- specific error handling only for HTTP:FORBIDDEN errors --> </when> </choice> </on-error-continue> </error-handler>
DataWeave 2.2 is compatible and bundled with Mule 4.2. Standard Support for Mule 4.2 ended on May 2, 2021, and this version of Mule will reach its End of Life on May 2, 2023, 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.
This function matches an error by its type, like an error handler does.
causedBy is useful when you need to match by a super type, but the
specific sub-type logic is also needed. It can also useful when handling a
COMPOSITE_ROUTING error that contains child errors of different types.
A string that identifies the error, such as HTTP:UNAUTHORIZED.
This XML example calls
causedBy from a
when expression in a Mule error
handling component to handle a SECURITY error differently depending on whether
it was caused by an HTTP:UNAUTHORIZED or HTTP:FORBIDDEN error. Notice that the
first expression passes in the
Error type) explicitly, while the
second one passes it implicitly, without specifying the value of the parameter.
error is the variable that DataWeave uses for errors associated
with a Mule message object (see
DataWeave Variables for Mule Runtime).