Andrea Cosentino created CAMEL-23526:
----------------------------------------
Summary: camel-cxf: align Exchange header constant names with
Camel naming convention
Key: CAMEL-23526
URL: https://issues.apache.org/jira/browse/CAMEL-23526
Project: Camel
Issue Type: Improvement
Components: camel-cxf
Reporter: Andrea Cosentino
The two Exchange header constants in {{CxfConstants}} (module
{{camel-cxf-common}}) use raw string values that do not follow the
{{Camel<Component><Field>}} naming convention used across the rest of the
component catalog. Rename the string *values* only — keep the Java field names
unchanged so routes/code referencing the constants symbolically continue to
work:
* {{CxfConstants.OPERATION_NAME}}: {{operationName}} ->
{{CamelCxfOperationName}}
* {{CxfConstants.OPERATION_NAMESPACE}}: {{operationNamespace}} ->
{{CamelCxfOperationNamespace}}
Consistent with the same alignment applied to camel-elasticsearch-rest-client
(CAMEL-23508), camel-nats (CAMEL-23515), and camel-aws2-sqs / camel-aws2-sns
(CAMEL-23506). Affects 4.21.0 (current main).
h4. Tasks
* Change the two constant string values; keep Java field names.
* Audit all usages of the two constants across {{camel-cxf-*}} modules and
tests for consistency.
* Regenerate component metadata, catalog, and endpoint DSL.
* Add a {{=== camel-cxf}} entry to
{{docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_21.adoc}},
mirroring the camel-elasticsearch-rest-client entry (symbolic references
unaffected; routes using the literal string values must be updated).
_Reported by Claude Code on behalf of Andrea Cosentino._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
