Skip to content

CAMEL-23515: docs - sync camel-nats 4.14 upgrade-guide entry to main #23256

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
oscerd wants to merge 1 commit into
base: main
Choose a base branch
from
Open

CAMEL-23515: docs - sync camel-nats 4.14 upgrade-guide entry to main #23256

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -255,3 +255,12 @@ The addresses, privateFor and Topics parameters for camel-web3j have been define

The `jobLauncher` and `jobRegistry` is now autowired on the component if there is a single instance pre-configured in the application.
This avoids having to wire this into the Camel component or endpoints.

=== camel-nats

The default `headerFilterStrategy` is now a new `NatsHeaderFilterStrategy` that filters headers
starting with `Camel` / `camel` (case-insensitive) in both the inbound and outbound directions,
aligning the component with the rest of the Camel component catalog (`camel-kafka`, `camel-mail`,
`camel-coap`, `camel-google-pubsub`, ...). Routes that relied on passing through these header
names from NATS messages can supply a custom `headerFilterStrategy` to restore the previous
behaviour.