davsclaus opened a new pull request, #109: URL: https://github.com/apache/camel-jbang-examples/pull/109
[CAMEL-24422](https://issues.apache.org/jira/browse/CAMEL-24422) Since Camel 4.23, camel-docling reads a file path in the message body only when `allowFilePathSource=true` (CAMEL-24422, in the 4.23 upgrade guide). `ai/docling-langchain4j-rag` passes the document's absolute path as the body, so on the current 4.23 snapshot it fails at its first `docling` call: > java.lang.IllegalArgumentException: Message body looks like a file path but allowFilePathSource is disabled. Set allowFilePathSource=true to have Docling read it, or pass the document itself as the body. The four `docling` calls now set `allowFilePathSource: true` (the paths come from the example's own `documents` directory), and the README says why. Checked end to end with Docling (`camel infra run docling`, docling-serve v1.35.0) and Ollama `granite4:3b` on Camel 4.23.0-SNAPSHOT: a dropped document is converted, analysed and reported, and `/api/ask` answers from it. `camel validate yaml --canonical` reports nothing. Found while checking #108 (variables), which touches the same file in other lines. _Claude Code on behalf of Claus Ibsen_ 🤖 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]
