davsclaus opened a new pull request, #26505: URL: https://github.com/apache/camel/pull/26505
Item 7 of CAMEL-24748, the half #26451 left: the jt400 syntax `jt400:userID:password@systemName/QSYS.LIB/objectPath.type` had literal segments the catalog read as options (`Unknown option 'QSYS.LIB'`, `'objectPath.type'`), so every URI on the jt400 page failed the catalog checks and the page sat in the `CatalogDocExamplesTest` skip list. What the component actually does (`Jt400Configuration`, `Jt400Component.createEndpoint`): `objectPath` is the whole URI path (`QSYS.LIB` is not required, the page's own `lib.lib/MSGINQ.MSGQ` examples show it), and `type` is always derived from the suffix after the last dot, after `setProperties` — it was never an option anyone could set. This PR makes the metadata say that: - syntax is `jt400:userID:password@systemName/objectPath`; `type` loses `@UriPath` (the `getType()/setType()` API is unchanged); `objectPath` documents that the suffix (`.DTAQ`, `.MSGQ`, `.PGM`, `.SRVPGM`) selects what the endpoint works with - the page's URI format block is corrected (`user:password@system`, not `user:password/system`) and gains the service program form - `CamelCatalogJsonSchemaTest` drops its jt400 special case (the syntax splitter learns `@`, jt400 is the only syntax using it); new `CamelCatalogTest.testEndpointPropertiesJt400` parses and validates the documented URIs - jt400 leaves the `CatalogDocExamplesTest` skip list - upgrade guide 4.23 entry for the removed `type` path option (URIs are unchanged) - regenerated: jt400.json, catalog, docs, `Jt400EndpointUriFactory`, endpoint-dsl Based on #26501 (first commit); only the second commit is this change. Verified: camel-jt400 tests, `CamelCatalogTest` (127) and `CamelCatalogJsonSchemaTest` (776) in camel-catalog, `CatalogDocExamplesTest` in camel-jbang-core all pass. _Claude Code on behalf of 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
