This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 3291dd91c09f CAMEL-24062: Sync backport upgrade guide entry for 
Multicast UseOriginal fix
3291dd91c09f is described below

commit 3291dd91c09ff93506028053bad956bd9f210881
Author: Claus Ibsen <[email protected]>
AuthorDate: Wed Jul 15 09:17:11 2026 +0200

    CAMEL-24062: Sync backport upgrade guide entry for Multicast UseOriginal fix
    
    Add the 4.18.4 upgrade guide entry on main to keep the canonical
    upgrade guide history in sync with the camel-4.18.x backport.
    
    Co-Authored-By: Claude Opus 4.6 <[email protected]>
    Signed-off-by: Claus Ibsen <[email protected]>
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc          | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index df57833f08ea..c350992a215c 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -13,6 +13,15 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation] 
page for details.
 
 == Upgrading from 4.18.3 to 4.18.4
 
+=== camel-core - Multicast EIP honors UseOriginalAggregationStrategy
+
+The `UseOriginalAggregationStrategy` binding has been moved from `Splitter` 
and `RecipientListProcessor`
+into `MulticastProcessor` (their shared base class), so all three EIPs 
(Multicast, Splitter,
+RecipientList) now consistently bind the original exchange on the strategy. 
Previously, Multicast
+never called `newInstance(exchange)`, which made the strategy silently 
ineffective — especially in
+error scenarios where the aggregated result could overwrite the original 
exchange body instead of
+preserving it.
+
 === camel-azure-servicebus - Camel-managed message lock renewal
 
 When consuming from Azure Service Bus in `PEEK_LOCK` mode with 
`maxAutoLockRenewDuration > 0`, Camel now

Reply via email to