davsclaus opened a new pull request, #29326: URL: https://github.com/apache/camel/pull/29326
https://issues.apache.org/jira/browse/CAMEL-26690 Part 3 of 4 for CAMEL-26690, follow-ups from the r28 run of the local-model benchmark. The four PRs are independent of each other: each was built and tested alone on main. - **An sftp or ftp endpoint without a login.** A `to: sftp` without username and password logs in as anonymous, and failed at runtime (connect-sftp-transfer step 3 in r26, r27 and r28). When another endpoint of the same scheme, host and port in the project logs in, the write now says: "to: sftp://{{sftp.host}}:{{sftp.port}}/receipts has no username, so it logs in as anonymous, while the from: on line 4 logs in to the same server: add the same login under the parameters: of this to: ...". Placeholders are resolved from the project's properties. It fires on all 10 accepted anonymous writes of r26 to r28 and on no other sftp write. - **A header read in a split that no step sets.** `toD http://localhost:8080/stock/${header.sku}` in a split, with no step that sets sku, gave 100 errors of 404 (connect-http-client step 1, r28l-6 and -7). The check of CAMEL-26632 covered only a header copied to itself. A read is now reported too, for routes from file, timer, scheduler, cron and quartz: "${header.sku} is null here: no step before this line sets the header sku. In the split the body is one of the lines ...: write ${body[sku]}" (or a variable, when the body changes before the read). Of 462 writes of r23 to r28 with a header read in a split, it fires on exactly the 3 that failed this way. The quartz and cron job headers now count as set. **Checks** - Tests pass: the `ai` package of camel-jbang-core (948, 1 skipped as before), camel-yaml-dsl-validator (350), camel-jbang-mcp (539; CatalogServiceTest failed once on a temp folder path and passed on the retry, unrelated). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_016Y4dDi5iQNgtHrDdz2NpwF -- 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]
