davsclaus opened a new pull request, #28269:
URL: https://github.com/apache/camel/pull/28269
From the local-model benchmark of Oct 21-22 2026 (qwen3.6:35b-mlx through
the camel-jbang-mcp server).
**Where a language option goes.** A model wrote `resultType` next to the
short form of the language:
```yaml
- setBody:
expression:
jsonpath: "$[?(@.orderId == '${header.id}')]"
resultType: java.util.Map
```
The validator answered only "property 'resultType' is not defined in the
schema", and the model wrote the same file 23 times, into the next step. The
YAML validator now says where it goes: "resultType is an option of the jsonpath
language: write the language as a map, with the text under expression: and
resultType next to it (jsonpath: {expression: "...", resultType:
java.util.Map})". It works for any language and any of its own options, which
`YamlValidator.languageOptions` reads from the schema.
**A JMS reply header set by hand.** The request-reply hint of CAMEL-25901
never fired in the run: it is given for an unknown header that starts with
Camel, and the models wrote `JMSReplyTo`, `replyTo` and
`${header.camelJmsReplyTo}`. A route that sets or reads a JMS reply header by
hand, in a file where nothing is sent with InOut, now gets a note in the
answers of `camel_write_file` and `camel_validate_source`, and the write
message points to it. It is a note, not an error: a reply queue set by hand for
a reply that another route consumes is a design of its own.
**Headers of an endpoint written as the scheme alone.** The header checks
did not run for `uri: jms` with its options under `parameters:`, the canonical
form. They do now.
Tests: camel-yaml-dsl-validator 273, camel-jbang-core 2416 + 237,
camel-jbang-mcp 503, all green.
🤖 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]
