[ 
https://issues.apache.org/jira/browse/CAMEL-25181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18128361#comment-18128361
 ] 

Claus Ibsen commented on CAMEL-25181:
-------------------------------------

Closing as a duplicate of CAMEL-25200, where the work and the design discussion 
are. The scope above is copied there as a comment.

_Claude Code on behalf of davsclaus_

> camel-jbang - camel overview should show where each route's body comes from 
> (reuse the validator BodyTypeFlow)
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-25181
>                 URL: https://issues.apache.org/jira/browse/CAMEL-25181
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang, camel-yaml-dsl
>            Reporter: Claus Ibsen
>            Priority: Major
>
> Add body-origin information to *camel overview*: for each route, where its 
> message body comes from (from the consumer, from the calling route, from an 
> error handler or saga, or never set), and the first step that may set it. Add 
> a {{body-never-set}} finding for a step that reads a body the route cannot 
> have.
> The analysis already exists in the YAML DSL validator (BodyTypeFlow, 
> CAMEL-24844), but it only runs as a validation gate in camel validate. PR 
> #27100 (camel topology, drafted in favour of camel overview) split 
> {{BodyTypeFlow.check}} into {{analyze}} + {{check}}. Reuse that split, so 
> camel overview and camel validate never disagree:
> * Expose {{BodyTypeFlow.analyze}} (and {{EndpointConsumers.unconsumed}}) 
> publicly from camel-yaml-dsl-validator.
> * In ProjectOverview, add a per-route "body from" line (markdown and JSON) 
> and the {{body-never-set}} finding, for YAML routes first.
> * Treat deadLetterUri and saga compensation/completion as callers (as fixed 
> in #27100 review).
> * Fix the {{//}} normalization inconsistency in BodyTypeFlow.
> Limitations to note: YAML only until the shared model analysis exists (see 
> the unification issue), and the body flow is per file today.
> Related: CAMEL-25143, CAMEL-24844, CAMEL-24956 / PR #27100.
> _Filed by Claude Code on behalf of davsclaus_



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to