oscerd opened a new pull request, #29615: URL: https://github.com/apache/camel/pull/29615
Backport of #29310 ([CAMEL-26278](https://issues.apache.org/jira/browse/CAMEL-26278)) to camel-4.18.x. The `hazelcast-seda` consumer restored any `DefaultExchangeHolder` it took from the queue, with its headers and exchange properties, whatever its `transferExchange` option said. It now restores them only when the consumer has `transferExchange=true` itself. Without the option it takes only the body of such an exchange and logs a warning the first time. ## Differences from the commit on main - The consumer change is applied by hand onto the consumer of camel-4.18.x, which does not have the later changes of main around it: the new `takeTransferredExchange` method, the flag of its warning and the call site, as on main. - The `@BodyTypes` description of the endpoint is not taken, as the body types exist on main only. - The upgrade-guide changes are not taken: #29310 added the note to the 4.22.3 and 4.18.6 sections of the guides on main. - The description of the `transferExchange` option, the "Transferring the whole exchange" section of the component page and the three new tests are taken. The component JSON, its catalog copy and the endpoint DSL are regenerated on camel-4.18.x. camel-4.18.x has no catalog copies of the component pages, so only the page of the component is updated. ## Tests `HazelcastSedaTransferExchangeTest` has the three new tests of #29310. The 19 tests of the hazelcast-seda test classes pass on camel-4.18.x, with the module and the endpoint DSL built against the branch. The conflicts were resolved by hand, so this asks for a review. _Claude Code on behalf of Andrea Cosentino (oscerd)_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
