Claus Ibsen created CAMEL-24246:
-----------------------------------
Summary: Audit components for exchangePattern (InOnly vs InOut)
support
Key: CAMEL-24246
URL: https://issues.apache.org/jira/browse/CAMEL-24246
Project: Camel
Issue Type: Task
Reporter: Claus Ibsen
Most Camel components have a fixed exchange pattern — for example, HTTP is
always InOut (request/reply) and Kafka is always InOnly (fire-and-forget). The
exchangePattern option only has a practical effect on the limited set of
components that truly support both InOnly and InOut, such as JMS, SEDA, and
AMQP.
We should audit all components to determine which ones naturally support the
exchangePattern option to be configured as either InOnly or InOut, and which
ones do not use it at all. This would help:
- Improve documentation by clearly stating which components honor the exchange
pattern
- Potentially hide or remove the exchangePattern option from components where
it has no effect
- Reduce user confusion about what setExchangePattern actually does (see recent
mailing list discussion with Raymond Meester)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
