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

   ## Backport of #23887 to `camel-4.14.x`
   
   Cherry-pick of #23887 (squash commit `3445c57e147`, CAMEL-23716) onto 
`camel-4.14.x`.
   
   The code change is identical to `main` — the `camel-salesforce` 
header-constant set is the same on this branch (all 39 renamed constants exist 
with the same values), so the cherry-pick applied cleanly. Two 
backport-specific adjustments:
   
   - The upgrade-guide entry was added to `camel-4x-upgrade-guide-4_14.adoc` 
(the `4_21` guide does not exist on this branch). Per the upgrade-guide 
backport policy, the matching `4_14` entry will be doc-synced to `main` in a 
follow-up.
   - The component-doc note references Camel 4.14.8 / the 4.14 upgrade guide 
(instead of 4.21).
   
   ### Summary of the change
   
   Aligns the Exchange header constant *values* in `SalesforceEndpointConfig` 
with the project-wide `Camel<Component><Name>` naming convention, so they are 
governed by the default `HeaderFilterStrategy` (which only filters 
`Camel`/`camel`-prefixed headers). The Java field names are unchanged, and the 
endpoint-option spelling (for example `salesforce:query?sObjectQuery=...`) is 
unchanged — only the **header** name changes. 39 header-readable constants are 
renamed; the configuration-only options and the Approval API `approval` / 
`approval.<property>` mechanism are left unchanged.
   
   **Original PR:** #23887
   **Original author:** @oscerd
   **Target branch:** `camel-4.14.x`
   **Tracker:** https://issues.apache.org/jira/browse/CAMEL-23716
   
   Built `camel-salesforce-component` on `camel-4.14.x` — green, unit tests 
pass.
   
   ---
   _Claude Code on behalf of Andrea Cosentino_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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