In Mule's For Each, what defines the items that will be iterated?

In Mule's For Each, what defines the items that will be iterated?

• A. The payload type must be a list
• B. The iterable collection is automatically determined if the payload is a Java collection
• C. Each item is converted to a string
• D. For Each always iterates over the entire message envelope

Answer: (B)

The items that For Each iterates over come from the payload. If the payload is a Java collection, Mule automatically recognizes that collection and uses its elements as the items to process, one per iteration. In other words, each element of that Java collection becomes the new payload for the block inside the For Each during that iteration. This means you don’t have to convert the payload to a list explicitly for common Java collections—the framework handles it for you. If you need to iterate over something else, you can explicitly specify a different collection expression, but the automatic behavior kicks in precisely when the payload is a Java collection. Note that items aren’t turned into strings or forced to a particular type; they’re passed through as their actual element types. And it isn’t the entire message envelope that’s iterated over—only the collection’s elements, with the payload updated to each element in turn.

The items that For Each iterates over come from the payload. If the payload is a Java collection, Mule automatically recognizes that collection and uses its elements as the items to process, one per iteration. In other words, each element of that Java collection becomes the new payload for the block inside the For Each during that iteration.

This means you don’t have to convert the payload to a list explicitly for common Java collections—the framework handles it for you. If you need to iterate over something else, you can explicitly specify a different collection expression, but the automatic behavior kicks in precisely when the payload is a Java collection.

Note that items aren’t turned into strings or forced to a particular type; they’re passed through as their actual element types. And it isn’t the entire message envelope that’s iterated over—only the collection’s elements, with the payload updated to each element in turn.