-
Notifications
You must be signed in to change notification settings - Fork 42
Description
Issue description
The below statement is not entirely true.
“Headers and properties set in a child branch aren't available in other child branches.”
Because as per camel documentation, “The multicast EIP will copy the source exchange and multicast each copy. However, the copy is a shallow copy, so in case you have mutable message bodies, then any changes will be visible by the other copied messages.”
So if if a property value has data type of mutable types (like maps, lists etc.) then it can be changed in one branch and same changes can be visible in subsequent branches. But if a new property is created in a branch that will not get visible in the subsequent branches. (Because it’s local to that branch’s exchange.) So the wording matters because set can mean both create or change an existing property before multicast.
Feedback Type (Optional)
incorrect statement
Page Title on SAP Help Portal (prefilled)
Variant: Sharing Data Within the Same Integration Flow