oscerd opened a new pull request, #23255:
URL: https://github.com/apache/camel/pull/23255
## Backport of #23233
Cherry-pick of #23233 onto `camel-4.14.x`.
**Original PR:** #23233 - CAMEL-23515: camel-nats - Use dedicated
HeaderFilterStrategy aligned with sibling components
**Original author:** @oscerd
**Target branch:** `camel-4.14.x`
### Conflict resolution
- `NatsConfiguration.java`: real merge conflict because the field ordering
diverged on `camel-4.14.x` (JetStream fields sit directly after
`headerFilterStrategy`). Resolved by keeping all the 4.14.x-specific
surrounding code and only swapping `new DefaultHeaderFilterStrategy()` ->
`new NatsHeaderFilterStrategy()` (the `DefaultHeaderFilterStrategy` import
removal applied cleanly; `NatsHeaderFilterStrategy` is in the same
package).
- `camel-4x-upgrade-guide-4_21.adoc`: does not exist on `camel-4.14.x`
(modify/delete). Resolved by dropping the 4.21 change and adding a new
`=== camel-nats` section to `camel-4x-upgrade-guide-4_14.adoc` on this
branch. The matching `camel-4x-upgrade-guide-4_14.adoc` entry on `main`
is added in a separate doc-sync PR per the backport upgrade-guide policy.
The `camel-nats` module builds cleanly on `camel-4.14.x` (validated
locally); the full reactor build hits the pre-existing `core/camel-xml-io`
schemagen JDK 21 environment issue that also affected #23233 and #23250.
### Original description
`camel-nats` defaulted its `headerFilterStrategy` to a bare
`new DefaultHeaderFilterStrategy()`, which passes every inbound NATS header
(including `Camel*` / `camel*` / `org.apache.camel.*`) onto the Exchange.
This introduces `NatsHeaderFilterStrategy` (following the
`KafkaHeaderFilterStrategy` / `MailHeaderFilterStrategy` shape) and switches
the default to use it, aligning `camel-nats` with the rest of the component
catalog. Includes a unit test and the upgrade-guide note.
JIRA: https://issues.apache.org/jira/browse/CAMEL-23515 (fixVersions include
4.14.8)
_Claude Code on behalf of Andrea Cosentino_
--
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]
