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

   The deserializer's "unsupported field" and "Unknown expression with id" 
errors now name the nearest field or language and how it is written (`bean` as 
a language is `method: {ref: myBean, method: process}`); a `beans:` class that 
is not found says to check the package and names the built-in strategy package; 
`YamlDeserializationContext` passes the node, field and hint through 
`UnsupportedFieldException`. The generated `ExpressionDeserializers` is 
regenerated by the maven plugin change.
   
   Found while benchmarking a local model against the Camel MCP server 
(CAMEL-24698): a model that wrote `setBody: {bean: ...}` or a misspelled field 
got a message that named the problem and never what to write, and looped on it. 
The same message reaches anyone loading a YAML route.
   
   Tests: `OnExceptionTest` in camel-yaml-dsl; the yaml-dsl common, maven 
plugin and validator modules compile.
   
   Squash of the 7 commits on the working branch; the run-by-run history stays 
on a local bench branch.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   
   https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj
   


-- 
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