[
https://issues.apache.org/jira/browse/CAMEL-26385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-26385:
--------------------------------
Description:
The Enrich EIP page explains only the aggregation strategy. It never mentions
variableReceive, the simplest way to enrich without replacing the message: the
reply goes into a variable, and the body and headers stay as they are.
The local-model benchmark shows the gap: in a step that asks a stock service
with request-reply and must "keep the order as the body", only 1 run in 15 used
variableReceive. In the others the reply replaced the order.
The page gets 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 a variable, the order sent on). It says how the reply
headers are stored, what variableSend does, that to (InOut) and pollEnrich work
the same, and links to the variables guide. The "Aggregation Strategy is
optional" section 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.
_Filed by Claude Code on behalf of davsclaus_
was:
The Enrich EIP page explains only the aggregation strategy. It never mentions
variableReceive, the simplest way to enrich without replacing the message: the
reply goes into a variable, and the body and headers stay as they are.
The local-model benchmark shows the gap: in a step that asks a stock service
with request-reply and must "keep the order as the body", no run in 15 used
variableReceive. The reply replaced the order every time.
The page gets 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 a variable, the order sent on). It says how the reply
headers are stored, what variableSend does, that to (InOut) and pollEnrich work
the same, and links to the variables guide. The "Aggregation Strategy is
optional" section 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.
_Filed by Claude Code on behalf of davsclaus_
> camel-core - Enrich EIP docs: keep the message with variableReceive
> -------------------------------------------------------------------
>
> Key: CAMEL-26385
> URL: https://issues.apache.org/jira/browse/CAMEL-26385
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, documentation
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> The Enrich EIP page explains only the aggregation strategy. It never mentions
> variableReceive, the simplest way to enrich without replacing the message:
> the reply goes into a variable, and the body and headers stay as they are.
> The local-model benchmark shows the gap: in a step that asks a stock service
> with request-reply and must "keep the order as the body", only 1 run in 15
> used variableReceive. In the others the reply replaced the order.
> The page gets 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 a variable, the order sent on). It says how the reply
> headers are stored, what variableSend does, that to (InOut) and pollEnrich
> work the same, and links to the variables guide. The "Aggregation Strategy is
> optional" section 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.
> _Filed by Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
