Claus Ibsen created CAMEL-25719:
-----------------------------------
Summary: camel-jbang - camel_catalog_doc and camel_catalog_find do
not know the beans entry of the YAML DSL
Key: CAMEL-25719
URL: https://issues.apache.org/jira/browse/CAMEL-25719
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
Fix For: 4.24.0
In the local-model benchmark (Oct 16-17), a model that had to declare a Java
class as a bean looked up {{beans}} four times in one step, and found nothing:
* {{camel_catalog_doc}} with name {{beans}} answers "EIP not found: beans"
(kind eip) or "Artifact not found: beans" (no kind).
* {{camel_catalog_find}} with term {{beans}} answers "Nothing in the catalog
matches 'beans'".
* Only {{camel_catalog_sample}} knows it: it returns a sample of the top-level
{{- beans:}} entry and where it goes.
The other top-level entries of the YAML DSL ({{route}}, {{from}}, {{rest}},
{{routeConfiguration}}, {{routeTemplate}}, {{errorHandler}}, {{onException}},
{{intercept}}, {{onCompletion}}) are known to all three tools.
{{templatedRoute}} has no sample.
h3. Proposal
* {{camel_catalog_doc}} answers for {{beans}}: what the entry is for (a Java
class, a script or a builder declared as a named bean, then used with
{{#bean:name}}, {{$\{bean:name\}}} or the bean EIP), its shape (a list of
{{name}}, {{type}}, {{properties}} and the other keys), and where it goes (a
top-level entry of a YAML file loaded with the routes), with the sample of
{{camel_catalog_sample}}.
* {{camel_catalog_find}} lists it for {{beans}} and {{bean}}.
* A sample for {{templatedRoute}}.
_Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
