davsclaus opened a new pull request, #28635: URL: https://github.com/apache/camel/pull/28635
https://issues.apache.org/jira/browse/CAMEL-26385 The Enrich EIP page explained only the aggregation strategy and never mentioned `variableReceive`, the simplest way to enrich without replacing the message. - A first section, "Keeping the message: the reply in a variable", with an example in Java, XML and YAML: an order sent to a stock service over JMS, the answer in `${variable.stock}`, and the order sent on. It also covers the reply headers (`header:stock.<name>` variables), `variableSend`, and that `to` (InOut) and `pollEnrich` work the same. It links to the variables guide. - "Aggregation Strategy is optional" now says that the reply replaces the body, and points to `variableReceive`. - The example comes first on the page, so the AI tools' catalog samples show it. The catalog copy of the page is updated. Found with the local-model benchmark: in a step that must "keep the order as the body" after a request-reply, no run used `variableReceive`. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m -- 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]
