Claus Ibsen created CAMEL-26482:
-----------------------------------

             Summary: camel-jbang - AI tools: a to: that copies the files a 
file consumer moves, a placeholder left unused, and the place of an errorHandler
                 Key: CAMEL-26482
                 URL: https://issues.apache.org/jira/browse/CAMEL-26482
             Project: Camel
          Issue Type: Improvement
          Components: camel-jbang, camel-yaml-dsl
            Reporter: Claus Ibsen
             Fix For: 4.24.0


Three findings from the r25 run of the local-model benchmark (qwen3.6 35B on 
Ollama), and the runs before it.

*A to: that copies the files a file consumer moves (connect-file-processing 
step 1)*
Asked to move the processed files to the done directory, 4 runs added {{to: 
file:done}} after the file consumer. That writes a copy, and the consumer still 
moves each file to .camel, its default. The write and edit answers now have a 
note when a to: or toD: file follows a file consumer with no noop, move, 
delete, moveFailed or preMove. The note says to set {{move: done}} on the 
consumer, and that a move value that starts with a dot is a hidden folder. It 
is a note, so the write is not refused.

*A placeholder left unused (run-nightly-report step 4)*
Asked to change the schedule, 4 runs wrote the cron in the route over 
{{{{report.schedule}}}}, and the key stayed unused in application.properties. 
The write and edit tools now say so in a note when a change replaces the last 
use of a key that application.properties defines, and no other file of the 
project uses it.

*The place of an errorHandler (fail-well-error-handling step 2)*
- An errorHandler under from: was told it is a top-level entry. Runs that 
followed that moved it to the top level, where it applies to every route, and 
failed. The hint now gives both places: under the route, next to from: (this 
route only), or a top-level item (every route).
- A top-level errorHandler is set on the CamelContext, which has one for all 
routes. A second one in the same file replaces the first for every route, 
without a word. 5 runs wrote a second one for a single route, and failed. The 
validator now reports it, with the line of the first one and the form for one 
route.

_Filed by Claude Code on behalf of davsclaus_



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

Reply via email to