[
https://issues.apache.org/jira/browse/CAMEL-25586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-25586.
---------------------------------
Resolution: Fixed
Fixed by https://github.com/apache/camel/pull/27722 (merged to main as
5432fc78c4d1, 4.24.0).
_Claude Code on behalf of Claus Ibsen_
> camel-jbang-mcp - the route tools read the components of a route from its
> endpoints instead of searching its text
> -----------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-25586
> URL: https://issues.apache.org/jira/browse/CAMEL-25586
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 4.24.0
>
>
> Several MCP tools and CLI commands find the components a route uses by
> searching its text for each catalog component name followed by {{:}} or in
> quotes:
> * MCP {{camel_route_context}} (ExplainTools), the harden tool (HardenTools),
> {{camel_dependency_check}} (DependencyCheckTools) and the dependency security
> audit (DependencySecurityAuditTools)
> * CLI {{camel explain}} and {{camel harden}}
> That misses the endpoint DSL ({{kafka("orders")}}) and constants, and gives
> false hits: a {{log:}} EIP step is taken for the log component, {{rest:}} for
> the rest component, a name in a comment or a description counts.
> h3. Proposal
> A shared helper in camel-jbang-core that reads the route source as routes of
> its DSL with the overview reader ({{ProjectRoutes.parse}}: YAML and XML read
> structurally, Java with the Java DSL parser and the catalog endpoint DSL
> resolver), and returns the schemes of its endpoints that the catalog knows.
> The text search stays as the fallback for content that cannot be read as
> routes. The tools above use it; the line based checks of the security scan
> stay as they are.
> _Created by Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
