davsclaus opened a new pull request, #28002:
URL: https://github.com/apache/camel/pull/28002

   ## What
   
   The AI catalog tools now know the top-level entries of the YAML DSL that 
they missed:
   
   - **`beans`.** `camel_catalog_doc` answers for it: its items are bean 
factories, so the options are those of the `beanFactory` model, and the answer 
says where the entry goes, how a route uses a bean (`#bean:name`, 
`${bean:name.method}`, the bean EIP), and has an example. `camel_catalog_find` 
lists it for `beans` and for `bean` (after the bean EIP). Before, both answered 
that nothing was found, while `camel_catalog_sample` had the example.
   - **Samples for five more entries.** `templatedRoute`, `restConfiguration`, 
`transformers`, `validators` and `sslContextParameters` had no sample, because 
their examples are on the page of what they belong to. The sample generator now 
reads those pages for them (`entryPages` in the camel-jbang-core pom); 
`eip-samples.json` is regenerated.
   
   ## Why
   
   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 was told "EIP not 
found".
   
   Left for later: `camel_catalog_doc` and `camel_catalog_find` do not know 
`sslContextParameters` either (it has a sample now), and `interceptFrom`, 
`interceptSendToEndpoint` and `dataFormats` still have no sample: the first two 
are on the same page as `intercept`, and the generator maps a page to one entry.
   
   ## Tests
   
   `CatalogDocsTest` and `CatalogSamplesTest` have a test each; 
camel-jbang-core and camel-jbang-mcp pass.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01STT6whBgK1AqsSsUKrnE8m
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to