This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch docs/CAMEL-27052-guide-sync in repository https://gitbox.apache.org/repos/asf/camel.git
commit 9158692eec623e3404935ec5cfc4b4565cf01bd0 Author: Claus Ibsen <[email protected]> AuthorDate: Wed Nov 18 21:06:35 2026 +0100 CAMEL-27052: Upgrade guide notes for 4.22.3 and 4.18.6 - camel-jaxb part class and namespace headers Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- .../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 19 +++++++++++++++++++ .../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 15 +++++++++++++++ 2 files changed, 34 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc index 5e34ec55f2e0..c0a2d800a605 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc @@ -191,6 +191,25 @@ logs a warning the first time. Before, the consumer restored the headers and exc Set `transferExchange=true` on both the producer and the consumer endpoints to keep transferring the headers and exchange properties. +=== camel-jaxb - the part class and namespace headers are used only when allowed + +The JAXB data format has a new option `allowPartClassFromHeader` (default `false`). The `CamelJaxbPartClass` and +`CamelJaxbPartNamespace` headers are now used only when this option is `true`; otherwise they are ignored, and the +`partClass` and `partNamespace` options of the data format apply. Before, the headers were always used, and took +precedence over these options. + +With `allowPartClassFromHeader=true`, the headers now apply to their own message only. Before, a header also changed +the `partClass` and `partNamespace` of the data format, so later messages without the header used the class or +namespace of an earlier message. + +Routes that set these headers to choose the part class or namespace per message must enable the option, for example +`jaxb.setAllowPartClassFromHeader(true)` in Java, `allowPartClassFromHeader="true"` on `<jaxb>` in XML, or +`allowPartClassFromHeader: true` in YAML. With REST binding, set the data format property +`xml.out.allowPartClassFromHeader=true` on the REST configuration for a REST service (the response), or +`xml.in.allowPartClassFromHeader=true` for the `rest` producer (the request). + +The SOAP data format (camel-soap) is built on the JAXB data format, and always ignores these headers. + === camel-lra - only an LRA hosted by the configured coordinator is joined The LRA saga service now joins, completes or compensates an LRA only when its URL is under the configured LRA diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc index 293f40a1df3f..f4a554f2d3fa 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc @@ -228,6 +228,21 @@ logs a warning the first time. Before, the consumer restored the headers and exc Set `transferExchange=true` on both the producer and the consumer endpoints to keep transferring the headers and exchange properties. +=== camel-jaxb - the part class and namespace headers are used only when allowed + +The JAXB data format has a new option `allowPartClassFromHeader` (default `false`). The `CamelJaxbPartClass` and +`CamelJaxbPartNamespace` headers are now used only when this option is `true`; otherwise they are ignored, and the +`partClass` and `partNamespace` options of the data format apply. Before, the headers were always used, and took +precedence over these options. + +Routes that set these headers to choose the part class or namespace per message must enable the option, for example +`jaxb.setAllowPartClassFromHeader(true)` in Java, `allowPartClassFromHeader="true"` on `<jaxb>` in XML, or +`allowPartClassFromHeader: true` in YAML. With REST binding, set the data format property +`xml.out.allowPartClassFromHeader=true` on the REST configuration for a REST service (the response), or +`xml.in.allowPartClassFromHeader=true` for the `rest` producer (the request). + +The SOAP data format (camel-soap) is built on the JAXB data format, and always ignores these headers. + === camel-milo - the OPC UA client validates the server certificate When the endpoint it selects uses a security policy other than `None`, the `milo-client` and `milo-browse` components
