Dhairya-007 opened a new pull request, #29488: URL: https://github.com/apache/camel/pull/29488
Four component pages show an example that sets a message header by name, and in each case the name does not match the constant the component actually reads. A header set under the wrong name is not an error — it is simply ignored — so these examples quietly do nothing. | Component | Example sets | Component reads | | --- | --- | --- | | zookeeper | `CamelZooKeeperCreateMode` | `CamelZookeeperCreateMode` | | kubernetes-nodes | `CamelKubernetesNodeLabels` | `CamelKubernetesNodesLabels` | | kubernetes-pods | `CamelKubernetesPodLabels` | `CamelKubernetesPodsLabels` | | spring-rabbitmq | `CamelRabbitmqExchangeOverrideName` | `CamelSpringRabbitmqExchangeOverrideName` | Each right-hand name is the string literal in the component's own constants: ```java // ZooKeeperMessage public static final String ZOOKEEPER_CREATE_MODE = "CamelZookeeperCreateMode"; // KubernetesConstants public static final String KUBERNETES_NODES_LABELS = "CamelKubernetesNodesLabels"; public static final String KUBERNETES_PODS_LABELS = "CamelKubernetesPodsLabels"; // SpringRabbitMQConstants public static final String EXCHANGE_OVERRIDE_NAME = "CamelSpringRabbitmqExchangeOverrideName"; ``` The zookeeper one is the most visible: the page's "create and write to a persistent znode" example passes `CamelZooKeeperCreateMode` to `sendBodyAndHeader`, so the `PERSISTENT` mode it is demonstrating never reaches the component. `CamelZooKeeper...` is a real prefix elsewhere in that component (`CamelZooKeeperNode`), which is why the wrong spelling is easy to miss. Found by checking every `Camel*` token in `components/*/src/main/docs` against the set of header names declared anywhere in the tree; these four appear nowhere. Tokens that are class names or documented prefixes were excluded. The catalog copies of the four pages are updated alongside the sources, per the `src/main/docs` rule in CLAUDE.md. Documentation only — no production code touched. -- 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]
