Claus Ibsen created CAMEL-26823:
-----------------------------------
Summary: camel-core - the route topology says whether a route
waits for the answer of the route it sends to
Key: CAMEL-26823
URL: https://issues.apache.org/jira/browse/CAMEL-26823
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Claus Ibsen
Fix For: 4.24.0
The route topology (RouteTopologyDumper, the route-topology dev console and the
topology JSON of the dump routes strategy) has an edge for every endpoint a
route sends to and another route consumes, for any component, with its
connectionType (internal, external) and kind (call, error). It does not say
whether the sending route waits for the answer of the other route.
For a link over a broker that is the difference between request-reply and a
hand-off: in connect-service/jms-request-reply (camel-jbang-examples)
reserve-order sends to jms:queue:stock with exchangePattern=InOut and waits for
stock-service, while it hands the reserved order to shipping and invoicing over
a topic. Tools that draw or count the flow of an integration (the About view
and the Diagram of the Camel TUI) cannot tell them apart, and count each hop
through the broker as a new message: 14 exchanges for 3 orders.
Proposal: TopologyEdge gets reply (since 4.24): the route waits for the answer,
as the send is InOut (the pattern of the to, or the exchangePattern of the
endpoint), or the component always answers (direct). The console and the
topology JSON write it.
_Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
