Claus Ibsen created CAMEL-25370:
-----------------------------------
Summary: camel-jbang-mcp - the catalog tools answer for the error
handler: samples, where it goes, its kinds, and the redelivery options
Key: CAMEL-25370
URL: https://issues.apache.org/jira/browse/CAMEL-25370
Project: Camel
Issue Type: Improvement
Components: camel-jbang
Reporter: Claus Ibsen
The catalog tools give a model no usable answer for the error handler. Found in
the local-model benchmark (r5, fail-well-error-handling: 3 of the steps that
used all 20 tool calls):
* {{camel_catalog_sample errorHandler}} (and noErrorHandler) answers "No sample
for 'errorHandler' as a eip ... which has no YAML sample". The user manual's
error-handler page has YAML examples of the route-level {{errorHandler:
\{deadLetterChannel: ...\}}} and {{errorHandler: \{noErrorHandler: \{\}\}}},
but they are not among the samples.
* The deadLetterChannel sample says its placement is "a step inside the steps
of a route". It is a top-level {{- errorHandler:}} entry or an
{{errorHandler:}} under one route, never a step.
* {{camel_catalog_doc errorHandler}} lists the option {{errorHandlerType}} with
type object; the model then wrote {{errorHandlerType:}} into the YAML. The
option is one of deadLetterChannel, defaultErrorHandler, noErrorHandler, ...,
written as that key.
* {{camel_catalog_doc onException}} with {{optionsFilter: logStackTrace}}
matches nothing: logStackTrace is an option of the nested redeliveryPolicy.
Proposal:
* The error-handler page is a source of samples for errorHandler;
noErrorHandler and the other kinds resolve to it.
* The placement of errorHandler and its kinds says both places.
* An element option with a oneOf list shows the list and says to write one of
them as the key.
* When optionsFilter matches none of an EIP's own options, the options of its
elements are searched and returned with the element they go under.
_Claude Code on behalf of davsclaus_
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
