This is an automated email from the ASF dual-hosted git repository.
Croway pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new e89d7189395a CAMEL-27062, CAMEL-27077: upgrade guides - the camel-cxf
and camel-quartz notes for 4.22.3 and 4.18.6 (#30273)
e89d7189395a is described below
commit e89d7189395a2c16b509d84dd26ce9e2a97cede5
Author: Federico Mariani <[email protected]>
AuthorDate: Tue Nov 17 17:01:11 2026 +0100
CAMEL-27062, CAMEL-27077: upgrade guides - the camel-cxf and camel-quartz
notes for 4.22.3 and 4.18.6 (#30273)
* CAMEL-27077: upgrade guides - the camel-quartz note for 4.22.3 and 4.18.6
* CAMEL-27062: upgrade guides - the camel-cxf and camel-cxfrs note for
4.22.3 and 4.18.6
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 32 ++++++++++++++++++++++
.../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 31 +++++++++++++++++++++
2 files changed, 63 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 8704f01cae28..5e34ec55f2e0 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
@@ -985,6 +985,38 @@ The Camel Main auto-configuration summary shows the value
of these options as `x
These options are matched by their whole key. Component and endpoint options
with the same name, such as `tenantId` or
`serviceAccountKey`, are not affected.
+=== camel-quartz - a scheduler from the registry gets the CamelContext when
the component starts
+
+With a Quartz `Scheduler` set on the quartz component or autowired from the
registry, such as the scheduler of
+`spring-boot-starter-quartz`, the component now stores the CamelContext in the
scheduler context when it starts, before
+the routes add their jobs. Before, it did so only once the CamelContext was
fully started, so a trigger that fired in
+between on a scheduler that was already running failed with `No CamelContext
could be found with name`. Such a job now
+runs its route if the route has started. The component now logs a WARN when
this scheduler is already running when it
+starts, as a trigger that fires before its route has started is still lost
(with Spring Boot, set
+`spring.quartz.auto-startup=false` to let Camel start it), and when the
options `properties`, `propertiesRef` or
+`propertiesFile` are set, as they are not used with such a scheduler.
+
+=== camel-cxf, camel-cxfrs - the former operationName and operationNamespace
headers are not sent
+
+The `CamelCxfOperationName` and `CamelCxfOperationNamespace` headers replaced
the `operationName` and
+`operationNamespace` headers (see the
+xref:camel-4x-upgrade-guide-4_18.adoc#_camel_cxf_potential_breaking_change[camel-cxf
entry of the 4.18 upgrade guide]).
+The `cxf` producer does not read the former names. It now logs a WARN once
when one of them is set without its replacement.
+The default `CxfHeaderFilterStrategy` filters `operationName` and
`operationNamespace` again, as it did before the
+rename, so the service no longer receives them as HTTP headers. A route that
maps a header named `operationName` to
+`CamelCxfOperationName` keeps working.
+
+The `cxf` producer also logs a WARN once when neither the
`CamelCxfOperationName` header nor the `defaultOperationName`
+option selects the operation of a service with more than one operation. It
then invokes the first operation that CXF
+returns, which is not the first one of the WSDL.
+
+The `cxfrs` producer does not read the former `operationName` header either.
With the proxy-based client API
+(`httpClientAPI=false`) it still fails when `CamelCxfOperationName` is not
set. The `NoSuchMethodException` now names
+that header, and says when `operationName` is set, in place of `Cannot find
method with name: null`. The default
+`CxfRsHeaderFilterStrategy` filters a header named `operationName` again, as
it did before the rename. The producer
+no longer sends it as an HTTP header, with either client API. The
`SimpleConsumer` binding no longer returns it as a
+response header.
+
== Upgrading from 4.18.4 to 4.18.5
=== camel-azure-eventhubs
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 56ade44c6d8b..293f40a1df3f 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
@@ -935,6 +935,37 @@ including a value set through an environment variable. By
default this logs a wa
A file location in `camel.vault.gcp.serviceAccountKey`, such as
`file:/etc/gcp/sa.json`, is also reported. It can go
behind a property placeholder too.
+=== camel-quartz - a scheduler from the registry gets the CamelContext when
the component starts
+
+With a Quartz `Scheduler` set on the quartz component or autowired from the
registry, such as the scheduler of
+`spring-boot-starter-quartz`, the component now stores the CamelContext in the
scheduler context when it starts, before
+the routes add their jobs. Before, it did so only once the CamelContext was
fully started, so a trigger that fired in
+between on a scheduler that was already running failed with `No CamelContext
could be found with name`. Such a job now
+runs its route if the route has started. The component now logs a WARN when
this scheduler is already running when it
+starts, as a trigger that fires before its route has started is still lost
(with Spring Boot, set
+`spring.quartz.auto-startup=false` to let Camel start it), and when the
options `properties`, `propertiesRef` or
+`propertiesFile` are set, as they are not used with such a scheduler.
+
+=== camel-cxf, camel-cxfrs - the former operationName and operationNamespace
headers are not sent
+
+The `CamelCxfOperationName` and `CamelCxfOperationNamespace` headers replaced
the `operationName` and
+`operationNamespace` headers (see the
xref:camel-4x-upgrade-guide-4_21.adoc#_camel_cxf[4.21 upgrade guide]). The
+`cxf` producer does not read the former names. It now logs a WARN once when
one of them is set without its replacement.
+The default `CxfHeaderFilterStrategy` filters `operationName` and
`operationNamespace` again, as it did before the
+rename, so the service no longer receives them as HTTP headers. A route that
maps a header named `operationName` to
+`CamelCxfOperationName` keeps working.
+
+The `cxf` producer also logs a WARN once when neither the
`CamelCxfOperationName` header nor the `defaultOperationName`
+option selects the operation of a service with more than one operation. It
then invokes the first operation that CXF
+returns, which is not the first one of the WSDL.
+
+The `cxfrs` producer does not read the former `operationName` header either.
With the proxy-based client API
+(`httpClientAPI=false`) it still fails when `CamelCxfOperationName` is not
set. The `NoSuchMethodException` now names
+that header, and says when `operationName` is set, in place of `Cannot find
method with name: null`. The default
+`CxfRsHeaderFilterStrategy` filters a header named `operationName` again, as
it did before the rename. The producer
+no longer sends it as an HTTP header, with either client API. The
`SimpleConsumer` binding no longer returns it as a
+response header.
+
== Upgrading from 4.22.1 to 4.22.2
=== camel-lra - only an LRA hosted by the configured coordinator is joined