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

   [CAMEL-25865](https://issues.apache.org/jira/browse/CAMEL-25865): a route 
that needs a data file, such as a lookup table (stock.json), reads it with the 
constant language and `resource:file:stock.json`, for example in a 
`setVariable`. That recipe was only on the page of the constant language. For 
the file component, the tools pointed to the poll EIP and pollEnrich, which 
consume the file (without noop it is moved away).
   
   Found in a benchmark of Oct 19-20 2026: in a JMS example, 7 of 12 runs tried 
to load stock.json and failed, and no run opened the constant page.
   
   - For the file component, `camel_catalog_doc` (`CatalogDocs.usage`) adds: 
"to read a data file the route needs, such as a lookup table, use the constant 
language with resource:file: (such as setVariable with constant: 
resource:file:stock.json)". The hint for a consumer option on a `to: file:...` 
(`EndpointChecks`) adds the same. The other components keep their hint.
   - The Simple docs, next to the note that `load()` only reads the classpath, 
say that `camel run` puts the files of the project on the classpath, so 
`${load(stock.json)}` reads a stock.json next to the routes there. They also 
point to `resource:file:` of the constant language for a file of the file 
system in any runtime. The catalog copy of the page is the same as the page.
   
   ## Tests
   
   - `SourceValidatorEndpointTest`: the file component's hint and doc name 
resource:file:; a consumer option on a kafka `to:` and the jms doc do not.
   - All tests of camel-jbang-core pass (2360 + 237).
   
   🤖 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]

Reply via email to