davsclaus opened a new pull request, #26564:
URL: https://github.com/apache/camel/pull/26564
Follow-up of #26562 (`camel_catalog_sample` serves components, data formats
and languages from their documentation). While measuring that, 7 of the 285
component pages with YAML route examples turned out to have no example using
the component's own endpoint (listed on the JIRA). This PR gives six of them
one; the seventh, `mail`, needed no doc change since the tool maps `smtp`,
`imap` and `pop3` to the mail page.
One commit per page, each with Java, XML and YAML tabs, the catalog doc
mirror regenerated alongside:
| Page | Change |
|---|---|
| `hashicorp-vault` | a "Using the producer operations" section:
`createSecret`, `getSecret` (with the `secretPath` option and with the
`CamelHashicorpVaultSecretPath` header), `deleteSecret`, `listSecrets`; the
page showed the property function only |
| `aws-secrets-manager` | the producer operations section lists all eleven
operations (`restoreSecret` and `putSecretValue` were missing), explains which
header names the secret (`SecretName` to create, `SecretId` for the rest), and
shows `createSecret`, `getSecret`, `deleteSecret` and `listSecrets` |
| `infinispan-embedded` | **doc bug**: all six URIs used `infinispan:`, the
scheme of the remote component, kept from before the 2021 split; one had `&`
where `?` belongs and the custom listener example had no cache name although
`cacheName` is required |
| `jcache` | a producer section (the thirteen actions, how
`action`/`CamelJCacheAction`, `CamelJCacheKey` and the body go together, a PUT
and a GET) and a consumer section (the event headers, `filteredEvents`); the
page documented the JCachePolicy only |
| `knative` | plain-route versions of the existing Java-only examples for
producing to and consuming from the broker, and the channel bridge route from
`KnativeHttpTest`; the page had programmatic Java and Kubernetes manifests only
|
| `mapstruct` | the `mapstruct:className` endpoint next to the type
converter example, with when to prefer each |
### Verified
- Every new YAML route passes `camel validate yaml` (schema, endpoint
options, simple, headers), which is what the MCP tools use.
- The XML blocks pass `DocExamplesXmlSchemaTest` and the Java blocks
`DocExamplesJavaImportsTest` in camel-catalog with the regenerated mirror.
- Two things the validator caught on the way: the CloudEvents conversion is
`transformDataType`/`toType` in the YAML and XML DSLs (not `transform`), and
the knative component declares no headers in the catalog, so
`${header.CamelCloudEventType}` cannot appear in a validated example. The
latter is filed as CAMEL-24803; the knative examples keep the header out and
mention it in prose.
_Claude Code on behalf of davsclaus_
🤖 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]
