oscerd opened a new pull request, #23326:
URL: https://github.com/apache/camel/pull/23326

   ## Summary
   
   Aligns the `camel-cxf` Exchange header constant **values** in `CxfConstants`
   (module `camel-cxf-common`, shared by `camel-cxf` and `camel-cxfrs`) with the
   `Camel<Component><Field>` naming convention used across the rest of the
   component catalog:
   
   | Constant | Previous value | New value |
   |---|---|---|
   | `CxfConstants.OPERATION_NAME` | `operationName` | `CamelCxfOperationName` |
   | `CxfConstants.OPERATION_NAMESPACE` | `operationNamespace` | 
`CamelCxfOperationNamespace` |
   
   The Java field names (`OPERATION_NAME`, `OPERATION_NAMESPACE`) are 
unchanged, so
   routes and code that reference the constants symbolically continue to work
   without changes. Routes that set the headers by their literal string value 
must
   be updated (documented in the 4.21 upgrade guide).
   
   Consistent with the same alignment applied in CAMEL-23508
   (camel-elasticsearch-rest-client), CAMEL-23515 (camel-nats) and CAMEL-23506
   (camel-aws2-sqs / camel-aws2-sns).
   
   ## Changes
   
   - Renamed the two constant string values; Java field names unchanged.
   - Updated the single test that set the headers by literal value, the
     `CxfProducer` javadoc, and the component documentation references.
   - Added a `=== camel-cxf` entry to `camel-4x-upgrade-guide-4_21.adoc`.
   - Regenerated component metadata, catalog, and endpoint DSL.
   
   JIRA: https://issues.apache.org/jira/browse/CAMEL-23526
   
   ---
   _PR created 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]

Reply via email to