[
https://issues.apache.org/jira/browse/CAMEL-23585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrea Cosentino resolved CAMEL-23585.
--------------------------------------
Resolution: Fixed
> camel-arangodb - align Exchange header constant names with Camel naming
> convention
> ----------------------------------------------------------------------------------
>
> Key: CAMEL-23585
> URL: https://issues.apache.org/jira/browse/CAMEL-23585
> Project: Camel
> Issue Type: Improvement
> Components: camel-arangodb
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.21.0
>
>
> {{ArangoDbConstants}} exposes producer-read header constants with
> non-prefixed values:
> * {{ARANGO_KEY = "key"}} - document key for FIND-BY-KEY / UPDATE / DELETE
> * {{RESULT_CLASS_TYPE = "ResultClassType"}} - deserialisation target type
> Rename to {{CamelArangoDb<Name>}}.
> h3. Fix shape
> Rename the *string value* of each producer-read header constant to
> {{Camel<Component><Name>}}; keep the Java field name unchanged so routes that
> reference the constants symbolically continue to compile and run. Update
> tests that use the literal string values; regenerate component catalog JSON
> and docs; add an upgrade-guide entry in {{camel-4x-upgrade-guide-4_21.adoc}}
> (and matching 4_18 / 4_14 for backports where the component existed in those
> branches).
> h3. References
> * Tracker: CAMEL-23577
> * Precedent (rename pattern): CAMEL-23526 (camel-cxf)
> * Alternative pattern (HeaderFilterStrategy approach): CAMEL-23532
> (camel-vertx-websocket / camel-atmosphere-websocket / camel-iggy)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)