[
https://issues.apache.org/jira/browse/CAMEL-25200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18121274#comment-18121274
]
Brijesh Thakkar commented on CAMEL-25200:
-----------------------------------------
[~davsclaus] I checked the scope question with real YAML (same analysis,
two files alone vs together):
- A: timer -> direct:x (no setBody); B: direct:x reads the body.
Alone: no findings. Together: 1 body-never-set. (project-wide reports more)
- A: timer -> setBody -> direct:x; B: its own timer -> direct:x, reads the body.
B alone: 1 finding (false positive). Together: none. (project-wide reports
less)
So per-file and project-wide differ in both directions. Since overview and
camel validate should never disagree, my proposal is:
1. Analyse per file in overview, with the same schema gate and the same
OpenAPI bodyless endpoints as validate, through one public validator
entry point that YamlValidator also calls. A project-wide version could
follow later for both commands.
2. Keep this change additive: no change to camel validate's output. The
dead-letter/saga and direct://x fixes (they change validate's output)
go in a separate PR.
3. YAML only; a new "Message bodies" section in the markdown and bodyFrom
in the JSON; no change to the Routes table.
Is that OK?
> camel-jbang - camel overview: show where each route's message body comes from
> and report body-never-set
> -------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25200
> URL: https://issues.apache.org/jira/browse/CAMEL-25200
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Brijesh Thakkar
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
