[ 
https://issues.apache.org/jira/browse/CAMEL-26412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Claus Ibsen resolved CAMEL-26412.
---------------------------------
    Resolution: Fixed

Merged in https://github.com/apache/camel/pull/28718

> camel-jbang - AI tools: the error handler says it acts on an exception only, 
> a pollEnrich of a file gives the file, and two REST verbs on one path are 
> caught
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-26412
>                 URL: https://issues.apache.org/jira/browse/CAMEL-26412
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jbang, camel-yaml-dsl
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 4.24.0
>
>
> Three gaps that the local-model benchmark (qwen3.6:35b on Ollama, run r24 on 
> Oct 29-30 2026) showed.
> * *The error handler acts on an exception only.* Asked to move an order that 
> the stock service cannot reserve to a dead letter queue, the model added a 
> deadLetterChannel but no exception, in 7 runs of 7. The stock service answers 
> "not enough", which is a normal message, so nothing reached the dead letter 
> queue. The errorHandler sample shows a throwException, but nothing said why. 
> The camel_catalog_sample and camel_catalog_doc answers for errorHandler, its 
> kinds and onException now say that they act only when a step fails with an 
> exception, and that a reply that means no must be tested and thrown 
> (throwException).
> * *A pollEnrich of a file gives the file.* With no variableReceive and no 
> aggregation strategy, the polled message is the body: for the file component, 
> the file as it was read (a GenericFile). The validator took that body for 
> unknown, so a field read such as $\{body[name]\} after it passed the write 
> and failed at runtime. It now reports it, as it does for a file consumer and 
> for a pollEnrich into a variable.
> * *Two REST verbs on one path.* A second get with no path: in one rest passed 
> the validator, and Camel then stopped loading the routes with "Duplicate verb 
> detected in rest-dsl". The validator now reports it at write time, with the 
> advice to give each its own path.
> Also: a quoted value followed by a stray : (a line copied with the colon of 
> the next key) got the message that a YAML value has no concatenation, 5 times 
> in a row. The message now says to remove the : and gives the line to write.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to