1. What are Scopes?
Mule scopes work to encapsulate other message processors so that they function as a
single unit.
You might wrap several message processors together to form a transactional unit, so
that they succeed or fail to process a message together, thus ensuring accurate
updating of a database.
3. Async Scope
Creates a block of message processors that execute asynchronously while the rest of
the flow continues to execute in parallel. For instance, you can populate an Async
scope with a sequence of building blocks that perform logging so that logging does
not slow down the rest of the application flow.
4. Cache Scope
Caches data produced by part of a flow. Wrap a cache scope around message
processors in your flow so that it caches the response events produced within the
scope
5. Foreach Scope
Splits any type of message collection apart into individual messages for processing,
and then aggregate them again at the end of the scope. For specific information on
configuring the Foreach Scope
6. Message Enricher
Appends information to a message, often using an expression to determine what part
of the payload to evaluate so as to return an appropriate value to append to that
payload. For example, the expression can evaluate a ZIP code and then append the
associated City and State to the payload. The message processor is executed and the
enricher scope uses the result of that execution to enrich the message coming into
the scope.
7. Poll Scope
Periodically polls an embedded message receiver for new messages. For example, set
a Poll to retrieve email at regular intervals by placing a request-response connector
such as SMTP within the Poll processing block.