oscerd opened a new pull request, #23528:
URL: https://github.com/apache/camel/pull/23528
Backports #23470 to `camel-4.18.x`.
Cherry-pick of merge commit `743fc3774b1` with one adaptation: the original
PR's upgrade-guide entry was added to `camel-4x-upgrade-guide-4_21.adoc`,
which does not exist on the 4.18.x maintenance branch. Per the project's
backport policy the same content has been added to
`camel-4x-upgrade-guide-4_18.adoc` instead.
## Summary
Renames the two Exchange header string values in `Jt400Constants` that were
**not** in the `Camel` namespace (and therefore not filtered by the default
`HeaderFilterStrategy`) to `CamelJt400<Name>`:
| Constant | Previous value | New value |
|----------|----------------|-----------|
| `Jt400Constants.KEY` | `KEY` | `CamelJt400Key` |
| `Jt400Constants.SENDER_INFORMATION` | `SENDER_INFORMATION` |
`CamelJt400SenderInformation` |
`Jt400Constants.KEY` is the data-queue key used for keyed-data-queue read and
write operations. The Java field names are unchanged so routes referencing
the constants symbolically continue to work; routes using the literal string
values must be updated.
`MESSAGE`, `MESSAGE_ID`, `MESSAGE_FILE`, `MESSAGE_TYPE`, `MESSAGE_SEVERITY`,
`MESSAGE_DFT_RPY`, `MESSAGE_REPLYTO_KEY` were already `Camel`-prefixed and
are unchanged.
DSL accessor renames: `kEY()` → `jt400Key()`, `senderInformation()` →
`jt400SenderInformation()`.
## Test plan
- [x] `mvn test` in `components/camel-jt400` on the 4.18.x branch — 34
tests pass (2 skipped)
- [x] Cherry-pick applied cleanly except for the 4_21 → 4_18 guide-file
rename described above (no merge marker shipped)
- [x] Upgrade-guide entry added under `=== camel-jt400 - potential
breaking change` in `camel-4x-upgrade-guide-4_18.adoc`, immediately
before the existing `=== camel-web3j` backport entry
Tracker: CAMEL-23577
_Reported by 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]
